Upgrade Guide and New Features

In This Chapter

Upgrading RuleManager

Version 2.4.0

Version 2.3.0

Version 2.2.1

Version 2.2.0

Version 2.1.0

Version 2.0.0

Version 1.7.0

Version 1.6.0

Version 1.5.1

Version 1.4.4

Version 1.4.3

Version 1.4.2

Version 1.4.1

Version 1.4.0

Version 1.3.0

Version 1.2.6

Version 1.2.5

Version 1.2.4

Version 1.2.3

Version 1.2.2

Version 1.2.1

Version 1.2

Version 1.1.9

Version 1.1.8

Version 1.1.7

Version 1.1.6

Version 1.1.5

Version 1.1.4

Version 1.1.2

Version 1.1.1

Version 1.1

Version 1.0.4

Version 1.0.3

Version 1.0.2

Version 1.0.1

Version 1.0

Next

Installation and Configuration

Upgrading RuleManager

To upgrade to the latest release:

  1. Stop the RuleManager service.
  2. Backup your configuration file (FChoice.RuleManager.WindowsService.exe.config).
  3. Uninstall the previous version (using Control Panel - Add/Remove Programs).
  4. Install the current version.
  5. Merge in any of your custom configuration settings to the new configuration file
  6. Start the RuleManager service.

Version 2.4.0

Enhancements

Upgrading to Version 2.4.0

Version 2.3.0

Enhancements

Bug Fixes

Requirement Changes

Upgrading to Version 2.3.0

Version 2.2.1

Bug Fixes

Version 2.2.0

Enhancements

Upgrading to Version 2.2.0

This version requires a database schema change. Follow the instructions in Update the Clarify Schema to apply the schema changes.

Version 2.1.0

Bug Fixes

Version 2.0.0

Enhancements

Version 1.7.0

Enhancements

This default image will be used when an inline image cannot be retrieved:

"Image Not Available" Image

Version 1.6.0

Enhancements

Version 1.5.1

Enhancements

Bug Fixes

Installer

Dependencies

Version 1.4.4

When RuleManager sends a log email, it will now update the email_log record. The information is pulled from the outgoing email, and will update the sender (email_log.sender) and subject (email_log.x_subject, if that field exists).

Added EmailServiceConfig.DefaultFromEmailAddressDisplayName configuration setting. This setting allows the display name to be set for email notifications.

Removed LicenseInstaller.exe from the installation package. All license installation should be performed with the LicenseInstaller that ships with Dovetail SDK.

Version 1.4.3

IsIn Condition Evaluation Update

Fixed a bug for the IsIn Condition where parenthesis in the list values would cause the values to not be recognized correctly.

Version 1.4.2

IsIn Condition Evaluation Update

Fixed a bug for the IsIn Condition where spaces between the list values would cause the values to not be recognized correctly.

Dovetail SDK updated to 3.3.3.

Version 1.4.1

Property Evaluation Enhancements and Fixes

Version 1.4.0

Important: This release of RuleManager requires Microsoft .Net 4.0 Full edition.

Dovetail SDK updated to 3.2.3.

RuleManager can now sign outgoing emails when an digital certificate is present. This feature can be enabled via configuration.

Property expansion : added support for rule properties that use the focus_obj2act_entry relation which traverses from the focus object to act_entry when those two tables are related via the fact-participant model.

Version 1.3.0

RuleManager will now support sending email notifications to contact and employees who have multiple email addresses in their email fields. For example if a contact has "contact@domain.com, alternate@homemail.com" their email field they will receive mail at both addresses. These email addresses can be delimited by comma, semi colon and white space.

Version 1.2.6

The name of the RuleManager windows service is now "DovetailRuleManager" (was RuleManager). 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.

Fixed bug where activity entries being created by scheduled application events were not being enlisted into the current database transaction.

Version 1.2.5

Fixed bug related to property evaluation

Version 1.2.4

Fixed two bugs related to the intrinsic property "Current Queue Memberships"

Version 1.2.3

Dovetail SDK updated to version 2.4.6

Version 1.2.2

Version 1.2.1

Version 1.2

In this release we focused on adding support for Amdocs 6 thru Amdocs 7.5.

No changes to the rule processing were required, but Dovetail SDK has been updated since it was upgraded to support the new database enhancements.

Version 1.1.9

Fixed a regression introduced in 1.1.8 that caused the RuleManager service to stop when sending email to an invalid address. This situation will cause the application event's escalation time to be forwarded to the far future.

Version 1.1.8

When evaluating rule conditions where the operands cannot be coerced to the specified operand type. The condition's operands will be treated as type string.

Added ApplicationEventExecutor.StopApplicationIfEmailServiceIsDown configuration setting. This setting allows you to avoid stopping RuleManager if the Email Server goes down.

Version 1.1.7

Added EmailServiceConfig.Timeout configuration setting to the allow control of the number of seconds until sending an email will timeout.

Version 1.1.6

Added more verbose logging when failing to send an email.

Version 1.1.5

This release makes Dovetail RuleManager compatible with Amdocs Rulemanager's expansion of the [Current Queue Members] property. The [Current Queue Members] property now excludes the queue supervisors from the list of queue members.

Version 1.1.4

Sending emails with attachments that exceed the server message size limit will now be sent without attachments. An error log will be generated when this situation occurs. The email message body will be prepended with this message:

Attachments in this email have been removed due to the message size limit of the senders email server.

Version 1.1.2

Fixed a bug when executing a command line process whose argument values contain newline characters.

For example, sending a page (using the NotificationConfig.PagerApplicationPath) when the message to be sent contains newlines would cause an error such as Cannot start process because a file name has not been provided. This has been fixed.

Version 1.1.1

Fixed an issue where RuleManager was not processing business rules on objects that were not defined in a built-in list of standard objects. For example, business rules would properly fire for "case", "contact", etc. However, if a business rule was created on a "modem" object or on a "x_my_custom_table" object, then these rules would never fire. This has been fixed.

Version 1.1

Note: The configuration file (FChoice.RuleManager.WindowsService.exe.config) changed in this release. Specifically, a new spring context element (EmailLogDataAccess.config) was added. You must use this new config file when upgrading, and edit it for your environment.

Version 1.0.4

Fixed database verification to ensure proper version of MSSQL database is being used.

Version 1.0.3

Fixed issue when sending an email to a local invalid mailbox. This could cause many duplicate emails to be sent to the valid recipients, and could also cause the RuleManager service to shut down.

Version 1.0.2

Fixed issue with the "CC List1" Intrinsic property. It was missing from the list of known properties, which could result in a warning such as: No property "CC List1" was found in intrinsic XML properties

Version 1.0.1

Fixed an issue with the condition operator expecting the left operand property to always expand into whichever type the right operand was.

Version 1.0

Initial Release

Upgrade Guide and New Features