ER 4.3 Release Notes

ER 4.3 enhancements include:

Quick Match

Infogix ER Quick Match speeds the process of selecting items to create possible match sets based on match rules. The match determination is based on the rules definition. In Quick Match mode, the count of selected items, total left and right side amounts, and passing notifications for selected items are displayed on the status bar. This is much easier and faster way to identify manual match sets.

Under Quick Match mode, when user selects multiple items, Matching Rules defined for the Recon are evaluated against the selected Items. If the items meet matching criteria, they can be matched automatically by clicking the Match button. You can also click and drag the items to the New Match Set button to add them to the matching panel for further review and matching.

When Quick Match is “Off”, or when Items are not selected, no matching results are shown.

Recon Skip List

A dynamic configurable option allows you to configure a list of reconciliations that will be skipped during retention and purge processing. This list is configured using the recon IDs found on the Core Definition tab of the recon definition.

You may choose to add reconciliation to the skip list, for example, if you wish to run retention on several other recons without impacting the recon on the skip list.

If the purging jobs run and the skip list is configured with a reconciliation ID, an email notification and a log message is triggered to alert the administrator.

Chunk Size

A dynamic configurable option is added in the property file to delete Recon definitions with huge volume to avoid log space constraints in database. The chunk size is organized starting from 5 by default up to 1000 max. If configured chunk size exceeds system limits, that is higher than 1000 and lower than 1, a warning message will be triggered and system captures the size to system limits. A log message is generated to indicate progress to track how many total retention IDs are yet to be deleted and how many deleted so far.

Concurrent Purge Prevention

At times, running a purge job may take longer than anticipated and sometimes remain unfinished before the next purge job runs. This leads to an overlap in purge jobs which causes potential resource contention or exhaustion and interference. To prevent a second purge job from running in the system, a configurable option is added in the property file, and is enabled by default.

Work Owner Activity Log

In previous releases, there was no auditing available for revisions made to work owner definitions. With this release, any changes made to a work owner definition is tracked and recorded in the activity log. The activity log for work owners is accessed via the Activity Log icon, as with other application components.

When a work owner definition is no longer needed, the Activity Log data is deleted when the corresponding work owner is removed from system.

Rules Catalog Enhancements

The Rules Catalog functionality that was introduced in ER 4.0 was restricted to only two rule types: Adjustment Approval Rules and Routing Rules. This functionality now supports search and rule assignment for Aging Rules and Recon Entity Status Rules.

As with previous releases, administrators can now use the rule catalog to search for and locate specific Aging Rules or Recon Entity Status Rules. Once a rule is located, the Admin can click on the rule and drag it to a different definition to copy the rule. Edits to the rule must still be made to ensure all the fields and values used are correct so that the rule will function as expected.

Welcome Page

This release includes a Welcome Page which is enabled by default. The Welcome page is displayed when first logging onto the system via the Infogix ER Client.

The Favorites tab is displayed by default; this screen displays a linked list of the user’s saved favorite searches and the corresponding object ID for the search. The Overview tab is shown only for users having an Admin Role; it gives a graphical overview of the reconciliation process. The Help Quick Links navigates to view the Help Topics.

You can also access Welcome page from Help menu option available on the title bar.

Email Option on User Assign

In this release, users can receive email notification when an item or adjustment is manually assigned to them if the functionality is enabled by the administrator during deployment.

The email contains information regarding which items or adjustments are included in the user assignment. Emails are sent to those email addresses associated with the user profile of the assignee. If configured, a CC email will also receive the assignment email notice. This functionality is restricted to only those items that are manually assigned.

JavaMail version upgrade

When an SMTP server failed to respond, an Infogix thread would hang and prevent e-mail delivery.

The EmailGenerator now times out after 40 seconds if the SMTP server fails to respond.

WebSphere cluster clean script changes

The WebSphere clean script failed to remove JMS resources, when the JMS cluster was different from the application cluster.

The WebSphere clean script has been changed to accurately clean the JMS resources.

Millisecond Precision support for data captured using bulk loader

The capture and storage of Control data with sub-second information using the bulk loader utility resulted in loss of information.

The current release supports the use of sub-second information for date and time values during bulk loading. Control data is now captured and stored at a millisecond precision.

HornetQ Library Upgrade

HornetQ is an open source asynchronous messaging system.

The HornetQ library is upgraded to 2.2.24_EAP_GA to improve the JBoss® JMS reliability.

Standalone Database Migration

The standalone database migration script creates a compressed package containing the files required for the database upgrade.

The application server administrator must run the generate-standalone-upgrade script to create the standalone database upgrade package. The compressed zip file can be used by the database administrator to upgrade the database.