If you receive a business rule notification message, but you’re unsure as to exactly which business rule it came from, there’s a few ways to find the originating rule.
For example, lets say that you received the following notification:
How do I find which business rule caused this notification to be sent?
There’s actually a few options here.
1. Dovetail Agent – Query Business Rule Actions
Using Dovetail Agent, create a query for Business Rule Actions
And filter for Message Contains something happened
This will show you a list of rules that contain that string in the message.
Clicking one of the results will take you to the Business Rule itself.
2. Dovetail Agent – from the History
If you know the work item (Case, Subcase, etc.) that the notification pertains to, then you …
A few years ago I wrote a post titled Getting the most out of your business rules. Most of the information in that post is still relevant today.
In that post, I discussed how we can analyze the data inside our database to see which rules are firing and how often. We can do this using a Business Rule Usage Report.
This report tells us what business rules are firing along with how often. Perhaps even more importantly, it allows you to see the rules that are not being fired. Perhaps those rules could be removed, or made inactive, therefore simplifying business rule administration. Or maybe they should be firing, and need further investigation.
One of the available extensions within Dovetail Carrier is the Parent-Child Cases Extension, which allows for automating workflow processes involving parent and child cases.
Quick Refresher on Parent and Child Cases
With parent and child cases, we can relate a group of similar problems with a root cause. The parent case identifies the root cause. A child case is a customer problem that arises due to the root cause and is linked to the parent case.
For example, suppose someone knocks out a utility pole, which causes an internet outage for many customers.
Each customer may call into the call center and report the outage. We can relate all of these cases to a parent case, which is where the repair is being tracked. Updates on the …
We’ve recently added support for Configuration Item Rule Properties in Dovetail Rulemanager and Dovetail Agent. In this post I’ll cover what they are, why you’d want to use them, as well as a few examples.
First, a quick refresher on Rule Properties and Config Items.
Business Rule Properties are used in a number of places throughout the Dovetail suite, including:
Business Rule ConditionsBusiness Rule Action MessagesCanned Response VariablesEmail Log Templates
Traditionally, a rule property would traverse a path through the schema, starting from the base object, and ending at a column.
For example, the Contact First Name property for a case would use the path case_reporter2contact:first_name.
However, there are instances where a static value may be desired, and this static value cannot be traversed to via a schema path. In these …
When employees are notified as part of a business rule action, the notification method is determined by the employee’s notification preference.
The default notification methods are:
EmailNotifierForward to my SupervisorTone PagerText PagerDigital PagerNone
Dovetail Rulemanager recently added support for one additional option: SMS
An SMS notification will send an SMS message (text message) to an employee’s configured device, typically their mobile phone.
Users can set their notification preferences for SMS, just like any other preference.
Couldn’t we do this before?
In the past, if you wanted to send SMS messages, we would typically use a custom replacement paging application for Rulemanager. This custom script would call into a 3rd party web service, or use the cell provider’s email to SMS gateway. These solutions all required …
We recently added a new extension to Dovetail Carrier – a Webhooks Extension.
What’s a webhook?
Webhooks are “user-defined HTTP callbacks”. They are usually triggered by some event, such as pushing code to a repository or a comment being posted to a blog. When that event occurs, the source site makes an HTTP request to the URI configured for the webhook. Users can configure them to cause events on one site to invoke behavior on another. The action taken may be anything.
This allows for making a web request based on an event within your Clarify/Dovetail system. A business rule can fire based on the event. Dovetail Rulemanager will evaluate the rule, and send a message to Dovetail Carrier. With the webhooks extension, that message …
I’ve often stated that Rulemanager and Business Rules within Clarify/Dovetail are the most powerful (but often underused) components of the system.
And when you combine Rulemanager with Dovetail Carrier, it gets even more powerful.
To demonstrate some of this power, I’ve created a collection of business rule recipes that will educate and inspire you to make the most of your business rules.
There’s over 30 business rule examples, and they stretch across a number of areas, including:
User NotificationsWorkflow AutomationCustomer NotificationsIntegrating with third-party services/appsTask ManagerCalling external apps/scriptsSLA Rules (Service Level Agreement)Bonus!
There’s also a Business Rule Template, which is helpful when defining new business rules.
It can be provided to business users, who can fill out the template and submit it to the technical staff.
This Collection of Recipes and the Business Rule Template is completely free.
Simply click …
Recently I discussed function-based rule properties, which allow you to add your own code for calculating a rule property value.
The property can be defined as a function using the Rule Property UI within Dovetail Agent.
But if you’re not using Dovetail Agent, but you are using Dovetail Rulemanager, you can still take advantage of these.
Rule properties are stored in table_prop_name. There is a new custom field named x_is_function that defines this property as a function. If set to 1, this property will be evaluated as a function. If set to 0 (default), it will not be.
So you can simply …
When talking about calendars, notifications, and SLAs – questions around calendars and holidays often arise.
So lets explain how they work within Dovetail apps.
Lets start with Business Calendars. They define the work hours.
For example I may have a business calendar named “M-F 9-5” with the following work hours:
Monday 9:00 AM – Monday 5:00 PMTuesday 9:00 AM – Tuesday 5:00 PMWednesday 9:00 AM – Wednesday 5:00 PMThursday 9:00 AM – Thursday 5:00 PMFriday 9:00 AM – Friday 5:00 PM
Business Calendars can be setup using Dovetail Admin.
Now lets setup the Holidays.
Using Dovetail Agent, navigate to the Admin page, and click on the Holidays icon:
We recently released Dovetail Agent version 14. Here’s a run-down of the highlights.
User-Configurable home page
Users can now set their home page to be any page within the app – such as a queue or a query.
For example, perhaps you’re a manager who doesn’t work cases. In this case, you may wish your home page to be My Workgroup’s Open Items or one of your custom queries.
By default, Home is the same as My Work.
To set your home page, use the s+h keyboard shortcut while you’re on any page in the app. Or set it on the User Preferences page.
Clicking the Home icon (or using the g+h keyboard shortcut) will take …