Problem with Postconditions when adding tasks to workflows

Document ID : KB000098488
Last Modified Date : 30/05/2018
Show Technical Document Details
Issue:
The problem is described based on an example

There is a workflow with (in this case) 6 tasks in it, all of them have the same postcondition. It makes no difference whether the then- and else-branch call different scripts or not

User-added image

The example-script SCRI.NEW.PP is called in the postcondition with action START OBJECT. Script SCRI.NEW.PP contains the Promptset PRODB.LOGIT.PRPT with mandatory text fields
 
User-added image

Via <PARAMETERS> these fields are supplied with some text
 
User-added image

This workflow runs correctly
 
User-added image

Close the workflow and open it again. Then add at least two more tasks again with the same postconditions (SCRI.NEW.20 and 21 in the screenshot below). Adding only one does not seem enough to cause the error
 
User-added image

Start the whole workflow again. An error occurs on the first task. The first task WAS NOT CHANGED, not even touched during editing
 
User-added image
Unblock the 1st task, the 2nd tasks blocks, which again has NOT been changed
 
User-added image
The script that is called in the postconditions ends with
 
User-added image
  
Resolution:
Workaround: Edit all postconditions of the tasks in the workflow. You do not need to change anything. Just click on and close the dialog again with Accept
 
User-added image

If you do that for all Tasks the workflow runs without an error again.