Workflow messaging is great, but it can be tricky to determine which specific rule triggered a notification. This usually becomes an issue when you have multiple workflow rules sending out messages every day.
In the past, it was really difficult to figure out which workflow rule was responsible for a particular message. However, ConnectWise has recently introduced a couple of new tools to make it easier to troubleshoot and identify which rule generated a given notification.
Workflows now come with an assigned Event ID, which you can find in the Workflow Rule list.
When you examine an audit trail, you’ll notice that each workflow action in the description includes its corresponding Event ID. By matching this information with the Workflow Rule list, you can easily troubleshoot and identify which rule was responsible for a particular action.
Tokens are now available for use within messaging actions:
- [workflowruleeveentid]
- [workflowrulename]
As demonstrated in the example, you can add these Event IDs to the message to help identify which workflow rule triggered it.
Tip: To keep these identifiers out of sight, you can reduce the text size. For extra discretion, you can also change the text color to a light grey or another subtle shade.
In summary, tracking workflow messages becomes crucial as your workflow rules grow in number and complexity. To make this task more manageable, ConnectWise has introduced Event IDs for workflow rules, allowing you to trace notifications back to their source. By including these Event IDs in message content and using subtle formatting tricks, like reducing text size or changing its color, you can keep your workflows organized without cluttering your message space. This approach not only simplifies troubleshooting but also enhances your overall workflow efficiency. With these new tools and strategies, you can maintain better control over your workflow processes and ensure seamless operations.
