• Published On: October 9th, 2013

    A few weeks ago I came across an issue involving

  • Published On: January 31st, 2013

    One very common service request or change request approval requirement

  • Published On: February 22nd, 2012

    A couple of weeks ago, I saw a great idea

  • Published On: December 14th, 2010

    While this article is still extremely useful as an example

  • Published On: October 20th, 2010

    Service-now.com provides a really cool Graphical Workflow engine to help

  • Published On: August 16th, 2010

    A common Graphical Workflow requirement in ServiceNow is to tell

  • Published On: January 12th, 2010

    This post is written in response to a question I

  • Published On: December 29th, 2009

    It is very common to use graphical workflow to help facilitate some change management process within your organization. One common requirement in change management is to be able to cancel or close the change request at any time during the process. "Simple", you say. "Just allow the user to change the value of the 'State' field to 'Closed'." You would not be incorrect in saying something like that, but you would be forgetting about part of the problem with closing or canceling a change request or other task ticket.

  • Published On: December 28th, 2009

    When implementing the Change management process in Service-now you'll probably encounter a scenario where your entire change workflow (including all tasks and approvals) needs to be reset. The first option to consider (assuming you're using the graphical workflow engine to manage the tasks and approvals) is the Rollback workflow activity. The rollback activity works great for a lot of scenarios, but what if you don't have a defined point in the workflow where everything should be rolled back? What if the rollback (or reset) can happen at any point in time? There's not really an easy way to handle this within the workflow itself since you would need to check for a rollback condition at an infinite number of places.