Tag: bolt

Finding a Business Rule based on its message

September 26, 2017 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. Notification Message For example, lets say that you received the following notification: Email 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 Dovetail Agent - Query 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. Dovetail Agent - Query Results Clicking one of the results will take you to the Business Rule itself. [caption id="attachment_7594"…

Transform a Pseudo Relation into an Exclusive Relation

October 18, 2011 Recently I had the need to use a pseudo relation as part of a path evaluation (i.e. as part of a business rule path). But, the path evaluator can’t do this, because it’s not a “real” relation in the Clarify/Dovetail schema. Pseudo Relations I covered pseudo relations in my recent Schema 201 webinar, but lets give a quick review. A pseudo relation is a sort of schema hack that implements a relation using two fields. One field holds the type_id of the object that we want to relate to, and one field holds the objid of the object. These pseudo relations were a bit of a data modeling hack, before exclusive relations. Pseudo relations are nice, because we don’t have to create a new physical column for a relation, and we can relate to any other object in…

Case Aging, including “pauses”

October 7, 2011 Over the years of working with Clarify, I’ve seen a request come up a few times for calculating case aging, including “pauses”. It’s easy to calculate a total case age. For open cases, it’s the difference between now and the time the case was opened. For closed cases, it’s the difference between case open time and case close time. But what about the workflows where a case can be paused? For example, the customer may go on vacation, or any other myriad of reasons where we want to pause the clock on the case. The common approach to this from an application standpoint is to have a new case Status value of Paused (or something similar), so that we simply change the status to Paused to pause the case, and then change it to something else to…

Multiple email addresses for a contact or employee

June 10, 2011 In today’s modern age, many people have multiple email addresses. They may have a work email, a home email, a personal email, etc. I think I may have at least 1/2 a dozen. In Clarify (and Dovetail), there’s one field for specifying an email address. Back in 1990, it was uncommon that people had multiple email addresses, so a single field was sufficient. But what do we do when a contact has multiple email addresses? Where do we store that info? I’ve seen systems where multiple custom fields are created, such as: table_contact.x_home_email table_contact.x_work_email table_contact.x_alternate_email table_contact.x_alternate_email2 etc. Yuck. I’ve also seen systems where multiple email addresses are crammed into the one existing email field. Yuck again. How about… I think what would be useful is a table that allowed for many email…

Everyone play nice: BOLT, OLEDB, Oracle, 64-bit Windows

May 27, 2011 With 64-bit machines becoming more and more prevalent, we’ve seen some confusion popup around installing and using applications. Is the app 32-bit? 64-bit? which database provider do I use? Is my web app 32 or 64 bit? etc. It’s confusing. No doubt. tl; dr Short answer: If you’re on a 64-bit machine, and using Oracle, use the 64-bit Oracle provider for OLE DB for BOLT. 64-bit Windows explained There’s a great post from last year that “explains 64 bit”: Programs are still in the same place, in %ProgramFiles%, unless you need the 32 bit version, which is in %ProgramFiles(x86)%, except on a 32 bit machine, where it’s still %ProgramFiles%. All those dll’s are still in %SystemRoot%System32, just now they’re 64 bit. The 32 bit ones, they’re in %SystemRoot%SysWOW64. You’re with me so far, right? Oh, and the 16 bit ones…

Clarify Form Identifier (Or, What the heck Clarify form is that?)

January 6, 2011 On occasion, while working in the Clarify Classic Client (especially in a customer’s customized environment), I come across a form that I’m not familiar with (might even be a custom form) that I need to dive into the details of. Trying to find this form in UI Editor is not always easy. It’s common that the form name and/or title aren’t very descriptive (this even happens on baseline forms). So I typically have to start the Clarify client with some debugging and tracing switches, and examine the log file to try and find its form ID. This works, but I think there should be an easier way. An approach from the past One approach I’ve seen done in the past is to create a custom help file (CHM) that contains the form IDs. Then pressing F1 on a…

How do I know what ID to use for a new table or view?

September 18, 2009 When creating a new table or view in Clarify/Amdocs/Dovetail, a unique ID number must be supplied.How do I know what ID to use?Clarify has defined a range of numbers that are reserved for custom tables and views. They guarantee that they will not use any numbers in this range. So, you need to use a number in this range.There are two ranges reserves for custom IDs: 430-571 and 2000-4999. The rest are reserved for Clarify baseline use.So, you simply need to pick a number in that range that hasn’t yet been used.How do I know what numbers have already been used?The most common method is to export your schema, pick a number, and search your schema to see if its in use. If it is, pick another number, search again. Repeat until you find an available number.A better waySince our…

Migrate a business rule from one database to another

November 13, 2007 I was working with a customer today, and they mentioned that one task that is problematic for them is moving business rules from their test database into the production database. Currently, the business rule is manually created via the Clarify Client in the test instance, and then when its all working, it is then again manually re-entered into the production. Manual re-entry is a point of potential failure. The rule may have been perfect in test, but a simple typo when re-entering it in production can cause havoc.One solution to this issue is to archive the business rule using ArchiveManager or dataex from the test database, and then use ArchiveManager or dataex to import it into production.Business RuleFirst, I created a new business rule in my test system:Object Type:CaseRule Name/Description:New Employee RequestStart Event:DispatchCancel Events:NoneConditions:Case Type = New EmployeeAction Title:Create SubcasesMessage…