A few months ago I wrote about copying change requests
Service-now allows administrators a lot of flexibility in defining which
One of the great features of Service-now.com is its CMDB and relational mapping. You can easily set up relationships between any CIs in the system. Once the relationships are defined, it becomes very simple to pull up a visual representation of a CI and its dependencies by using Service-now BSM maps. Using this feature allows an end user to look at that CI and identify what else in the environment is impacted by an outage or a change to that CI.
Standard JavaScript provides 3 different types of popup boxes: Alert box, Confirm box, and Prompt box. Since Service-now.com supports standard JavaScript, these popup boxes can be used anywhere in the application where client-side JavaScript is supported. They will most commonly be used in an 'onSubmit' client script or a UI action with the 'Client' checkbox checked.
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.
There are a variety of ways to implement copying functionality...
