I'm on 18.1 and have a situation whereby I am using a receive message to re-enter a process in order to amend details. The assignment for the first interface node is set to a user based on an expression. This is happening correctly however the node is also getting assigned to the original assignee (from the first time this node was processed). I've been through the chaining in the process and removed the override assignment options, there is no lane assignment and the expression rule returns just a single user. Is there something I'm missing in the assignment process where it picks up previous assignees? Has anyone else had this issue?
hiyou can try checking ->since you have more than 1 instance.
Thanks Amit, the expression already does check what type of flow this is... see code snip. The pv!AmendmentDecision is only set via the receive message flow.
) = "DUP",
pv!AmendmentDecision = "Amend"
pv!AmendmentDecision = "Amend",
in my case the correct value is being set - i.e. pv!businessTravelRequest.TravelAdministrator but it is also retaining the original assignee for this node. In a simplified form the process is as attached... so the first time in to the "task in question" the assignment assigns the initiator, then when the receive message event is triggered the assignment assigns the second instance to the pv!businessTravelRequest.TravelAdministrator and also the initiator.
Discussion posts and replies are publicly visible
© 2020 Appian. All rights reserved.