Error Message :
When loading Transport Cases from AE version 8 or older into more recent AE versions, Postconditions are sometimes overwritten. At upgrade, objects are exported via a transport container from an older version (say version 8).
DB Load imports data from Transport Cases of older AE versions and migrates Postconditions using the database format used by the newer AE versions.
When a second DB Load is executed to import another Transport Case (again, older AE version), the migration procedure is triggered again.
Changes made to the Postconditions between the first DB Load and the second are lost.
Impacts are seen in Workflows where a Job's Task Properties contain a condition (entered in the Result tab).
These containers are loaded into the new version.
DB Load converts the Result tab into Postconditions.
This is a standard operation for upgrades because the Result tab in V8 and older was replaced by Postconditions in V9 and above.
In the DB's JPP table (jobplan process), the column JPP_RWhen and JPP_RElse are set.
The Postcondition is then removed manually (during normal WF editing).
Then, a second DB Load is executed with objects that contain Result tab data. These objects are entirely separate from the first DB Load.
Yet when the DB Load completes, the post condition from the DB Load is present.
Root Cause: When DB Load imports transport cases from older AE versions, it migrates Postconditions to the database format used by newer AE versions.
Whenever DB Load is used to import another transport case from older versions, the procedure is triggered again.
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.
Fix Status: Released
Automation Engine 12.0 - Available
Automation Engine 11.2.3 - Available
Automation Engine 11.1.5 - Available
Automation Engine 10.0 - will not be fixed
Check Workflows after DB Load of a transport case and remove Postconditions manually.