January 29, 2010
In Clarify, Logistics and Quality both use transitions to determine how a request moves from one condition to another. To change a condition, a transition must be defined between the two conditions for that part request type. To restrict access to critical part operations, you can administer permissions according to privilege classes. In complex installations, the number of transitions across both business areas can easily reach the imposed limit of 256 transitions. This limitation can truly impose headaches when the transitions cannot be accurately configured to match the business process. Dovetail Admin can also be used to configure the transitions, and now it does not enforce the same limitation. It does use the same mechanism for storage, so a little bit of work needs to be done to allow more transitions to be set up, and using Dovetail Agent (or…
Transitioning Beyond 255 Transitions
January 29, 2010
In Clarify, Logistics and Quality both use transitions to determine how a request moves from one condition to another. To change a condition, a transition must be defined between the two conditions for that part request type. To restrict access to critical part operations, you can administer permissions according to privilege classes. In complex installations, the number of transitions across both business areas can easily reach the imposed limit of 256 transitions. This limitation can truly impose headaches when the transitions cannot be accurately configured to match the business process. Dovetail Admin can also be used to configure the transitions, and now it does not enforce the same limitation. It does use the same mechanism for storage, so a little bit of work needs to be done to allow more transitions to be set up, and using Dovetail Agent (or…
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…
July 14, 2009
Yesterday I added a feature that will be in the next release of Dovetail Seeker.Executive Summary: Coming soon, support for indexing against Clarify views.Didn’t it support that already?Well.. No. I was working on a feature for Mobile Agent that I wanted to use some cool search techniques to facilitate and found out a view would work better. When I tried to do just that the indexer exploded with nasty unfriendly errors. What is a developer to do but stop everything and add a feature.Does this great power come with any great responsibilities?Yes. Paths traversing relationships are not allowed when indexing views. What is a path? Well, paths are basically instructions telling the indexer how to find the piece of data you want in the index. Against tables paths can include relations which are not possible for views. This means you…
December 20, 2007
Our customer would like to query all the cases including a column with a calculated number of "open" subcases related to each case record. They want to query for all of the cases that have any open subcases. A normal view would not work because it cannot calculate the count of related object with specified condition. Steps taken. 1. We showed it could be done in SQL (See SQL below). Note the nested SQL statement to calculate the number of open subcases. select c.objid, c.id_number, cond.title, cond.title, (SELECT count(*) FROM table_subcase sc INNER JOIN table_condition sc_cond ON sc_cond.objid = sc.subc_state2condition WHERE sc.subcase2case = c.objid AND sc_cond.title LIKE 'OPEN%') as open_subcase_count FROM table_case c INNER JOIN table_condition cond ON cond.objid = c.case_state2condition 2. Created the following SchemaEditor SchemaScript. Case identifiers and condition and the count open subcases for the case…