An essential part of the integration framework is mapping ActiveControl fields to the equivalent fields on any external system. This is achieved using the table ‘/BTI/TE_INT_MAPP’. Ideally, this process will need to be undertaken before the framework can be used. For general fields the AC field should be entered complete with table name into field TEFIELDREF and the external fieldname must be entered in the EXTERNAL_REF field. There is also the functionality to be able to reference any AC Custom fields the custom field ID’s would need to be added to TECUSTFIELD_REF, also multiple line itemed fields are able to be handled here such as text fields. Finally, on the mapping table there is a KEY_FIELD field this is used to hold the external system record key in general use a specific non display custom field on the task would be created for this purpose.
| /BTI/TE_INT_MAPP – Integration Mapping | |
|---|---|
| Field | Description |
| EXTSYS_NO | Main external system identifier, this is the identifier of the system that you wish to integrate with we can have as many systems as we want. |
| EXTSYS_NAME | Full description of external system |
| TEFIELDREF | This is the AC Field that needs to be mapped to a field on the external system. This table name is required in the field as well. I.e. /BTI/TE_TASK-PRIORITY |
| EXTERNAL_REF | This is the fieldname that the frameworks calling web service needs to reference to map across the data. |
| KEY_FIELD | This field is the link between the AC record, in our task record we have set up a custom field which is hidden from view and in here we store the ID of the created record on the integrated system. |
| TECUSTFLD_REF | ID of AC Custom field to be mapped. |
| DEFAULT_VAL | Defaulted Value to be mapped over to the integrated system field. |
Figure: Example configuration of the JIRA mapping table.
Post your comment on this topic.