Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
2.0.0
-
None
Description
Current Situation
- When a workflow definition does not start with a fork but with another instruction, e.g. a job instruction, the following behavior can occur when the Order Log window is open during live execution:
- Example workflow definition:
- Job1
- Fork (Job2a, Job2b)
- Job3
- The following behavior will occur when the Order Log window is open while the first job (Job1) is running:
- Job1 is displayed correctly.
- OrderForked is displayed.
- The jobs of the forked branches Job2a, Job2b are not displayed.
- OrderJoined is displayed after Job2a and Job2b have finished.
- Job3 is displayed.
- So the fork jobs are not displayed.
- Example workflow definition:
Desired Behavior
- The live progress of the fork jobs or other instructions inside a fork should be displayed correctly.
Test Instructions
- Use, for example, the attached JOC-2269-TEST.workflow.json
. - Start the workflow run and open the Order Log window while the first job is running.
- Expected behavior: all live nodes of the workflow execution should be displayed correctly.