A trigger program should be scheduled to pick up the Task status changes that need to be interfaced to the external system(s). This trigger program selects the appropriate AC records, dependent on the configuration set up above, and passes it through the mapping engine. It then stores the mapped integration transactions into a set of standard tables.
Program Name: /BTI/TE_INTEG_TRIGGER
| Selection Option | Description |
|---|---|
| External System | The external system the trigger program is to be run against |
| Integration Trigger Condition | The trigger program /BTI/TE_INTEG_TRIGGER reads the updated business task based on various conditions defined in table /BTI/TE_INT_COND. Although historically with the Integration Framework it was only possible to trigger the outbound integration based on changes to Business Task [Deployment Status], it is also now possible to trigger based on other updates, such as updates to other Business Task standard or custom fields. If nothing is entered in this field, then the default will be ‘Based on status update(Traditional)’. |
| Task ID | Task(s) the trigger program will be run against |
| Task Type | Task Type(s) the trigger program will be run against |
| Task Reference | Task Reference the trigger program will be fun against |
| Task Priority | Task Priority the trigger program will be run against |
| Send previous changes | Select this checkbox if Task status changes is ‘backwards’ in the process and this change should be sent to the external system |
| Run as though Last Run on | The date and time of the ‘last’ run can be entered manually if this flag is checked |
| Run Date | The date of the last run (if manually entered) |
| Run Time | The time of the last run (if manually entered) |
Figure: A variant of of Program /BTI/TE_INTEG_TRIGGER needs to be created and scheduled to run periodically (typically every 5-10 minutes).
Using trigger condition based on the update in standard/custom field of a Busines Task
Table /BTI/TE_INT_TRIG is required to be configured if the triggering strategy is based on the update in standard/custom field of a business task. The condition ID for this strategy is INT_ON_FIELD_UPDATE.
| Field | Description |
|---|---|
| EXT_SYS_NO | Integration System Number |
| CONDITION ID | INT_ON_FIELD_UPDATE from table /BTI/TE_INT_COND |
| TE_FIELD | Possible fields are : CAPTION REFERENCE GROUPID TYPEID TESTERID PRIORITY PROJECTID STAT_DEPL STAT_PLAN {Custom Field Number} |
| IDENTIFIER | Corresponding values that are required to trigger the integration. |
Figure: Example configuration of table /BTI/TE_INT_TRIG
Post your comment on this topic.