What are the benefits and drawbacks of using MNI in process model?
Discussion posts and replies are publicly visible
Objective:- MNI is something which we use when we have requirement such that when we want to no the same process N number of times.supports parallel and sequence algorithms.
Pros:- we can achieve looping of a process with counter as increment or decrement .Cons:-Time complexity expansive ,Memory management expansiveSelf Case:- you need to check whether application can have >1K process in upcoming future and what performance you're looking for along with the business expectation as solution temporary or permanent
The general recommendation to implement loops in Appian is:
1- Use appian expressions if possible (eg apply, filter, reject etc)
2- Use MNI
3- Implement the loop in a process model with gateways
Use option 1 whenever is possible.
A common use of MNI is to create multiple tasks and everyone should complete the task.
In the following scenario we can use MNI:
If you want to create multiple tasks for a single event, and all participants should complete the task.
If you are recursively building a text document from process data.
When using Appian RPA to process items from the list.
LOOPING vs MNI :
Use an MNI, if you need to run instances in parallel. Looping flows can’t do this.
Use an MNI, if you need to repeat an activity that involves a user interaction, and it's a different user each time.
Use a looping flow, if you need to repeat an activity that involves a user interaction, and it's the same user each time.
Not use MNI when no of activity chaining is greater