How to call script include in UI Action (2024)

FAQs

Can we call client script in UI action? ›

To change a UI action to run client-side script, we first need to check the client field tick box. This brings up some additional fields, including the checkboxes to select which list versions the UI actions will be compatible with, but the main new field we are interested in is called onClick .

A Script Include is a reusable piece of JavaScript code that can be called from anywhere in the ServiceNow platform. Rather than defining condition criteria in an individual UI Action, it's possible to instead define the condition criteria on a Script Include, then call it from a UI Action.

If we want to call another script include within existing script include or current script include then we use gs. include('another script include name'). This is actually very helpful and avoid writing same code again and again in every script include.

Run a UI script from a form

To run a UI script on a form, create a formatter. In the associated UI macro, include a g:requires tag and specify the name= parameter as the name of the UI script followed by the . jsdbx extension. Add the formatter on the form view.

The code shown here would be wrapped in a function ( onLoad, onSubmit, onChange ) depending on the type of Client Script. In this example the GlideAjax object is used to call the Script Include and pass in parameters.

UI Policies execute after Client Scripts. If there is conflicting logic between a Client Script and a UI Policy, the UI Policy logic applies.

- Yes, you can have a single UI Action that runs both Client-Side and Server-Side code. This is necessary sometimes, for example in the case where you want to check additional conditions or gather additional information from the user After he clicks the UI Action but Before you pass control back to the server.

Create script includes to store JavaScript functions and classes for use by server scripts. Each script include defines either an object class or a function. Consider using script includes instead of global business rules because script includes are only loaded on request.

The syntax to call a Script Include depends on scope - A scope prefix is not required to call a Script Include in the same scope var conflict = new ItineraryConflict(); - To call a Script Include in another scope, prepend the Script Includes name with its unique scope namespace to distinguish it from other Script ...

What is the difference between script include and business rule? ›

Script includes run only when called by a server script. https://docs.servicenow.com/bundle/geneva-servicenow-platform/page/script/server_scripting/concept/c... Business rule: A business rule is a server-side script that runs when a record is displayed, inserted, updated, deleted, or when a table is queried.

Calling a Business Rule from a UI Action offers an added level of flexibility and capability. By employing a Script Include, developers can bypass the 255 character limit constraints on the Business Rule Condition field, and create more complex and nuanced conditional logic.

In simple words we can say UI-Script is a global client-side javascript code which we can call or run from other client side scripts, such as client scripts, UI Pages, UI Macro, HTML code etc.

Do minimal work in the UI action, and let business rules react to it. Not only does this make it easier to debug the UI action and the business rule, but it also makes the logic available elsewhere in the system by calling the business rule.

UI actions are generally considered to be a server-side script, but they can also run as client-side script, too. We will cover an introduction to UI actions and their basic usage in the server-side basics in the next chapter.

According to the UI Policy documentation, “You can also use client scripts to perform all of these actions, but for faster load times use UI policies when possible.” If, however, you start getting into more complicated form behavior and neither UI Policy Actions nor UI Policy scripts are working for your use-case, move ...