In a process model with a start form and two synchronous subprocesses of 40 and 66 nodes each, all nodes chained from the start to the end, what could cause the confirmation screen not to be shown to a normal user?

In a process model with a start form and two synchronous subprocesses of 40 and 66 nodes each, all nodes chained from the start to the end, what could cause the confirmation screen not to be shown to a normal user?

• A. The maximum number of activity chained nodes is exceeded and breaks.
• B. The user lacks permission to view the confirmation screen.
• C. The process has no end node.
• D. The start form is not published.

Answer: (A)

The main concept is that there is a limit on how many activity nodes can be chained in a single process path, and exceeding that limit can prevent the process from progressing to later steps such as a confirmation screen. In this scenario, the two synchronous subprocesses have 40 and 66 nodes, and when chained from start to end the path totals 106 nodes. If the system’s maximum allowed number of chained nodes is around 100, this path would exceed it, causing the chain to break or fail to render the subsequent screens. That’s why the confirmation screen wouldn’t be shown to a normal user. The other possibilities (permission issues, no end node, or an unpublished start form) don’t align with the described flow and wouldn’t inherently cause the confirmation screen to disappear in this setup.

The main concept is that there is a limit on how many activity nodes can be chained in a single process path, and exceeding that limit can prevent the process from progressing to later steps such as a confirmation screen. In this scenario, the two synchronous subprocesses have 40 and 66 nodes, and when chained from start to end the path totals 106 nodes. If the system’s maximum allowed number of chained nodes is around 100, this path would exceed it, causing the chain to break or fail to render the subsequent screens. That’s why the confirmation screen wouldn’t be shown to a normal user. The other possibilities (permission issues, no end node, or an unpublished start form) don’t align with the described flow and wouldn’t inherently cause the confirmation screen to disappear in this setup.