August 15, 2018
Dovetail Carrier has a number of extensions that greatly enhance your Dovetail/Clarify system. One of the more recent extensions is the AutoDest Toolkit Extension. AutoDest Toolkit Extension This extension allows for automatically assigning or dispatching workflow objects based on an auto-destination rules. Typically, these messages will originate from Dovetail Rulemanager (such as from a business rule action), although they can also originate from custom applications as well. Example Message type=CallToolkit toolkit=AutoDest method=execute ObjectType=case Operation=DISPATCH Id=12345 This example would evaluate the DISPATCH auto-destination rule for case 12345, and if a destination queue is found, the case would be dispatched to that queue. Auto-Dest Rule Here's an example of an auto-destination rule: (calltype2gbst_elm:title = "Equipment Repair") -> "Equipment Repair"; (calltype2gbst_elm:title contains "Payroll" ) -> "Payroll"; (calltype2gbst_elm:title contains "Benefits" ) -> "Benefits"; (title contains "Benefits" ) -> "Benefits"; objid > 0 -> "Support…
Automatically routing cases using Dovetail Carrier’s AutoDest Toolkit Extension
August 15, 2018
Dovetail Carrier has a number of extensions that greatly enhance your Dovetail/Clarify system. One of the more recent extensions is the AutoDest Toolkit Extension. AutoDest Toolkit Extension This extension allows for automatically assigning or dispatching workflow objects based on an auto-destination rules. Typically, these messages will originate from Dovetail Rulemanager (such as from a business rule action), although they can also originate from custom applications as well. Example Message type=CallToolkit toolkit=AutoDest method=execute ObjectType=case Operation=DISPATCH Id=12345 This example would evaluate the DISPATCH auto-destination rule for case 12345, and if a destination queue is found, the case would be dispatched to that queue. Auto-Dest Rule Here's an example of an auto-destination rule: (calltype2gbst_elm:title = "Equipment Repair") -> "Equipment Repair"; (calltype2gbst_elm:title contains "Payroll" ) -> "Payroll"; (calltype2gbst_elm:title contains "Benefits" ) -> "Benefits"; (title contains "Benefits" ) -> "Benefits"; objid > 0 -> "Support…
August 6, 2010
Great changes are happening with our Dovetail Seeker search product. I wanted to talk about a core change to the product. By moving our application architecture to use messaging we are seeing increased flexibility, testability and performance. Why Messaging? Based on our experience building Dovetail Carrier (pdf), our messaging oriented enterprise integration solution, we decided messaging was a great fit for Seeker’s search indexing windows service. We decomposed the indexer’s behaviors into work (message) producers and consumers. For example to keep your database in-sync with the search index we have a service which watches the database for changes to the objects Seeker is indexing. When a database item is added or updated a message is created which gets put onto a work queue. We have many message consumer threads standing by waiting for work to munch on. Our message consumers…