Hi guys,
Encountered an interesting behaviour today in a workflow that encompasses a multitude of different process models. Each PM is a step in the process, and some steps are performed by different teams. E.g. Team A would perform a relevance check, then Team B would check if all is in order and either approve or send it back.
What I noticed is that sometimes Team A will not receive an automated email by Appian with their task, although they are the assignee in Appian and can navigate to it from there. And it seems that it has to do with how Activity Chaining and the checkbox for "Override assignment for the next attended activity even if the current user is not an assignee" in the flow properties is set up?
I tried to check the documentation for information / best practices in this regard, but didn't find anything pertaining to this problem. Would someone happen to know what the rules are and what pitfalls I should avoid when modelling such a workflow?
Best,
Matthias
Discussion posts and replies are publicly visible
According to documentation
I checked the process model and the flow has override active for each node except before the user input task (activity chaining enabled but override unchecked). This is true for all sub-processes step 1-7 (activity chaining+override on all nodes, except for flow leading to user task which has override unchecked). Step 8 is the supervisor task where activiity chain ends before the user task. Here, an email is sent of course.
What's the feasible solution here? Normally we want users to go from form to form seamlessly. Just check via XOR whether it was issued back and use different flow properties depending on that?