MNI

RE: MNI

sarathkumar13 — Thu, 11 Jan 2024 03:53:36 GMT

If its a related action, the interface will be configured as process start form in the start node right. Not sure why you have given it after the start node. Please correct me if I am wrong.

RE: MNI

Mathieu Drouin — Wed, 10 Jan 2024 17:36:24 GMT

Yes, makes no sense to use MNI on a Related Action unless that action is triggering a bunch of tasks assigned to someone else.

RE: MNI

Komal Jain — Wed, 10 Jan 2024 17:18:22 GMT

If its Related Action , would advice to make the User interface task as non MNI , as there is no purpose of having MNI here and keep Assignment as pp!initiator

RE: MNI

David G. — Wed, 10 Jan 2024 15:16:36 GMT

MNI and chaining are basically mutually exclusive. Chaining says "keep the user with this one sequence of events"; MNI says "run multiple copies of this". So MNI nodes usually break chains, since you can't keep a user with a single process flow when you create more than one of them.

In this example, what I'd expect to happen is the user gets the "completed" message, but has multiple tasks assigned to them in their task queue, each of which allows them to fill out the user input task.

RE: MNI

Jones Prakash Selvaraj — Wed, 10 Jan 2024 15:11:52 GMT

Hi ,

Would you be able to explain your use case that why do we need a MNI configured in a user input task as a related action?

RE: MNI

Stefan Helzle — Wed, 10 Jan 2024 15:11:37 GMT

What is the purpose of making that starting user input task a MNI?