Suggestions for Designing a Process Model

Go to the user input task properties --> Others tab --> Multiple Instances Section --> Select "Run one instance for each assignee". It will assign the task to 50 members.

Its better to have 50 members in a single group.

can you please elaborate the scenario...
do you want to handle the data after the user submission??
or do you want to restrict the task for only 1 user??

sowjanya@yeah Both Scenario's

@praveenkumark could you please explain your requirement in brief

50 Instances need to be created for one task and need to handle the 5o task data after Submission

If i am not wrong, you want to have one task for each assignee, so that everyone can complete their own, for example, Feedback application where each individual is needed to complete the task rather than a single among group, if so, then there is an option

'When executing more than once, there should be one-to-one assignment of task instances to assignees'

under Assignment tab of User Input Task, which you can go for

I hope this will help you

You can use MNI for this , generate the tasks on the basis of the total member of a group. But can i know the business use case for this? I think once you tell us the logic behind generating so many tasks , the practitioners here can provide you other better way as well.

@praveenkumark,
1st scenario,you can handle in 2 ways:
1) If data is same for all the instances then under the MNI section of user input task you need to select "Automatically run multiple instances of this node" and
specify the PV variable in "Run one instance for each item ". This overrides all the previous instances(considers the latest 50th instance by overriding other 49 instances).
2) If each instance data is required you can select : "Run one instance for each assignee". This stores each instance.

In the 2nd case: Add all the 50 members to a group and add that group to the assignment,this restricts single user at a time,if 1 user accepts the task others would not be able to see the task.
Please let me know if this is not the case which you asked for...

@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.