Base actions

A base action is a secondary action that is triggered by a primary or top-level action. A base action is automatically triggered by every other action (such as Nested actions, initialization, access control, validation, and commit) for that record type.

Base actions allow an action hook to be written once and then re-used with multiple actions. For example, writing a base action and adding a notification hook to send an e-mail causes an e-mail to be sent when any action is performed on the record.

Each step of an action (initialization, access control, validation, commit, and notification) executes the hooks of all base actions for that record type, followed by the hook for the main action itself.

A base action cannot be initiated directly by a user, so it is not displayed in the list of possible actions presented to the user in the Actions menu.

There can be multiple base actions for a record type. Some base actions can be added to a schema by the application of a package.

If a record has multiple base actions, they do not run in a specific order but always precede the main action that triggered them.

Note: Any access control restrictions placed in base actions apply to all other actions.