ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Result tab conversion to Postcondition tab adds ENDED_SKIPPED clause
Article ID: 84779
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
In Version 9 the Result tab of a workflow tasks has been replaced by the Postconditions tab.
When you load a Transport Case, the objects are automatically converted to the new version.
When the Result tab is converted to a Postcondition tab, the Result tab settings are to execute a script for a status other than ENDED_OK. After the import to a newer version the Postcondition has one extra condition which checks to see if the status is ENDED_SKIPPED() else.
The intended behavior in V8 is as follows:
Check to see if the staus of the Task is ENDED_OK else execute a script (this includes the status ENDED_SKIPPED).
As of V9 there is no option available in the Postcondition tab to take an action on an ENDED_SKIPPED status because the Postcondition is not executed.
N/A
In Version 9 the Result tab of a workflow tasks has been replaced by the Postconditions tab.
When you load a Transport Case, the objects are automatically converted to the new version.
When the Result tab is converted to a Postcondition tab, the Result tab settings are to execute a script for a status other than ENDED_OK. After the import to a newer version the Postcondition has one extra condition which checks to see if the status is ENDED_SKIPPED() else.
The intended behavior in V8 is as follows:
Check to see if the staus of the Task is ENDED_OK else execute a script (this includes the status ENDED_SKIPPED).
As of V9 there is no option available in the Postcondition tab to take an action on an ENDED_SKIPPED status because the Postcondition is not executed.
Cause
Cause type:
Defect
Root Cause: Change of workflow behavior from V8 to V9 - See Release Notes for Version 9.00A on docs.automic.com. The DB Load utility added an unnecessary ENDED_SKIPPED clause to the postconditions of a workflow task.
Defect
Root Cause: Change of workflow behavior from V8 to V9 - See Release Notes for Version 9.00A on docs.automic.com. The DB Load utility added an unnecessary ENDED_SKIPPED clause to the postconditions of a workflow task.
Environment
OS Version: N/A
Resolution
Update to a fix version listed below or a newer version if available.
Fix Status: Released
Fix Version(s):
Automation Engine 12.0.2 – Available
Automation Engine 11.2.4 – Available
Automation Engine 11.1.6 – Available
Fix Status: Released
Fix Version(s):
Automation Engine 12.0.2 – Available
Automation Engine 11.2.4 – Available
Automation Engine 11.1.6 – Available
Additional Information
Workaround :
Add the script to be executed in the Task Dependencies in case the Task is skipped.
Add the script to be executed in the Task Dependencies in case the Task is skipped.
Feedback
Yes
No
Powered by
