JR53460: DIFFERENT BEHAVIOUR OF MULTI-INSTANCE LOOPING WHEN LOOP CONTENT CONTAINS SERVER SCRIPTS ONLY

APAR status

• Closed as documentation error.

Error description

• If a multi-instance loop is defined with Ordering = Run in
  Parallel, a valid complex flow condition, and Cancel Remaining
  Instance set to true, the execution behavior will differ
  depending on the task implementation:
  
  LOOP CONTENT CONTAINS SERVER SCRIPTS ONLY:
  If there are only server scripts specified in the
  multi-instance loop task content, the various instances of the
  loop are executed sequentially. Therefore all instances are
  executed in sequence, they all run to their end, and at the end
  of all task instances the exit conditions are verified, again
  sequentially.
  
  LOOP CONTENT CONTAINS HUMAN OR SYSTEM SERVICES:
  If the loop task content comes with a Human or System Service,
  then the tasks are instantiated in parallel within their own
  thread. Now when the task of the e.g. third instance is
  completed, and the exit condition is set, then the result is
  given back to the multi-instance loop task, the condition is
  evaluated and the multi-instance loop task completes, which
  will terminate / end all other still running loop instances.
  

Local fix

• n/a
  

Problem summary

• In IBM BPM V8.5.5.0 documentation
  http://www-01.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.
  ibm.wbpm.wle.editor.doc/topics/creating_loops_B.html
  information about the behavior of multi-instance loops when the
  task content contains server scripts only and when it also
  includes services is missing.
  

Problem conclusion

• The content will be updated the next time the documentation is
  refreshed.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  BPM STANDARD

• Fixed component ID

  5725C9500

Applicable component levels