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 …
I was recently posed a question about how to make a URL in a textbox be automatically clickable.
I’ve posted in the past about using hyperlinks in the Clarify Client, but this question was a bit different.
For example, on the Account form in Clarify, there is a web site textbox.
If you type in a URL in that textbox, it is automatically turned into a clickable hyperlink.
Lets say that you wanted to do something similar on a custom form.
You add a textbox to the form, set its contextual object properly, type in a URL, and then – nothing.
It’s not automagically converted into …
I introduced the term Canned Response into that post, as the original request sounded a lot like the Canned Response feature that we recently added in Dovetail Agent.
Other terms for this include snippets, templates, and saved replies.
The original request was:
Is it possible to assign a keyboard short cut for case notes field so we can auto populate certain text that is very repeatedly used.
There’s nothing out of the box within the Clarify Client to insert commonly used text within a case note. Depending on what you want to do, it’s …
It’s easy to fall into the thinking that we want our customizations within Dovetail Agent to look and behave the same exactly as how they are within the Clarify Client. While there are advantages to this (familiar app, less training, etc.), I think it’s worthwhile to revisit your customizations and take the opportunity to improve them where it makes sense.
Within Clarify, there are some constraints that often cause customizations to have to be done a certain way. Within a web application like Dovetail Agent, we also have some constraints, but they’re not typically the same constraints that we had with the old …
There are times when Rulemanager will report a bad time_bomb in the system. Although it’s easy to just ignore when this happens, it’s better to diagnose the issue to understand (and resolve) the root cause.
This post will walk through an approach to troubleshooting bad time bombs.
Recall that a time_bomb record is created when events happen in the system, such as a case being created or closed, workflow actions (dispatch, accept, assign, yank), etc. Rulemanager is responsible for picking up these time bombs, and comparing them against the defined business rules in the system, to see if something should happen, such as a notification.
Time Bombs Gone Bad
On occasion, Rulemanager will report a bad time_bomb. This will typically show up in the Rulemanager log file. It may also be reported via email, if your …
I’ve talked in the past about how to create custom events in Clarify/Dovetail, and how to fire business rules based on these events.
In short, code needs to be written that creates a custom activity log and time bomb.
A recent webinar covered details on how to do this: http://www.slideshare.net/gsherman/advanced-business-rules-part2 (starting on slide #18)
For additional info, take a look at the “User-defined Business Rule Events.doc” available on the Rulemanager wiki: http://rulemanager.wikispaces.com/How-To
If you also want to create a custom act_entry record, you’ll probably want a custom activity code. Here’s an example: https://gist.github.com/1042796
One of our customers recently wanted to do something similar, but for Change Priority of a case. They wanted to be able to fire a business rule when the priority of a case changes. They needed …
This will probably be old news to most of you, but there’s always new people getting exposed to Clarify, so I figured it couldn’t hurt to share.
If you’ve worked with the Clarify Classic Client for any amount of time (say, more than a day), you’ve probably run into the scenario where things start to misbehave. Often, this is because the Clarify cache files get corrupt. The fix is to delete those cache files, and restart the app. The cache files will get rebuilt during app startup.
What gets cached?
Mostly what gets cached is:
Schema (data from the ADP tables) is cached in the <databaseName>.0XX file, where XX is your schema revision. Example: testdb1.062 Forms and other metadata is cached in the <databaseName>.cfy file. Example: testdb1.cfy ClearBasic Code is cached in a boatload of files in the CBCache directory …
One of my favorite features of a Clarify/Dovetail system is the business rule.
Business rules, particularly notification rules, are a cornerstone of staying up to date on what’s happening in your system, and making sure nothing falls through the cracks.
As we’ve been doing more and more Clarify System Health Checks for customers, I’ve observed that many organizations are either over-using or under-using business rule notifications.
When there are too many notifications, they become noise, and are simply ignored.
I’ve observed many users who have setup email filters/rules that automatically file those emails away, or even delete them.
With the overabundance of emails that we all get, we’re forced to attack the email problem in some way – and that typically means ignoring everything that’s not critical.
Except emails from my Mom. And foreigners …
The task at hand is to be able to click on a URL (such as clarify://case/12345) and that will open case 12345 in the Clarify client.
Custom URL protocols
In Windows, you can create your own custom URL protocols, which allow you to register an application to a URL.
In my previous post, I introduced a clarify:// URL protocol. Lets see how we can make that URL trigger the Clarify Client (clarify.exe)
Basically, you create a registry key that maps the URL to the application.
And you’re URL will be passed to the application as a parameter (that’s the %1).
Here’s a sample registry entry for this:
Windows Registry Editor Version 5.00
@="URL: Protocol handled by CustomURL"
So, when I call a URL of clarify://something, clarify.exe will be started and the URL …
Most of you know that there a bunch of command line options available for the Clarify Classic Client.
Some of the more common ones include:
cbtrace CBDebugger clfy waggle debug debugCB msg nocache sqlhint sqllog
But did you also know you can pass your own parameters and evaluate them?
Lets take a simple example
Lets start clarify, passing in a case ID number. We’ll do this by coming up with our own custom URL format.
Custom URL Format? OMGWTFBBQ!
Everyone’s familiar with URL formats such as:
But we can also define custom URL formats, such as:
Not that it does anything, yet. But it looks cool, no?
Back to clarify.exe params
OK, so lets pass that as param to clarify.exe
From a command line, start clarify.exe with that custom URL …