The SOP Mapping tool lets you map data from the SOP object and any of its associated objects, to an existing top-level custom object and its associated objects. You can map to any TeamConnect custom object and create multiple mappings for each custom object.
If you want to map incoming SOP text fields to a list of items in a lookup table, each incoming SOP text field must have a matching list item label in the lookup table.
During matter creation, if the lookup table does not have an item whose label matches the SOP text field name, the field is left blank.
If the lookup table contains more than one item with the same label, the first item that SOP manager finds is used to populate the field.
You can customize an SOP record by adding custom fields or custom categories, and then mapping these fields to a matter. If you are using custom categories or custom fields, you must meet the following requirements before you can download SOPs:
•If you want these custom fields to appear on the General page of an SOP record, the custom category must be a child of the SOP object's root category. The unique code of the child must be CUST or a descendant of the <ROOT>_CUST category.
•If a category has required fields, you must specify the default values or the record is created without the custom fields.
•Custom categories must be in the design.
Note: You cannot map custom fields of a custom object.