Suggestions for Designing a Process Model

@praveenkumark Is the requirement about generating the tasks for all the users wherein each user will have their own copy(something like a Feedback form)? If so, afaik, there are two approaches for this:
1. Creating a process model that holds the task and the necessary DB updates which run based on the context of a user. And this process needs to be MNI'ed for each user, which is 50 in your case.
2. Another option is to MNI'ing the task and for this, you need to shield the process variable (which has been elaborated at https://forum.appian.com/suite/help/16.1/Protecting_Process_Variable_Values_in_Parallel_Flows.html and https://forum.appian.com/suite/help/16.1/Process_Variables_and_Parallel_Flows.html) from parallel flows to capture the data without being overridden.

Both of the approaches mentioned above has got their own pros and cons which we can discuss based on the conversations in the thread. Above-mentioned is the core design and to make it best, you need to follow the best practices which you see in the documentation such as archiving the instances whenever possible, achieving engine balancing when there is a chance to kick-off multiple flows at a time etc.

I believe a good discussion has taken place at https://forum.appian.com/suite/tempo/entry/e-194377. I would suggest going through it if possible.

@praveenkumark Is the requirement about generating the tasks for all the users wherein each user will have their own copy(something like a Feedback form)? If so, afaik, there are two approaches for this:
1. Creating a process model that holds the task and the necessary DB updates which run based on the context of a user. And this process needs to be MNI'ed for each user, which is 50 in your case.
2. Another option is to MNI'ing the task and for this, you need to shield the process variable (which has been elaborated at https://forum.appian.com/suite/help/16.1/Protecting_Process_Variable_Values_in_Parallel_Flows.html and https://forum.appian.com/suite/help/16.1/Process_Variables_and_Parallel_Flows.html) from parallel flows to capture the data without being overridden.

Both of the approaches mentioned above has got their own pros and cons which we can discuss based on the conversations in the thread. Above-mentioned is the core design and to make it best, you need to follow the best practices which you see in the documentation such as archiving the instances whenever possible, achieving engine balancing when there is a chance to kick-off multiple flows at a time etc.

I believe a good discussion has taken place at https://forum.appian.com/suite/tempo/entry/e-194377. I would suggest going through it if possible.