Field Mapping
In the context of ENPS, this table is used to map Playbook fields to ENPS fields.
Users at sites with both ENPS and Playbook can search Playbook from within the ENPS client. Results are returned alongside other matches from within ENPS and can be drag-and-dropped into a Rundown or Planning Grid.
The field mappings in this table determines how that content and metadata is presented in the grid and resulting ENPS Story / Planning Item.
For example, if you map the PSTCategory field to the ENPS Category field, any values in the former will be inherited by the latter.
Rules for creating valid field Mappings
- The validation type of the source field ID and the destination field ID must match for the field to be accepted as a valid field mapping.
- The validation type of the destination object must be supported by the client for the destination object type. This means new validation types like lookuplist that are not yet supported by ENPS cannot be leveraged when creating a mapping for an ENPS object such as a script.
- Complex validation types, such as special, are not supported.
- If a mapping is set up between two fields that have different schema options - for instance a combo box or checklist - then the source field value will be copied even if it is not in the target field.
- Only create one mapping per source/destination object type and destination property.
- If a field has the property
DO NOT COPY
selected in theSystem or Local fields tables, the content of that field will not be copied between ENPS and Playbook.
Pre-Defined Options for System Properties
Rules for creating valid field Mappings
- ENPSText- content of the object from above the black line in the editor window
- ENPSTextBBL- content below the black line in the ENPS editor window
Settings
Setting |
Description |
---|---|
Source object type |
The type of the object being dragged into ENPS. Set to either Topic o rAssignment. |
Destination object type |
The type of ENPS object the source object is being mapped to. Set to either Story or Planning Item. |
Source Field ID |
The field ID for the Playbook object field to be mapped. |
Destination Field ID |
The field ID into which the Playbook field is being mapped. |
Copy to Target |
Should be ticked. |
Copy to Child |
Not relevant in this context |
Update to Child |
Not relevant in this context |
Update to Parent |
Not relevant in this context |
Data Rules (only for update to child/parent) |
Not relevant in this context |
Update to Linked Object |
Not relevant in this context |
Publication Channel Type (only for update to linked object) |
Not relevant in this context |