Deliver Order from Chaos

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.

Recently I posted about how to notify the yankee, meaning the person who a case was yanked from.

Last we left off, we turned a pseudo relation into an exclusive relation.

Specifically, we created a participant2user relation, which allowed us to traverse from an activity to the user who participated in the activity with a path like: focus_obj2act_entry:fact2participant(role_code=1):participant2user:login_name

I was recently presented with an interesting business rule requirement from a customer.

the objective here is when someone closes a case, I can use Rulemanager to send an email to the related CR owner.

Lets give it a whirl.

Data Model

First, lets recall the data model.

Cases are linked to solutions (probdesc/workaround), and solutions are linked to Bugs (CRs, Change Requests).

The other night I got curious and inspired and started working on a Business Rule Usage Report.

This 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.

I ran it against our production system, and it was pretty enlightening.

Yuval over at NextGen Consulting has a couple of good posts on Data Paths and Expressions and Path Contexts.

Paths are classically used in RuleManager properties, aliases, and auto-destination rules. More contemporary uses include CBO queries, Smart Client forms, and routing rules.