Integration Status Check (0065) analysis can be used to perform an automated check to ensure that a corresponding ticket in an integrated ITSM or other external system is in the correct/expected status. The analyser will warn if the other tool ticket is not in the expected (configurable) status (as can potentially happen depending on the setup of the Integration / the external ticket being transitioned back in its workflow). For example – if you are about to approve some Transports to move to Production in ActiveControl, but the corresponding external ticket for that Business Task is somehow sitting in status “Awaiting UAT”.
|Needs to match what was configured for your external system in table /BTI/TE_INT_SYST.
|The message you want to appear in the message output if the expected/actual status’ do not match.
|This is the field name from the external System. E.g. status-name in the case of JIRA Status field.
|This is the Status field value from the external System that you want to check for (any other value will make the Analyser present a warning). Please note that [STATUS_IN_EXTERNAL_SYSTEM] is the technical value – not the Label that is seen by the user (in the case of JIRA). Also please note that the status parameter is case sensitive. It needs to match the technical field value in your external system exactly (eg “To Do” and not “TO DO” in the above screenshots).
(i) The analyser requires some of the standard Integration framework to already be setup for your external system. (i.e /BTI/TE_INT_SYST plus associated configuration tables).
(ii) The analyser has been build to satisfy a specific customer requirement for their existing ActiveControl integration with JIRA, but the reality is the Analyser can potentially be used with any ITSM / external tool that is supported by the ActiveControl Integration Framework. It should be noted, this would require some modification to the existing 0065 Analyser, ie it will not work out-of-the-box on other tools such as ServiceNow or suchlike.