Linking interface having MNI to another interface with MNI using activity chaining

As per my Understanding 

If you link two interfaces both having MNI (Multiple Node Input) enabled using activity chaining, it will not work as expected. When you chain activities in Appian, it expects a single output from the previous activity to serve as input to the next. However, when both interfaces have MNI enabled, they can accept multiple inputs, which can create ambiguity in the chaining process. In this case, Appian will likely raise an error or not execute the activity chain properly. To resolve this, you may need to rethink your design or use other methods to achieve the desired functionality.

When you link two interfaces with Multiple Node Instances (MNI) enabled using activity chaining in Appian, what happens depends on how many instances (repetitions) are set up. Here's a simple breakdown:

1. Chaining Works:

   • If the number of repetitions is small, the chaining will work smoothly, and the user will move seamlessly from one interface to the next.

2. Chaining Fails:

   • If there are too many repetitions, Appian might stop the chaining to prevent slow performance. The user will be sent back to their Task Inbox or start page instead of continuing to the next interface automatically.

3. Slow Performance:

   • Even if the chaining works, having many repetitions can slow down the system, making the interface load slowly or become unresponsive.

4. User Flow Disruption:

   • If the chain breaks, the user might have to manually find and open the next task or interface, interrupting the smooth flow you intended.

So, it's best to use activity chaining with MNI carefully to avoid these issues.