ER 4.5 enhancements include:
Letter Data Access in Adjustment Workflow Rules
In this version of Infogix ER, two adjustment workflow events, the Pre-Update Adjustment Entry Field event and Post-Update Adjustment Entry Field event, may use Letter data in an If Condition or Set Field By Expression statement within the rule.
Only fields from the data models of letter definitions used in the adjustment's Letter Applicability Rules may be used in Workflow Rules, and access is read-only.
Date Formatting in Adjustment Workflow Rules
This release of Infogix ER includes a new function, date_to_text, which formats a date or timestamp value for use in a text field (for example, in a description field). This function is available in the adjustment Workflow Rules.
New View Secure Values Permission
To manage the security surrounding Secure Text fields, the application includes a new security permission (View Secure Values) in the Recon Data permission set.
If a work owner is granted the View Secure Values permission, they will be able to use the Unmask button to view the values of a Secure Text field. If a work owner does not have this permission, the Unmask button is disabled and data will not be visible to the user.
Secure Text Fields
This version of Infogix ER includes a new data type, Secure Text, available in the reconciliation data model.
A Secure Text data type, by default, has field values masked in the user interface and encrypted in the database. Because data are encrypted, Secure Text fields require more database space than regular text fields; this should be taken in to account when administering and monitoring the application database.
Due to the sensitive nature of data in Secure Text data type fields, these fields cannot:
- Be used in search criteria
- Be used in field mapping rules for an adjustment
- Be used as identity fields for recon entities, match sets, or items
- Be used in matching rules or other rules
- Will not be pushed to Infogix Sagacity (definition or data)
Existing text fields in a reconciliation cannot be converted to a Secure Text data type field.
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.
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.