What operation is a record undergoing?

This evaluation will pass if the current record is undergoing the specified operation and will fail if the current record is undergoing any other operation.

Evaluations have two automation triggers associated with them : Then and Else. Actions under the “Then” automation trigger execute when the evaluation passes, and actions under the “Else” automation execute when the evaluations fails.

Record operation evaluations are used to execute a set of actions if the current record is undergoing a particular operation, and another set of actions if the current record is undergoing any other operation.

Example : Suppose an application contains a table called Contact. When Contact records are added, certain starting, or default, values should be set into fields on the Contact, but subsequent updates of a Contact should leave these fields as they are. To accomplish this separation a builder would create a record operation action on the Contact table's automation trigger and check for the “Add” operation. Under the “Then” trigger the builder would create a series of set field value actions, and leave the “Else” trigger empty.

Choose an operation to evaluate for. The Add, Edit, Delete, and Recycle options specify an operation the record must be undergoing to pass. Not Add, Not Edit, Not Delete, and Not Recycle will pass when the record is not undergoing one of those operations. For example, Not Add would pass if the record was undergoing edit, delete or recycle.

Useful as a comment, this description will overwrite the automatically generated description in the Action Manager.

When an action is queued, the subsequent actions continue to process without it. Meanwhile, the queued action and its children process separately. Queue actions that you don't want a user to wait for.