Prior to ActiveControl 7.20, the Integration Framework facilitated integration only when the 3rd Party ticketing tool identifier was stored in the Business Task ‘Reference’ field.

Some customers now prefer to use ActiveControl auto-generation of Task References, and store the 3rd Party identifier in a seperate ‘custom’ field.

ActiveControl 7.20 provides this capability.

After setting up the Configuration detailed below, when the standard /BTI/TE_INTEG_POLL program is run for a particular sequence and Ext System Number, a Business Task should be created, with the custom JIRA Reference field populated with the corresponding JIRA ticket number.


1) A working ActiveControl integration with other supported 3rd Party system.

Configuration Steps

1) Enable the auto-generate Task Reference with prefix via the ActiveControl Windows GUI configuration ([Other] tab).

2) Add the user exit into table /BTI/TE_EXITC in the Domain Controller. Please note this is a custom user exit, would need to be provided by Basis Technologies.

3) In table /BTI/TE_INT_POLF ion the Domain Controller, replace Key= Header-Reference with Key= EXTERNALID

Other Notes

(i) The new Jira Reference custom field is not a standard custom field. The new field will only be present on a Business Task if the relevant configuration is set.

(ii) Both the Jira Reference field and the _BT auto-generated number fields are non-user editable.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment