|
|
|
In This Chapter |
Next |
Task Manager Extension is a new extension that will process messages received from Dovetail Rulemanager. These are typically part of the Dovetail Task Manager process.
The message will specify a type of Run Task Set, a Task Set Name, and a Case ID. The Task Manager extension will execute each Task within the given Task Set. This includes dynamic property evaluation and workflow.
In addition to its main out-of-the-box process of creating subcases, Dovetail Task Manager is an enabling technology, meaning that it supports messages flowing into Carrier, where custom functionality can reside. For example, this would enable the Dovetail system to invoke custom code within Carrier, such as calling into another system via a web service.
Task Manager Extension requirements:
Upgrading to Version 2.0.0
For incoming emails, save the email message id to the email log record.
When adding attachments, relate the attachment record to the email log record.
Upgrading to Version 1.4.2
If using the EmailAgent Extension, the unique message id of incoming emails will be added to the email log. To add this behavior, a custom database column, x_id, needs to be added to the email_log table. Follow the instructions in Update the Clarify Schema to apply the schema changes.
Updated the Dovetail SDK dependency to version 3.3.7.7
Updated Email Agent Extension to use the email subject when logging emails to cases and subcases.
Resolved an issue where a single email message sent to multiple email addresses that are being monitored by Carrier could result in the message being processed multiple times, and in some cases, throw an error when trying to read the .eml file to access attachments within the email.
Added documentation and installation folder for Reprocessing Failed Messages.
Upgrading to Version 1.3.4
If using the EmailAgent Extension, the subject line of incoming emails can be added to the email log for the target case/subcase. To add this behavior, a custom database column, x_subject, needs to be added to the email_log table. Follow the instructions in Update the Clarify Schema to apply the schema changes.
Updated the Dovetail SDK dependency to version 3.3.5.35
Resolved issue with the DovetailCRMSettings.AttachmentMode setting not being honored.
Fix issue where emails with an empty subject would throw an error.
Fix issue where emails without any recipients would throw an error.
Fix Email Agent Extension to handle incoming emails with an empty To field.
Resolved a log4net assembly binding issue.
Resolved the error "Could not load file or assembly ADODB" when Dovetail SDK was not installed on the same machine as Dovetail Carrier.
Added support for multiple email addresses. Simply use a list of comma-separated email addresses in the EmailAgentExtensionSettings.EmailAccountUserName setting:
<add key="EmailAgentExtensionSettings.EmailAccountUserName" value="account1@company.com,account2@company.com"/>
Updated the help text for carrier-diagnostics.exe to be correct for configuration file changes made as part of version 1.2.
Infrastructure update to the latest version of the underlying message bus and windows service technologies being used.
Removed the Twitter extension example as it has not been working due to Twitter API changes.
Improved the code responsible for turning HTML emails into plain text.
A number of small logging changes.
Log Email now truncates sender and recipient details if they will not fit into their database fields. The original values are logged as warnings.
Log Email operations now populate the email_log.cc_list field with any CC data from the incoming email.
Log Email operations now populate the email_log.x_subject field (if this field exists) with the subject from the incoming email.
The act_entry record for Log Email and Create Case operations are now related to the contact (if found) who sent in the incoming email.
emailService.config and email-accounts.config files have been removed. The settings from those files are now included in DovetailCarrierService.exe.config.
This simplifies configuration, and also allows for encrypting of sensitive information, such as email account usernames and passwords, as well as database connection information.
For more information on encrypting configuration files: https://support.dovetailsoftware.com/selfservice/solutions/show/619
Requires Microsoft .NET version 4 (4.0 or 4.5.x)
Fixed an issue related to the scoping of database transactions when consuming messages with rule sets.
Reverted to behavior where Auto Destination happens as a separate message after creating a case. The option is present to do Auto Destination in-line with the create case rule set. The reason we restored this behavior is that in the event of a locking issue with auto destination. This new behavior will allow the case to be created.
Storing email attachments now supports configuring the strategy used for selecting the directory structure when storing the file.
Email Agent Extension's Auto Destination action now happens during creation of new cases. Previously auto destination was evaluated separately as part of its own ruleset.
Added a email configuration settings diagnostic command line tool to assist administrators in verifying configuration settings without having to start up the Dovetail Carrier Windows service.
Fixed a bug which was causing SMTP authentication issues with Exchange 2010 email servers.
The Communications extension is no longer installed by default.
The previous release was missing a logging support assembly.
Added additional debugging support.
Email service settings now have a SmtpSslMode configuration setting allowing better control over how secure connections with SMTP servers are negotiated.
Pop3 and IMAP connections using secure connections in Manual mode were not properly starting the secure connection.
Added better logging around email connectivity.
Fixed a bug affecting Oracle users where the Dovetail SDK did not want to initialize properly.
Updated the Dovetail SDK dependency to version 3.2.3. This update contains many bug fixes but notably for Dovetail Carrier it corrects a few database transaction related bugs.
Restored the zipped Dovetail Carrier extension source code which was accidentally excluded.
Added better control of how secure IMAP and POP3 connections are made see email account configuration for more details.
Fixed bug where the email account port configuration was not being used.
Previously only one message consumer was processing incoming messages. The default is now two times the number of processors. This setting is now configurable.
Many Dovetail Carrier extensions use regular expressions to allow for configurable message handling. Regular expression evaluation now has a configurable timeout to avoid rare occurrences where complex regular expressions fail to evaluate in a timely manner.
The name of the Dovetail Carrier windows service is now "DovetailCarrier" (was DovetailCarrierService). This change has been made across all our products with Windows services for consistency. Please be aware that this change may affect service monitors or automation scripts.
Doing a better job managing database connections across RuleSet executions.
The MailBee email support library has been updated to version 6.2.
Log4Net default settings now include thread details in log output.
Carrier will now use Dovetail SDK application settings when they are present.
When converting the contents of HTML email bodies to text we now have better whitespace handling
Detection of bounced emails has been improved.
With this release we are introducing a new extension included with Dovetail Carrier : Email Agent. The Email Agent Extension has similar functionality to the FreeForm mode of our stand alone Dovetail Email Agent application.
Added support for email accounts which use the IMAP email protocol. We have renamed the pop3-account.config file to email-accounts.config to reflect this. Please move the pop3Account configuration elements from your old pop3-account.config into the new configuration file.
Also included in this release with the extension source code are two new examples: a simple Clock example and Twitter Agent.
The Clock example extension is a comprehensive yet simple sample showing how to publish and consume messages.
Twitter Agent demonstrates Email Agent like functionality while using the direct messages within the social networking service Twitter as the medium rather than Email.
Extensions assemblies are now marked with the DovetailExtension attribute. During application startup any assembly having this attribute found in the Dovetail Carrier application directory is configured as an extension.
The email publishing service is no longer started up automatically. Dovetail Carrier is now more intelligent about Message Publishing Services. A Message Publishing Service for a given message type will automatically be started when there are rule sets defined for the message type.
A message published into Carrier having no subscribers will be removed. Previously such a message would forever sit in the message queue.
Dovetail SDK updated to version 2.4.8.
Dovetail SDK updated to version 2.4.6
Fixed a regression that caused line returns to be stripped from HTML emails.
Tracking Ids are now removed from the title of communications created from incoming emails.
Poorly formed HTML content within incoming emails was causing email content to get truncated after unescaped angle brackets. This issue has been corrected for content in <pre> tags.
Additionally Html to Plain text conversion no longer strips line returns from Html content.
Outgoing communications emails were not getting CC and BCC recipients added to the email.
Dovetail Carrier was being too strict when retrieving email communications regarding the type of electronic address medium.
Updated Dovetail SDK to fix activity entry details when creating dialogues.
Updated the version of the Dovetail SDK to correct a bug which prevented dialogues and communications from being updated when they are closed.
This is the initial release of this product.