Did records change?

This evaluation will pass if all of the records from the query have changed, and will fail if all of these records have not changed. A “change” occurs when at least one field associated with the record has had its value change during this operation. The “last modified date” field is excluded from this evaluation.

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 changed evaluations are used to execute a set of actions if certain records have changed, and another set of actions if those records have not changed.

Example : Suppose an application has the requirement of a high level of security, logging whom changes which records and when. To accomplish this, the builder can create a record changed evaluation on the automation trigger at the table level that is triggered when records in that table are updated, and check for the records' change. If it has changed, then run the appropriate actions to create an Audit Change record recording that this record was changed, what time and by whom.

Use the query builder to define which records to evaluate for a change.

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.