A common workflow is to have a business rule fire, and that business rule will send Dovetail Carrier a message.
For example, when a customer updates a case via SelfService, we can have a business rule fire that sends an SDK Toolkit message to Carrier, and Carrier will change the case status to “Customer Update”.
Complete end-to-end Testing
When I’m putting this all together, and testing it out, a full integration test would be to log into SelfService, and log a note to a case. That would cause Rulemanager to fire a business rule which would send the message to Carrier, then Carrier can do its thing. So I have multiple apps in play here:
Dovetail Agent, for setting up the business ruleDovetail SelfService, which is …
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 …
I’ve blogged before about the Filter Config and Filter Overrides within Dovetail Agent.
I totally dig this feature, as it makes it super easy to customize the queries within the app without having to write code.
We know it’s easy to show data that comes from a database column within the query results – such as a contact’s name or phone number.
But what if we wanted to show something that is more dynamic? i.e. something that needs to be calculated?
For example, in the result set for contact queries, what if we wanted to show the number of open cases that a customer has?
There’s not an existing field in the database that contains this data. The number of open cases needs to be summed up.
So how can we do this in a …
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 …
We recently released a major update to the Dovetail SelfService app. There’s SO many great new capabilities here.
I would group these enhancements into 2 major categories:
Dynamic Content, Pages, and Menus – making it easy to create and edit content throughout the app Knowledgebase Enhancements – making the knowledgebase much more prevalent, approachable, and functional
Lets take a run through the highlights of this release.
Dynamic Home Page Content
When a user logs into SelfService, they’re immediately taken to the Home page.
In the past, if you wanted to change what was displayed on the home page, you would need to customize the HTML page content, and re-deploy the application.
Now, the home page content comes from a solution. So you can easily edit the solution using Dovetail Agent, and …
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 …
We recently added Themes to Dovetail Agent. Users can now pick a theme that fits their personal style preference.
We currently ship with 3 themes in Agent 18 (Default, Dark, and Quiet Light), and we’ve recently added a new Blue theme as well (part of Agent 19).
Dark ThemeQuiet Light ThemeBlue ThemeUser Preferences
Users can select their personal Theme preference from the User Preferences page in Dovetail Agent.
Customers may wish to develop their own theme – for example they may want a theme that mimics their corporate styles. We’ve greatly simplified the process for over-riding existing theme styles, and for creating new custom themes. The Dovetail Agent documentation covers this in detail.
In addition, one of our developers, Barrett Sonntag, has created a couple of …