How change Tasks are dependent on one another ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2014 02:42 AM
When I submit a change request, 4 tasks from the workflow gets created on that change request. And that 4 tasks(Planning task, Build task, Test task, Implementation task ) are dependent on one another, i.e. initially Planning Task is in "Open" state and rest all the tasks are in "Pending" state. So when we change the state pf "Planning task" to "closed complete", the build task comes in "Open" state. I want to customize this task dependency, could anyone please guide me from where i can achieve this ?
Thanks,
Gaurav

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2014 03:57 AM
Hi Gaurav,
I hope this link will give you the required information needed.
https://wiki.servicenow.com/index.php?title=Creating_a_Change_Management_Execution_Plan
Please let me know if you have any questions.
Kindly mark your question as answered if this resolves your issue.
Thanks and Regards
Pradeep Sharma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-09-2014 08:50 AM
Thanx pradeepksharma

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2014 06:25 AM
Hi Guarav,
Take a look at the workflow editor and examine your change workflows. The default "Comprehensive Change" and "Emergency Change" workflows each generate four tasks as you described.
If you open the workflow activities for these tasks, you'll see a "Wait for completion" checkbox.
This is what makes the workflow engine wait on that task before moving on to the next. Use the workflow editor and the properties of these activities to customize the task order and whether they are dependent on each other.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-09-2014 08:52 AM
Thanks josh.nerius