REQUEST A DEMO

Blog

Let the system tell you where potential performance bottlenecks exist

January 15, 2007 A common cause of performance issues in database backed systems is poorly defined SQL, either a SQL operation that takes a long time to execute, or a SQL query that returns a large number of rows.Operations that take a long to execute can typically be corrected by database tuning, such as adding indexing, or changing the application logic so that the database can better optimize the operation.Queries that return a large amonunt of data can stress the application server & network. All that data needs to be transferred from the database to the application server, and in web applications, that data needs to then get transferred from the web server to the web client (browser).Typically, it's not that difficult to tune the database or tweak code once these situations are identified. However, it's not always easy to figure out where…

Email Integration with Clarify

January 12, 2007 Over the last 12 years of working with Clarify, email integration always seems to be a key topic of conversation, and I get many questions about email integration capabilities. So hopefully this post will answer most of these questions. I'm sure there will be details I've missed (especially on some of Clarify's later version capabilities), so please leave a comment. Outgoing Email Outgoing email is typically initiated via a Log Email action (for example, from a case) within the Client. When a email is "sent", the client saves the email details to the database, and then also adds a new time_bomb. This time_bomb tells RuleManager that it needs to send out this email. The Clarify client does not connect to a mail server or service, so it can not send the email, so RuleManager does it. On Windows, RuleManager connects…

Hello, world

January 11, 2007 The proverbial first blog post. I guess introductions are in order. Hello, my name is Gary Sherman, and I'm a Certified Clarify Developer...   Where to start? Perhaps with a just a touch of history. In 1995, while working for The MathWorks as a Technical Support Engineer (bonus points for identifying this image), I got involved in an implementation of our new Tech Support software - Clarify's ClearSupport. We purchased Clarify when it was version 2, but waited til version 3 (the Camelot release) before going live. Before long, I was the "Clarify Guy", responsible for all aspects of the Clarify system, from daily administration, upgrades, reporting, integration, customizations, etc.  In 1997, I went to work for Clarify as a technical consultant, where I spent the next 4 years working on Clarify implementations, including Made2Manage, Best Buy, Guaranty Federal Bank…

Top Ten Reasons to Switch from Clarify to Dovetail

Static image January 8, 2007 We surveyed users of Amdocs Clarify CRM systems to find out the primary reasons they incorporated, or migrated completely to, Dovetail Software’s CRM system, and their .NET platform, Dovetail SDK.   The following evaluations are in no particular order. Customer responses are edited for clarity. These are the ten most common themes we hear today, from mostly IT and some business folks.   1. DISTRIBUTION Dovetail’s cost per license is vastly lower than Amdocs Clarify. Dovetail’s agent-facing apps look and feel like Clarify, so no additional training is needed.   Comments: “awesome ability to expose data to the enterprise”; “now running twice the number of users on Dovetail, no way we could have done this with Amdocs”; “we were looking for a richer client-side experience.”   2. STRATEGY Eliminating Java, native applications written in .NET. Using thin clients.   Comments: ”.NET is our strategic platform going forward”;…