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.
| /BTI/TE_INTEG_TRIGGER se38 | |
|---|---|
| Selection Option | Description |
| External System | The external system the trigger program is to be run against |
| Integration trigger condition | Pick up the task based on the following conditions: 1) Based on BT update 2) Based on the update in standard/custom fields of business task 3) Based on the update in form( add/delete from business task ) 4) Based on status update (Traditional) & form add/del from BT 5) Based on status update (Traditional) 6) Custom triggering condition when BT is updated |
| 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) |
Only populate the options fields if you want to Exclude specific TE Tasks from the Service Now integration.
Create a Batch job with the same name and variant.
Post your comment on this topic.