
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-08-2019 03:07 AM
Hello,
We use the Standard Change Templates heavily and many of them have tasks linked to them.
However, all the tasks get triggered at the same time.
How do set the tasks so they trigger in a specific order?
I have change the Order numbers but that does nothing. What I need is for tasks to be triggered one after another or some at the same time.
Help appreciated.
Thanks
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2019 03:17 AM
Hi
Yes, this is exactly what the excution plans can do, without implementing a workflow (which is of course also the more flexible option).
I created an Execution plan under
> System Policy > Service Catalog > Execution Plans
You need to define, that the tasks will be attached to the "change_request" table (see field "Parent Table").
Then, when I create a new Change Request, the execution plan will be used automatically to attache the tasks to the new Change Request..
after Saving the new change request, the tasks will be attached automatically (see screenshot below):
All Tasks are now in state "Pending", but as soon as you fill in the assignment group an click on "Request Approval", the Change is waiting for approval.
If then, the change gets approved...
... the first task becomes "Open"
This way working through the tasks, should put them "active" in sequence.
Let me know, if that works for you, and mark my answer as correct and helpful,please.
BR
Dirk

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-08-2019 06:18 AM
Hi
What do you mean with "to be triggered in sequence"?
Do you want to keep some tasks in state = "Pending", and set them to "Open" as soon, as the "predecessor" is set to state = "Closed", or cancelled?
Let me know...
Edit:
I just found an interesting article for you:
https://old.wiki/index.php/Creating_a_Change_Management_Execution_Plan
Maybe that is already exactly what you need.
Let me know, if that solves your issue, and mark my answer as correct and helpful, please.
BR
Dirk
BR
Dirk

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-08-2019 06:22 AM
Hi Dirk,
What I mean is, say I have 10 tasks on the standard change.
What I would like it:
Tasks 1,2,3 to go our immediately
4,5,6 to go out when 1,2,3, are completed
and 7,8,9,10 to go out when 4,5,6, are completed
Is this possible and if so how?
Thanks
Riaz

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2019 03:17 AM
Hi
Yes, this is exactly what the excution plans can do, without implementing a workflow (which is of course also the more flexible option).
I created an Execution plan under
> System Policy > Service Catalog > Execution Plans
You need to define, that the tasks will be attached to the "change_request" table (see field "Parent Table").
Then, when I create a new Change Request, the execution plan will be used automatically to attache the tasks to the new Change Request..
after Saving the new change request, the tasks will be attached automatically (see screenshot below):
All Tasks are now in state "Pending", but as soon as you fill in the assignment group an click on "Request Approval", the Change is waiting for approval.
If then, the change gets approved...
... the first task becomes "Open"
This way working through the tasks, should put them "active" in sequence.
Let me know, if that works for you, and mark my answer as correct and helpful,please.
BR
Dirk

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2019 01:21 PM