We just noticed this functionality, where the Reassign button is not available on forms for the initiator, until they re-access the task from their Tasks List. I can replicate this in a simple model with one user input task chained from the start node, reassign permissions set to 'can reassign to anyone'. When you start the process from Actions, only the Save button is visible (even for system admins). If you immediately click Tasks, and load the same task again, from there, the Reassign button appears.
I can't seem to find anything similar on the forum regarding that functionality, and the 19.1 documentation does not note any situations reassign would not appear other than permissions, which are the same in both situations above.
Has anyone else experienced the same issue?
We're currently on Appian 19.1
Discussion posts and replies are publicly visible
We are in 19.2 and we also see the same behaviour, i assume that the reassignment option displayed only when the task is opened from Tempo>tasks tab.
I'd really like to understand this use case better.
If there's a typical need for someone other than the process initiator to work on the "first" interface - isn't this really describing the "second" step of the process, in which the initiator passes the form on to someone else? That would be handled with a submission of the current form followed by restarting the form (or starting a different form) assigned to a different user.
Hey Robert, sure thing. Note this is not an issue with only the first interface - create a small PM with 3 chained user input tasks, no start form, chain to the first as well from the start event. As you step through the 2nd, 3rd tasks, the reassign button does not become visible until the task is re-loaded from your tasks list. For example in a supply chain process we run, "buyers" may initiate the process, step to the 2nd form when items are entered from the PR. If the catalog returns an issue with a item, they may have to reassign the task to another buyer to resolve. Typically we would accomplish this with task reassignment permission configuration, but if the tasks are chained from the start event, we have to implement a work-around by manually creating the reassignment logic, adding a bit more to already-busy forms, or, train users to re-load the task (not a great UX).
I just figured I would check with the community if it was a reportable defect, as we have been on an older version, 19.1. Today I was able to test on 19.4 with a freshly updated server, it is repeatable there so I did end up logging this with support as #492729.
Any thoughts welcome, thanks!
Just a thought, in your use case, if they know there is an issue and they need to reassign, could you not add a button or text fields to collect the info and submit the task and then either assign a task to the party or (ideally) to a group where someone could pick it up. That way you keep the metrics is a good place with that person's completion of tasks (lag time, completion, etc) and not fault them for the need to reassign, Let them complete their work and let it flow as a step to where it needs to go.
Just a thought...
I can understand the desire for a more seamless experience, being able to leverage the default behavior for a reassignment.
From Appian's perspective, the reassign behavior is triggered when a task is assigned to a group of people. Any one of them is eligible to accept the task, and once they do they can hand it off to someone else who was eligible or give it back to the entire pool of potential assignees. This didn't happen in the case of a chained activity. Think of it as the process automatically assigning it to a specific person and starting it in the same instant; not a group of people.
It skips the part where you can accept or reassign and kind of presses the accept button for you automatically. In general, it's far more efficient to skip all of that because the intent is almost always one person completing all the forms in that setup. I can see from your use case how it might be interesting addition to the Appian product to let you configure a task to run the default accept / reassign even if you're chained into it, but that's not a feature Appian currently has.
You could recreate the reassign functionality for now. It's not going to be as seamless, but there is also something to be said for having many options for performing the same function. Sort of like how there's a contextual menu and keyboard shortcuts that both copy and paste in Windows. Multiple ways of doing the same thing can add to user experience.
Thanks All - and yes we do have custom reassignments built in where necessary, just confirming product functionality. Appian confirms this is expected behavior due to overriding task assignments with activity chaining, and reassignment permissions do not come along from the process model security settings via the start event. E.g., no one should be able to reassign any chained initial tasks regardless of permissions (including system admin).
docs.appian.com/.../Process_Model_Recipes.html