Client Status

Status indicators that client-side JavaScript uses to instruct server code to run or not run:

For example, if a client-side JavaScript script (which might be activated by a command button) determines that a user entered alphabetic rather than numeric data, the server-side JavaScript script does not run until the user enters the data correctly.

You use ActiveSection.ClientScriptStatus indicators, which take Boolean values, to coordinate actions between objects.

You use Object.ClientScriptStatus indicators, which take Boolean values, to initiate actions for objects. Object is a placeholder for the object name; for example, CommandButton1.ClientScriptStatus is a valid status indicator. Independent objects are subject to the script status settings of ActiveSection.

Table 229. Behavior of Status-Indicator Settings in EPM Workspace

Indicator Value

ActiveSection.ClientScriptStatus

Object ClientScriptStatus

True

Server-side scripts are initialized when client-side script execution concludes.

Client-side scripts are initialized when the browser page is refreshed.

Client-side scripts are initialized when users perform a required action, such as clicking a button.

False

No server-side script is executed.

No server-side script is executed.

For example, consider a dashboard that contains a password field and Submit and Cancel buttons. The password field contains a client-side script that requires an alphanumeric password of at least 6 characters. If ActiveSection.ClientScriptStatus is false (the user entered the password incorrectly) and the user clicks Submit, the password is not sent to the server. However, the Cancel button can reset ActiveSection.ClientScriptStatus to true and enable cancel logic, that is implemented at the server level, to run.