ARA/CDA Upgrading package type lauches workflows?

Document ID : KB000104014
Last Modified Date : 28/01/2019
Show Technical Document Details
Issue:

Our customer perform an upgrade on custom type (for package state change - They are using RM5)
and after the upgrade many workflow got trigger automatically. Please take a look at the below screenshot and attachment of custom type
User-added image

Environment:
Application.Release.Automation 5.1.4 HF2,Application.Release.Automation 6.0.7, Release.Manager 9.0.0,Release.Manager 8.0.2,Release.Manager 7.0.4 HF2 
Cause:
You can follow the workaround as below

Please go to IIS server, then look for the WebUI\config folder, 
..:\UC4\RM\WebUI\config
look for a config file name "core.config" then you can comment the below section 
<object type="Ventum.Bond2.Interceptors.AeIntegrationInterceptor, Ventum.Bond2.Services.Impl"> 
<property name="AutomationEngineConnector" ref="automationEngineConnector"/> 
</object>
then Restart IIS, now you can update the package in mass, and the workflow will not be trigger, after update you can enable the section above. 
Resolution:
The issue was found and fixed with Release.Manager 9.0.1 in Release Manager. The Package is available for download at the Automic-Support-Zone (https://support.automic.com).
Hotfix-Description: Workflows are triggered while upgrading Packages to a new Custom type version
A problem has been fixed where workflows were triggered during the upgrade of Packages to a higher Custom type version.
While upgrading Packages to a new Custom type version, the transition workflow was re-executed even though the Package state did not change.

The fixes also provided in below version
Release.Manager 8.0.4,Release.Manager 10.0.0,Release.Manager 9.0.1