There are three ways to implement this functionality:
1. Create trigger on status change and call method that sets "System task" status complete.
2. Create trigger on status change and call method that attaches Event to "System task". Event has macro that sets task status complete (this one is my favorite).
3. Create attach event macro and attach repeating event to "System task" that checks change status and sets task status when change status is 'BUILD'. Currently don't have test system so didn't test this third option. This approach is less favorite because of bunch repeating events.
Original Message:
Sent: 01-22-2020 11:34 AM
From: DEREK Johnson
Subject: Classic Workflow initiation delay
Appreciate the response. I guess the question then is what is the best way to 'complete' the task? Is this done through a trigger against the Status and some spel or is there a more succinct way?
Original Message:
Sent: 01-22-2020 05:32 AM
From: Sigitas Grincevicius
Subject: Classic Workflow initiation delay
Hi,
You create new task e. g. "System task" before Approval tasks. And complete this task when Change order status is 'BUILD'. You can even configure that some roles won't see "System task".
Original Message:
Sent: 01-21-2020 06:35 PM
From: DEREK Johnson
Subject: Classic Workflow initiation delay
Clarity Service Management version 17.2
We have a request to implement a Classic workflow to a change order category with just a few Approval tasks. These approvals can only occur after specific attributes have been entered by the ticket Assignee. These attributes are not required initially, they become required once the Status changes from 'RFC' to one called 'BUILD'. How can we delay the firing of the first workflow task until the ticket Status is updated to 'BUILD'? Or is there another way to tackle this?