Author__c

Loads the original record from the database or initializes the record for an upsert statement.

Loads the new record field values from the request and overwrites the old values.
If the request came from a standard UI edit page, Salesforce runs system validation to check the record for:

• Compliance with layout-specific rules
• Required values at the layout level and field-definition level
• Valid field formats
• Maximum field length

Executes record-triggered flows that are configured to run before the record is saved.

Executes all before triggers.

Runs most system validation steps again, such as verifying that all required fields have a non-null value, and runs any custom validation rules. The only system validation that Salesforce doesn't run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.

Executes duplicate rules. If the duplicate rule identifies the record as a duplicate and uses the block action, the record is not saved and no further steps, such as after triggers and workflow rules, are taken.

Saves the record to the database, but doesn't commit yet.

Executes all after triggers.

Executes assignment rules.

Executes auto-response rules.

Executes workflow rules. If there are workflow field updates:

• Updates the record again.
• Runs system validations again. Custom validation rules, flows, duplicate rules, processes, and escalation rules are not run again.
• Executes before update triggers and after update triggers, regardless of the record operation (insert or update), one more time (and only one more time)

Executes escalation rules.

Executes the following Salesforce Flow automations, but not in a guaranteed order.

• Processes
• Flows launched by processes
• Flows launched by workflow rules (flow trigger workflow actions pilot)
• When a process or flow executes a DML operation, the affected record goes through the save procedure.

Executes record-triggered flows that are configured to run after the record is saved.

Executes entitlement rules

If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure.

If the parent record is updated, and a grandparent record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the grandparent record. Grandparent record goes through save procedure.

Executes Criteria Based Sharing evaluation

Commits all DML operations to the database

After the changes are committed to the database, executes post-commit logic such as sending email and executing enqueued asynchronous Apex jobs, including queueable jobs and future methods.