• type of entity being secured
• operation being secured
• unique identifier describing the object

Can be defined by roles, conditional expressions or scripts.

• Ajax Client Scripts request that information be returned, or that action be taken, or sometimes both
• Ajax Server Scripts fulfill Ajax Client Script requests

• client - Ajax Client Scripts run on the client
• server - Ajax Server Scripts run on the server

• runs when a database action occurs (query, insert, update or delete)
• the script may run

• before or after the database action is performed (runs as part of the database operation)
• asynchronously (at some point after the database operation)
• on display (when displaying the data in a form)

• client - scripts in the "execute if true" field or "execute if false" field run on the client
• server - all conditions run on the server

• onLoad means the Client Script runs when the form or page is loaded
• onChange means the Client Script runs when something specific gets changed AND also when the form or page loads
• onSubmit means the Client Script runs when the form is submitted

Client Scripts can also be called by other scripts or modules, including UI Policies.

• approval is cancelled
• change is approved
• problem is assigned

Can have a condition which must be true for the script to run. Commonly used to call a Script Include.

Any server script which is complicated or reusable should be a Script Include (especially complicated Business Rules).

• defines mapping relationships between tables
• can use Business Rules, other scripts and/or other options to import that data

Do not always include scripts.

UI Actions put these items on forms and lists:

• buttons
• links
• context menu items
• list choices

• client - when the "Client" box is checked, the script in the script field runs on the client
• server - when the "Client" box is unchecked, the script in the script field runs on the server
• client - when the "Client" box is checked, the Onclick script is available, which can can contain any JavaScript but normally calls a function which is specified in the script field
• server - all conditions run on the server

Note: If you use a left-handed mouse configuration, right-click means "click the other button."

• client - onShow scripts run on the client
• client - action scripts run on the client
• server - dynamic action scripts run on the server
• server - all conditions run on the server

Note: Jelly turns XML into HTML.

• server - the UI Macro itself executes on the Server
• server - may contain content that runs on the server (Jelly expressions or JavaScript inside Jelly constructs)
• client - may generate output that runs on the client (embedded JavaScript within <script> tags)

Can contain

• Client Scripts,
• processing scripts (which are server scripts),
• HTML,
• Jelly,
• UI Macros,
• and also can call other scripts.
  

Note: Jelly turns XML into HTML.

• server - Jelly XML runs on the server to produce HTML
• client - HTML may contain embedded JavaScript that runs on the client
• client - client scripts run on the client
• server - processing scripts run on the server

• mandatory
• visible
• read only

Use UI Policies rather than Client Scripts whenever possible.

• UI Policies are always attached to one table
• UI Policies often have a condition which must be true in order for them to run

• client - scripts in the "execute if true" field or "execute if false" field run on the client
• server - all conditions run on the server

• server - properties set on the server
• client - the results get rendered on the client
  
  

no scripts

Not recommended for use.

For example, a validation script can verify that the only value allowed in a specific field is an integer.

Scripts also can be found inside every workflow activity and can be modified (although do so with extreme caution).