Script Execution in ServiceNow: An In-Depth Look

To execute a script in ServiceNow, it is important to know the exact sequence of events and by exploring this process in detail, we can make some fascinating discoveries that will deepen our understanding of script execution in ServiceNow.

The process of modifying a record in ServiceNow involves several key steps. We start by opening a form that displays the record we want to modify. Then, we edit the record's content and submit the changes using the form. Finally, we wait for the form to return with the updated data.

Different colors are used to represent different types of ServiceNow artifacts. "Scratch" indicates access to g_scratchpad, which is reset to an empty state when the form is submitted, so the g_scratchpad from the second Display Business Rule starts new.

While attempting to determine the precise sequence of all the steps involved in this process, several interesting observations were made:

1. Setting values in g_scratchpad through a Display Business Rule makes them accessible in ACLs.

2. It's worth noting that g_scratchpad remains available throughout the client's work until submission. This means that it can also be used to track client-side activity like a client state parameter.

3. Data Policies are executed at the "Before Business Rule" order number 1000. This means that they are executed after all Business Rules with order values less than 1000 and before all Business Rules with order values greater than 1000. It's essential to be aware that Business Rules executed before may interact with the checks performed by Data Policies.

4. Flows are executed after the data is committed to the database, unlike Business Rules and Workflows, which are executed before the data is saved. They allow you to automate tasks and integrations between ServiceNow and other systems.

5. The Script includes in ServiceNow can be invoked by Business Rules or any other server-side scripts. Therefore, their execution order is not fixed and depends on the server-side entity that calls them.

Note: This article is a successful collaboration of various insightful and thought-provoking pieces of content that I came across on LinkedIn and other sources.