What might be the reason for this behavior?

You created and published a new process model.

The process model has a start form with two synchronous subprocesses with 40 and 66 nodes each. All nodes are chained from the start node through the subprocesses to the end node. After the tasks and subprocesses, there is a second User Input Task in which the user can confirm the entries and add a comment.

When testing as a normal Acme business user, you see that the confirmation screen is not shown to you.

What might be the reason for this behavior?
A . The maximum number of activity chained nodes is exceeded and breaks.
B . The second User Input Task is assigned to the process initiator.
C . The second User Input Task is assigned to the Acme business user group.

View Answer

Answer: A

Explanation:

In Appian, there is a limitation on the number of activities that can be chained in a process, known as the "chaining limit." If a process model exceeds this limit, which includes synchronous subprocesses and their nodes, the process may break or not behave as expected. In this scenario, with two large subprocesses chained from start to end, the maximum number of activity chained nodes could be exceeded, resulting in the confirmation screen not being shown. Adjusting the process model to reduce chaining or using asynchronous patterns where possible can help mitigate this issue.

Reference: Appian Documentation – Process Model Best Practices