Client Script

Client Scripts make "real-time" changes to the appearance of the user interface, especially forms

Client Scripts can be created to do the following:

Automatically update the location field to reflect the value (user) entered into the caller field

Disable the attachment link of a closed record when the form is loaded so a user is unable to add or modify attachments

Display a notice at the top of the page to confirm a catalog request was submitted

Client Scripts execute on the client side

Client Scripts allow for browser/form manipulation and verification such as making fields visible on a condition. An example of this would be an alert appearing when a user changes the priority of an incident. Client Scripts get executed on the browser, but you may also run a Client Script when a database lookup is needed; if you think you need database info, and you need the info frequently (such as every form load) then ask: Is it a field you can add to the form but hide? Is it something you really, truly need?

Several types of scripts are supported:

• onCellEdit(): runs when a cell on a list changes value through use of the list editor

• onChange(): runs when a particular field changes value

• onload(): runs when a form is loaded

• onSubmit(): runs when a form is submitted

Unlike onload() or onSubmit() scripts, onChange() scripts apply to a particular widget on a form, rather than to the form itself. They are fired when a particular value on screen changes. An on load() script runs when a form is first drawn and before control is given to the user to begin typing. Typically you use an on load() script to perform some client side manipulation of the document on screen. An onSubmit() script runs when a form is submitted. Typically you use an onSubmit() script to validate things on the form to make sure the submission makes sense. As such, onSubmit() scripts can potentially cancel a submission by returning false.