The Help Desk selects a custom status on Task 1 to trigger an action macro that assigns Task 2 to one of several possible support groups. This is done manually because location based auto-assignment does not work in Classic WF. Here is an example:
Help desk reviews the request and completes Task 1 to start the WF by selecting a custom status to assign subsequent tasks in the WF to the appropriate region.
For example, "Assign to Group A"
The Action macro on the custom status assigns Task 2 to Group A and flag Task 1 complete. Task 2 is naturally set to Pending status. However, because a custom status is used in Task 1, Start time in Task 2 is not triggered.
I have confirmed the cause is the custom status by using "Complete" as a status for Task 1 which adds the Start time as expected. Unfortunately, a OOTB statuses do not work when Task 2 has several possible assignee groups.
This is a sample of the action macro to assign all tasks in the WF to the appropriate regional support group:
macro::upd_val("cr_wf", format("cr = '%s' AND sequence IN (20, 200, 40, 400, 70, 700)", cr.persistent_id), 1, 0, "group", "A304829476469547BF028DD12C4B98E6");
Thanks
Jeff
>>> Lindsay_Estabrooks <communityadmin@communities-mail.ca.com> February 20, 2019 15:52 >>>
Lindsay Estabrooks replied to the discussion
"Re: CR Workflow Task start_date"
To view the discussion, visit: