node assignment on re-entry into interface node

RE: node assignment on re-entry into interface node

mohamedt808 — Tue, 04 Sep 2018 09:47:30 GMT

hi, if it helps try using process variable in assignment tab .

RE: node assignment on re-entry into interface node

darrinw — Tue, 04 Sep 2018 04:23:48 GMT

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.

=if(

or(

rule!APN_isBlank(

pv!groupIdentifier

left(

pv!groupIdentifier,

) = "DUP",

pv!AmendmentDecision = "Amend"

if(

pv!AmendmentDecision = "Amend",

pv!businessTravelRequest.TravelAdministrator,

pp!initiator

pv!traveller

)

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.

RE: node assignment on re-entry into interface node

darrinw — Tue, 04 Sep 2018 04:05:49 GMT

Thanks, I looked at this but I think this is for when you initiate multiple instances at the same time (so each instance can be individually assigned). In my case the node is in a loop (of a sort) so the second instance can start some time after the initial one has already finished.

RE: node assignment on re-entry into interface node

amitm9 — Mon, 03 Sep 2018 14:38:47 GMT

Hi Darrinw,

You should use a Boolean flag for to identify 1st instance of flow or next instance initiated on receive message. Then create a user type process variable which will hold your assignee username as per business logic and Boolean flag. Hope this will work, give a try and let us know if it works. Thanks

RE: node assignment on re-entry into interface node

karthiks228 — Mon, 03 Sep 2018 12:19:04 GMT

Hi Darrinw,

Please refer the below link for node assignment of user input node.

docs.appian.com/.../Assignment_Tab.html

Regards,
Karthik S

RE: node assignment on re-entry into interface node

simples533 — Mon, 03 Sep 2018 11:57:26 GMT

Hi Darrin,

Can you please explain in more detail this scenario ? You want to change assignment when receive message event is getting triggered ? if so check variable value (based on what you need new assignee under assignment tab expression to evaluate) is updated after receive message event is getting triggered.

RE: node assignment on re-entry into interface node

Rahul Gundu — Mon, 03 Sep 2018 10:05:30 GMT

Hi paragk998

This option is useful, whenever you want to assign same task to each member of a group, or each user configured in variable.
Like one to one assignment. (Let's say 7 users part of a group. Task will create 7 instances and assign the task to each assignee. one task for a user)

RE: node assignment on re-entry into interface node

Rahul Gundu — Mon, 03 Sep 2018 09:59:55 GMT

Hi darrinw

Could you please let me know, whether the expression rule is updating a variable properly or not? If possible could you please post some screenshots? It will help to analyse?

I faced a scenario, user input task is configured in a sub-process and configured user input task assignment as process initiator and sub process assignment as ' who ever designed a process'. When a user run a new process, though the task is chained, it assigned to (process initiator and a user part of Application Admin group).

RE: node assignment on re-entry into interface node

paragk998 — Mon, 03 Sep 2018 07:21:52 GMT

hi
you can try checking ->

since you have more than 1 instance.