- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 03:35 AM
In the change task state i have replaced 'close skipped' with 'close failed', In the workflow if 'wait for condition' is checked and the state of task is either closed complete or incomplete the flow will complete the task and execution moves forward but how can make the workflow to go forward even when the states value is 'closed failed', in short i want the attributes of closed complete and incomplete to be added to closed failed.
Many Thanks
- Jayanth
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 04:07 AM
Ah, I think I may understand a little better now. No, do not modify the TaskStateUtil script include. That controls how all tasks behave.
It sounds like you created a new state and value (I'll assume the state value is 11 in this case.)
What you need to do is update the dictionary entry on the table to include your new state value "11" in the close_states attribute so TaskStateUtil treats it the same as the default 3, 4, 7 values (setting Active=false when you get to it, triggering any closure business rules, etc.)
http://wiki.servicenow.com/index.php?title=TaskStateUtil#gsc.tab=0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 04:04 AM
There was a script include mentioned in 'mark closed' business rule called 'TaskStateUtil'. Should i make any changes in that?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 04:07 AM
Ah, I think I may understand a little better now. No, do not modify the TaskStateUtil script include. That controls how all tasks behave.
It sounds like you created a new state and value (I'll assume the state value is 11 in this case.)
What you need to do is update the dictionary entry on the table to include your new state value "11" in the close_states attribute so TaskStateUtil treats it the same as the default 3, 4, 7 values (setting Active=false when you get to it, triggering any closure business rules, etc.)
http://wiki.servicenow.com/index.php?title=TaskStateUtil#gsc.tab=0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 05:00 AM
Hey Chuck can you please elaborate because i was unable to find close_state in the dictionary entry.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 05:08 AM
Hi,
This should prove helpful if you're not familiar with adding or updating dictionary attributes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 05:13 AM
Thank you!!