Page History

Known Issue Status

Behavior

• Passed Test Case
  • Starting Situation
    • In a A nested job chain a order is wating to be execute.
  • Action
    • Open the JOC , right click on the order and select the order state
  • Behavior
    • Order can only be assigned to the Sub job chains i.e. states of nested job chain but not to the state of sub job chain
  Failed Test Case
  • • has three nodes A, B and C
    • Node A and C use the same sub job chain
  • Action
    • Add 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.
  • Starting Situation
    • as above
  • Action
    • Open the JOC, right click on the order and select the order state, Try to set the order's state as one of the state of sub job chain.
  • Behavior
    • Order will can not be set to sub job chain's state
• 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.
  • In a practical scenario when job chains are organized under nested job chain, order's state can be set to one of the sub job chain.
  • As of now we don't see any real use case where order assigned to nested job chain need to be assigned to state in sub job chainEach job chain has its own order queue thus an order submitted to the top level job chain would appear at the same time in the included identical job chain and all the nodes will start simultaneously.

Requirement

• In a nested job chain order's state can be assigned to a state of sub job chain.

Workaround

• 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