Workflow FAQ Compendium

Q. When a Business Button edits data, does it trigger workflows set to run on change?

A: After adding a Business Button or a UI Button and configuring fields, whether an operation triggers change-based workflows depends on the button type and how it interacts with workflows/approval flows and data persistence.

• Business Button: Business Buttons are typically tied to specific business processes or data operations. When a Business Button operation completes, edited field values are automatically saved (precondition: the object is not configured to trigger approvals on edit). By default, this will trigger workflows that run on field changes/field updates.

• UI Button: UI Buttons are generally used for interface interactions (e.g., action controls) and have weaker ties to the system’s core business processes and data storage. When a UI Button operation completes, edited field values are not saved, and thus it will not trigger workflows that run on field updates.

Q. Does the workflow notification tab support permission control?

A: No. The workflow notification tab does not support permission control. Once a user receives a workflow notification message, that page/tab remains visible to them and cannot be hidden. There is no filtering supported on this tab.

Q. Workflow is configured to send reminders to the data owner but they didn’t receive it — why?

A: Workflow notifications must be checked in the workflow message tab; they are not sent to the CRM notification tab.

• You can also troubleshoot the workflow execution via the Process Report. The trigger logs will show why a match failed.

(Note: “Report” is used per the standard term mapping.)

Q. When a workflow triggers, under what conditions will it skip deactivated employees?

• Trigger evaluation: If the trigger condition uses operators such as “before change”, “after change”, “equals”, “contains”, or “belongs to” and the selected user is a deactivated employee, the workflow will not trigger.

• Post-action reminders: If a post-action reminder targets a user who becomes deactivated before the post-action executes, the reminder will not be sent to that deactivated user.