When Should you Script

• Add new functionality
• Extend existing functionality
• Guide users
• Automate processes
• Interact with 3 rd party applications

Examples of when you should script:

• Update related record(s)
  • Cascade a comment from a master incident to its children.
  • Updating the ownership of a Configuration Item (Cl) after a Change Request.
• Approval Strategies
  • One or all does not meet your business requirement.
  • Approvers need to be set dynamically.
• Show/hide a form section.
• Scan a list of Cls to dynamically determine risk based on criticality.
• Recursively traverse the Business Service Management (BSM) map.
• Query database.
• Customize widgets.
• Change default behaviors.
• The list of examples shown above is representative of typical uses for scripting. There are, of course, no limits as to what one can do with JavaScript in ServiceNow. It all comes down to your requirements!

TIP FROM THE FIELD

ServiceNow is always enhancing the platform. For example, the Embedded Help has bee updated and a new feature called Guided Tours has been added. Research these options before you script a solution to guide users. If you have already scripted a solution, revisit your code and see if these new baseline options can replace the script.