Step 3: Standard Evidence Configuration

There are a number of steps involved when configuring a new evidence type. Here is a checklist.

Name the Asset evidence type by adding an entry to Evidence Type Code Table.
Optionally, create a static description for Asset evidence via a new entry in the Text Translation initial data. Link this Text Translation to a new entry in the Localizable Text initial data. This step can be defered until later. It's only visible to the user on the New Evidence screen.
Add a new entry in the Evidence Metadata initial data linking it to the the Evidence Type and, optionally for now, the Localizable Text.
Link the Evidence Metadata to either an integrated case or a product by adding an entry to the Admin IC Evidence Link or the Product Evidence Link initial data respectively. If the evidence is to belong to an Evidence Category (e.g. Resources) set the category attribute here.
If the Asset Evidence Business Object Tab is to be utilised in a given Section of the application, contribute to the section definition (e.g. DefaultAppSection.sec). Without this contribution the Asset Evidence Business Object page will simply load in the current content panel.
A sample section file is generated for each product including all the evidence tabs. This sample is located at EJBServer/components/EvGen/ tab/BusinessObjectTab/<product.prefix>GeneratedAppSection.sec
```
<sc:section
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:sc=
  "http://www.curamsoftware.com/curam/util/client/section-config"
  id="DefaultAppSection"
>
  <sc:tab id="AssetObject"/>
</sc:section>
```

Note: There is one handcrafted implementation that must be completed after running the generator, as without it, some evidence screens will not be accessible. See Asset Hook getDetailsForListDisplay.