The standard DevMax Merge process will still merge where a conflict has been identified with an unreleased transport in the target Development system.

This can cause a risk of inflight work being overwritten / impacted.

ActiveControl 7.1 includes an enhanced 0005 DevMax: Conflict Analysis – whereby the Analysis results will highlight if the conflict is with a modifiable transport in the target system (last column in below screenshot), and also a new reason code to prevent the Merge from being done.

Configuration Steps

Switch on the UNRELEASED_TRANSPORTS_CHECK (X) if you want to see an extra column indicating the release status of the conflicting transports.


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