Contents
Before You Start
Where to Find the Workflow Badge
Understanding What You See
Differentiating Workflow Changes from Manual Edits
Frequently Asked Questions
1. Before You Start
You will need:
Access to any CRM record that has had changes (Accounts, Contacts, Potentials, etc.)
At least one active workflow configured to update a field on a record
The migration script must have been run on your instance by your system administrator
Access requirements: This feature is available to all CRM users who can view the Updates tab on a record. No additional permissions are required.
If the workflow badge does not appear after triggering a workflow, contact Dazos support to confirm the database migration has been applied to your instance.
2. Where to Find the Workflow Badge
The workflow name appears in the Updates tab on any record detail page.
To access it:
Open any CRM record (for example, a Contact, Account, or Opportunity).
Scroll down to the tab panel at the bottom of the record.
Click the Updates tab.
Look at the timeline entries — each entry shows who made the change and when.
For changes triggered by a workflow, you will see a blue badge immediately after the "Updated" or "Created" text, showing the workflow's name.
Tip: The Updates tab shows the most recent changes first. If a workflow just fired, its entry will appear at the top of the list.
3. Understanding What You See
Each entry in the Updates timeline contains:
Element | Description |
User name | The CRM user whose session was active when the change occurred (for workflow triggered changes, this is typically the system admin) |
Updated / Created | Whether this entry represents a new record or a field edit |
Workflow badge | The name of the workflow that triggered the change (only shown for workflow-triggered events) |
Field changes | The before and after values for each field that was modified |
Timestamp | Date and time the change occurred |
Example of a workflow-triggered entry:
Admin User Updated [Send Welcome Email] — Status changed from New to Active
Example of a manual edit (no badge):
Jane Smith Updated — Description changed from "" to "Follow up scheduled"
4. Differentiating Workflow Changes from Manual Edits
The blue badge only appears when a workflow performed the change. Use this to quickly answer questions like:
"Did a user set this field, or did our automation do it?"
"Which of our workflows fired on this record?"
"When did workflow X last touch this record?"
Scenario | What you see |
User manually edits a field | Name + "Updated" — no badge |
Workflow updates a field | Name + "Updated" + blue workflow name badge |
Workflow creates a related record | Badge appears on the new record's Updates tab, not on the triggering record |
Change happened before this feature was deployed | No badge (historical entries are not backfilled) |
Important: If a workflow creates a new record (for example, a Task), the workflow badge appears on that new Task's Updates tab — not on the record that triggered the workflow. Open the created record and check its Updates tab to see the workflow reference.
5. Frequently Asked Questions
Q: I triggered a workflow but I don't see the badge. What's wrong? The migration script may not have been run on your instance yet. Contact your system administrator or Dazos support to apply the update. Historical changes made before the feature was deployed will not show a badge.
Q: The badge shows a user name, not a workflow. Why? If the workflow performs an action other than directly updating a field on the triggering record (for example, creating a Task or sending an email), the badge appears on the record that was written by the workflow, not on the record that triggered it.
Q: Can I click the workflow badge to open the workflow? Not in this version. The badge is display only. To view or edit the workflow, go to Settings → Workflows and search by name.
Q: Will old change entries get workflow badges added retroactively? No. Only changes made after the feature is deployed on your instance will include the workflow name. Entries created before the migration are unaffected and will continue to display without a badge.
Q: The same record shows multiple "Updated" entries from different workflows. Is that normal? Yes. If multiple workflows fire on a single record save (each meeting its own conditions), each workflow's field changes are recorded as a separate entry, each with its own badge.
Q: Does this work on all record types? Yes. Any module that shows an Updates tab benefits from this feature — Accounts, Contacts, Potentials, Leads, and all other standard modules.
Q: Can I filter the Updates tab to show only workflow-triggered changes? Not yet. All changes continue to appear in the same chronological list. The badge is a visual indicator only.
Need Help?
If you run into issues:
Check whether the workflow badge appears on a recently-saved record that you know was touched by a workflow.
Confirm with your administrator that the CRM-2910 migration script has been applied to your instance.
Contact Dazos support with the record ID, the workflow name, and the timestamp of the expected change, referencing ticket CRM-2910.