Personal rules
Business rules that belong to you rather than to the instance, and fire in your browser on your saves only.
A rule is a background script plus a trigger. The trigger picker only appears on that kind, because it is the only one the extension fires.
Nothing is installed on the instance. The rule lives in your account, fires in your browser, on your saves only. Nobody else is affected, and it travels with you across instances.
That is the whole point of the feature. The check you want on every incident you touch is usually not a check the customer wants on every incident anybody touches, and having to ask for a real business rule to get it is how you end up not having it.
Triggers
| When | Fires |
|---|---|
load | When a form on the chosen table opens |
beforeSave | When you hit save, before the save goes through. A rule with a window can hold the save, then continue or cancel it |
afterSave | Once the save has landed |
manual | Never on its own. You run it from the panel |
Condition
An optional JavaScript expression, evaluated against a current-like object with table_name,
sys_id, fields and getValue(field):
current.getValue('state') == '3' && current.getValue('priority') == '1'
A broken condition never breaks your save. It is logged, and the rule is skipped. A tool that can stop you saving because of a typo in its own settings is a tool you cannot leave switched on.
With and without a window
A rule with only a server script runs silently. A rule that also has markup in its Modal tab opens a window, which is where the modal API comes in.
For a rule fired by a trigger, the server script also receives every field value from the form and the moment it fired, so it does not have to read back what is already on screen.