RE: Regarding MNI

Richard — Thu, 10 Jan 2019 16:49:22 GMT

It sounds like you desire to have a single task assigned to each member of the group, but once a certain condition is met (e.g. database fields are updated, or a certain threshold of people have accepted and fulfilled), then the remaining tasks should collapse and no longer be assigned.

I'm not certain that MNI is a good solution either, as paulc919 has suggested. For generating multiple tasks you have two options. MNI or tick the flag to generate one task for each assignee. But both vary slightly in how they execute and you'll need to read a little on how they both work.

However, one solution might be to have an orchestrator process that is launched at the same time as the tasks, that uses the Task Services (it may be a plugin) to run a task report and actively cancel tasks that are no longer needed.

Be aware however that this may have a negative impact to user experience, as the user's whose tasks are cancelled will likely have been notified of a task assigned to them, containing a task link, but if the task is cancelled and they subsequently click that link they will receive a message indicating that the task is no longer available.

Much depends on your desires, and in the case of database updates, how you choose to perform those updates. If you can supply more information, it will help the community provide a better answer

RE: Regarding MNI

paulc919 — Thu, 10 Jan 2019 10:19:29 GMT

Hi Aswini - there should be no need to use MNI in my opinion. If you've assigned a task to a group then all members of that group will receive a notification from Appian that there is something needing their attention. When the first user goes into the task and accepts it, all other users in the group will no longer be able to see the task. Assuming of course that the task is asking for the first user to update all the relevant items on the screen.

Hope this helps.