search cancel

ARA/CDA Upgrading package type lauches workflows?


Article ID: 104014


Updated On:


CA Automic Workload Automation - Automation Engine


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

<Please see attached file for image>

User-added image


You can follow the workaround as below

Please go to IIS server, then look for the WebUI\config folder, 
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"/> 
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. 


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 


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 (
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  


1558690866894000104014_sktwi1f5rjvs16gf9.png get_app