ER 4.4 Release Notes

ER 4.4 enhancements include:

Infogix Sagacity Integration

Infogix ER can provide Infogix Sagacity with information on all the reconciliations within the environment, including the reconciliation definitions, data, and activity logs that are produced or edited. Based upon selections by Infogix Sagacity users, Infogix ER sends the corresponding definitions, data, and results to Infogix Sagacity for analysis and visualization. This feature makes Infogix ER a source for the self-service business intelligence capabilities that Infogix Sagacity offers.

Configurable Attachment Upload Limit

Infogix ER administrators can now set limits on the size of files that are attached to objects. The MAX_ATTACHMENT_SIZE property in Infogix ER.properties can be set to a maximum allowed size of files that the users can attach. Users will receive an error if they try to attach files exceeding the configured size limit. This feature provides Administrators with the flexibility to apply attachment upload limits that meet corporate requirements and reduce errors associated with attaching large files to objects.

Rich Client: Retrieve Activity Log Data in Time Order

In this release, the functionality for Activity Log Data is enhanced by adding a yellow indicator icon which is displayed when the activity log result exceeds the specified maximum limit in the properties.

Option to Hide Proxy Setting on Login

This is a new setting to either show or hide the “Use Proxy” option found on the Login Screen. This setting is a client side configuration option with the default set to hide the “Use Proxy” setting. When the property value is set to true, the “Use Proxy” option is enabled. Proxy information is typically required only if it is a corporate network standard.

Use of Input Values without Requiring Tab Out

Users are no longer required to tab out of a revised field when performing search, validation, or save actions. Previously, the user was required to tab out of the revised field in order for the value to be recognized. With this new functionality, the revised value is used without tabbing out of the field; however, display formatting (such as masking or padding) is not applied to the field until the user tabs out of it.

Welcome Page Enhancements

In this version of Infogix ER, there are two new enhancements to the Welcome Page functionality:

1. The width of the Favorite Search name column on the Welcome Page has been widened to make viewing easier for saved searches with longer names.

2. A new “Welcome Page” button was added on the main menu bar at the top of the application screen to allow users to access the Welcome Page more quickly from within the application.

Read Access to the Adjustment Number in Workflow Rules

This new enhancement allows the Adjustment Primary Key and Adjustment Entry Primary Key fields to be read within the Adjustment Workflow rules.

The primary key fields for adjustments and entries are system-generated, and were previously not readable in the adjustment workflow rules. In this release, the adjustment and entry primary keys are available for use in the workflow rules as read-only values.

For example, a typical use case is to include the adjustment key in a textual description generated by a workflow rule so that users can refer to the adjustment at a later time by using the key to locate it in Infogix ER.

Trigger EOD with a Gateway Notification

In this release, it is possible to trigger end-of-day (EOD) in Infogix ER via a new notification sent from Infogix Assure.

To use this enhancement, the ERGATEWAY_ENABLE_NOTIFICATION_EOD_TRIGGER parameter must be set to true in the ER.properties file, and the Infogix Assure control must send a “Prep EOD” notification to Infogix ER through the gateway.

Once the notification is received, Infogix ER starts EOD if it is in a state in which end-of-day can execute. If the notification is received and Infogix ER is not a state which can run EOD, an error is logged.

Log entries are also generated if Infogix ER receives a “Prep EOD” notification and Infogix ER is not configured to trigger EOD.

Check Intraday Recon Status through the Gateway

In this version of Infogix ER, a new property, ERGATEWAY_ENABLE_INTRADAY_RECON_STATUS, has been added to enable an Intraday process status check through the gateway.

Intraday processing status may be checked via an Infogix Assure control using the “ER-recon_state” function. Refer to the Infogix Assure documentation for details on using this new function in a control.

Configuration Independent Product .ear File

This enhancement simplifies console-based WebSphere® deployments across multiple environments. In the prior releases, the .ear file generated by the dist.bat (or dist.sh), contained certain environment specific information that prevented the use of the same .ear file across different environments.

The enhancement provides the ability to re-use the same .ear file across multiple environments, when Infogix products are deployed manually from the WebSphere administrative console. Additionally, the product patching process is simplified as there is only one .ear file that must be patched.

Enforcing Strong Password Usage in Embedded Directory Deployments

The enhancement provides the ability to enforce the use of strong passwords in Embedded Directory deployments.

Enable the EMBEDDED_DIR_STRONG_PASSWORD_SECURITY property to impose strong passwords. You can configure region specific password policy settings, and also define the password complexity. For more information, see the Infogix Properties Guide.

Infogix Administrative Console: Health Checker Improvements

Health Checker feature is now available in Infogix ER, Infogix Insight and Infogix Perceive. You can run health checks to detect general problems at the platform-level such as runtime problems with clustering, database, file systems, and configuration.

Process and Memory Viewer is now Supported on Unix®/Linux®

The Process and Memory Viewer that is accessible from the Infogix Assure administrative console, is now supported for product deployments on the Unix®/Linux® environments.

Platform Thread Resource Usage Optimization

Fewer thread resources are used with Caching, Process Management, and Cluster Commands. Additionally, the platform specific thread names are prefixed with the product name and category. This is particularly helpful to:

• Identify problems when multiple applications run on the same JVM™.
• Analyze Thread Dumps and Heap Dumps.