There are two options when it comes to deleting existing Transport Forms within ActiveControl:

1. Permanent deletion of the Transport Form (this deletes all audit history of the Transport Form within ActiveControl – and so is generally not recommended)

2. Deletion of Transport Form from its current control point location. (this moves the Transport Form off the end of the Path (or branch))

Over the years, some existing customers have raised concern with the knock-on impact on Integrations with other 3rd party tools such as JIRA or ServiceNow in the situation where there is only that one Transport Form associated with the Business Task. This impact stems from the fact that when the Transport Form is deleted, it goes to “Transporting Completed” status, and the Business Task goes to “Deployment Complete” status since there are no other Transport Forms linked to the Business Task. As a result, this can cause an existing integration from ActiveControl to premature close the corresponding ITSM ticket and causing confusion for business end-users.

ActiveControl 9.10 introduces a new optional capability that can be used in this scenario, whereby it is possible to prevent the Business Task from going to “Deployment Complete” , but instead going to another (configurable) Deployment Status (eg “Deployment Cancelled”) that does not trigger an Integration (or give wrong impression on the Business Task that changes have been delivered on the change).

Configuration Steps

Please refer to this online Knowledge Article for details on how to configure this optional feature.


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