Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourYellow
titleUnder progress

 

Table of Contents

Known Issue Status

Occurrence
Display known issue occurrence
StartingFromRelease1.3
 
Change Management Issue
Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJS-1253
 

Behavior

  • Passed Test Case
    • Starting Situation
      • A nested job chain has three nodes A, B and C
      • Node A and C has use the same sub job chain
    • Action
      • Add a an order i.e. Main_Order to the nested job chain
      • Open JOC, righ click on the order Main_Order and start now
    • Behavior
      • Order Main_Order will start at two nodes i.e. Node A and Node C,since  the same job chain is assigned to both of the nodes.
  • Explanation
    • A nested job chain has contains other job chains as nodes, so for a an order submitted to a  nested nested job chain, the state is ideally a sub job chain.
    • At the same time each Each job chain has its own order queue thus an order submitted to Top the top level job chain once reach to sub would appear at the same time in the included identical job chain and if same job chain is used in multiple node, all the nodes will start simultaneously. 

Requirement

  • In a nested job chain one job chain can be used multiple times

Workaround

  • job chain the same job chain should be re-usable

Workaround

  • The workaround is to create multiple copies of the job chain with different names. The same jobs can be used for the copy of the job chain, therefore this workaround does not create any considerable overhead.

Resolution

  • This issue will not be fixed. The behavior of job chains works as expected. The workaround can easily be applied.Not Available