Any suggestions on how to collect input from multiple individuals at the same ti

@judym Hi, here goes my suggestions based on your comments:

>> That seems to work but I get 2 tasks for every person in the group (not sure why)

Choose 'There should be one-to-one assignment of task instances to assignees' under 'When executing more than once:' section in the 'Assignment' tab of User input task. Else you will continue to see more than 1 task. Please bear in mind that 'When executing more than once:' section will be shown only when you choose 'Show Advanced Options' in the 'Assignment' tab of User input task.


>> Each form collects the 'vote' (Y or N) and any feedback (text) in a CDT that is set up as a 'multiple'. When I test it - I get the multiple tasks/assignee but the data saved is just the last data entered. How do I get all responses saved?

I would like to suggest to go through the documentation 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 to get an idea over how to design in this situation with respect to persisting values.

For instance, though you are dealing with MNI (that is, one task per person in the group), you don't need an array variable and a subprocess to update the values in the database. If you shield the PV (from parallel executions) properly, a single (that is, non multiple) PV and a simple Write to Data Store Entity (not MNIed) is far more sufficient.

Offcourse, choosing a multiple PV and thereby a subprocess to make the updates, also works, but it's not the only way. Provided if you are able to implement the Shielding PV from multiple flows concept, your design looks simple and clean from the MNI, intermediate events, subprocess nodes etc.

@judym Hi, here goes my suggestions based on your comments:

>> That seems to work but I get 2 tasks for every person in the group (not sure why)

Choose 'There should be one-to-one assignment of task instances to assignees' under 'When executing more than once:' section in the 'Assignment' tab of User input task. Else you will continue to see more than 1 task. Please bear in mind that 'When executing more than once:' section will be shown only when you choose 'Show Advanced Options' in the 'Assignment' tab of User input task.


>> Each form collects the 'vote' (Y or N) and any feedback (text) in a CDT that is set up as a 'multiple'. When I test it - I get the multiple tasks/assignee but the data saved is just the last data entered. How do I get all responses saved?

I would like to suggest to go through the documentation 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 to get an idea over how to design in this situation with respect to persisting values.

For instance, though you are dealing with MNI (that is, one task per person in the group), you don't need an array variable and a subprocess to update the values in the database. If you shield the PV (from parallel executions) properly, a single (that is, non multiple) PV and a simple Write to Data Store Entity (not MNIed) is far more sufficient.

Offcourse, choosing a multiple PV and thereby a subprocess to make the updates, also works, but it's not the only way. Provided if you are able to implement the Shielding PV from multiple flows concept, your design looks simple and clean from the MNI, intermediate events, subprocess nodes etc.