Client-side scripting

In many ways, Client Scripts are very similar to business rules, which, as we saw in the previous chapter, run in the instance. Both Client Scripts and Business Rules run JavaScript against a specific table, one record at a time. However, instead of triggering at database access, Client Scripts add interactivity to a form. When specific events happen on the page, such when a field changes, when the form loads, or when a UI Action is clicked on, the Client Scripts will be evaluated. These actions can all cause the JavaScript code of your choice to run. In the majority of cases, the scripts will use the GlideForm functions.

Client Scripts can run in four different scenarios:

• onChange: When a field is edited in a form
• onLoad: When the form is displayed in the browser
• onSubmit: When a UI Action is clicked on in the form
• onCellEdit: When a field is edited in a list

As with business rules and Script Includes, the platform gives a script template to use.

Note

Client Scripts are supported...