Workflow FAQ Compendium

Q: Does editing data via business buttons trigger workflow upon field changes?

A: The behavioral differences between [Business Buttons] and [UI Buttons] after configuration primarily depend on their functional design and their interaction with workflows & approval processes, as well as data persistence mechanisms:

• Business Buttons are tightly integrated with specific business processes or data operations. After execution, edited field values are automatically saved (provided the object isn’t configured to trigger approvals upon editing). By default, these will trigger field-change or field-update workflows.

• UI Buttons are primarily used for interface interactions, such as operational controls, with weaker ties to core business processes or data persistence. Edited field values won’t be saved after UI Button actions, and consequently, no field-update workflows will be triggered.

Q: Does the workflow notification tab support permission controls?

A: No permission controls are available. Once a user receives workflow notifications, this page remains permanently visible without options for hiding or filtering.

Q: Why aren’t workflow reminders being received by data owners despite configuration?

A: Workflow notifications appear exclusively in the Workflow Messages tab, not in the general CRM notifications tab.

• Additionally, you can review execution details via the Business Process logs. Trigger logs will explicitly indicate any mismatch reasons.

Q: When does a workflow trigger match deactivated employees?

• Trigger Conditions: When using “before change/after change” operators (equals, contains, belongs to) where the selected person is deactivated, the workflow won’t trigger.

• Post-Action Notifications: If a selected recipient in post-action reminders is deactivated, no notification will be sent during execution.