Assure 8.2 Release Notes

Assure 8.2 enhancements include:

Rule Search

A rules writer can now search through the contents of all Infogix Assure rules to find where certain terms or constants are used. The searchable data is all of the information that is found on the definition reports for controls, data quality controls, layouts, translations, result templates and result actions. The results of a search include the type of rule found, the type of report reference (nearest definition report heading), the location of the matched text which includes the rule name and any additional hierarchical structure, the leading definition report label, and the content of the rule that matched the search.

For example, a rules writer might search for an account number 9991234 to see if there is any special handling for that account within the rules of the system. The user might get back search matches that have a rule type of Control, a Location that shows the control entity name, control point name, capture source and sublayout, a label of “When Condition”, and content that shows the expression for that condition that includes the account number. This feature helps rules writers find the rules they need to review or modify when business control requirements change.

Infogix ACR Integration

In past releases, Infogix Assure was able to obtain Infogix ACR history data values for use in validation of Infogix Assure controls. Now, Infogix Assure provides an integration web service that Infogix ACR can use to obtain history values from Infogix Assure control data and use them in ACR balancing rules. This allows customers to better expand the scope of their controls with Infogix ACR to include integrity information recorded by Infogix Assure controls.

Active Import Feedback

Previously, customers who imported very large sets of controls did not have any insight into the import processing progress. Additionally, the user needed to respond to session timeout warnings every 20 minutes. Imports that ran more than an hour would result in an error when Internet Explorer automatically resubmitted the import request.

The import process for control entities has been revamped to provide continuous feedback while the import process is running. The system breaks down the import process into several steps, and provides both a progress bar and detailed text feedback on the start and completion of each step. The user no longer needs to respond to timeout warnings while the import is running. This feedback provides customers a more dependable import process, and assurance that a large import has not become blocked by an unforeseen problem.

Ignore Item Dependencies on First Import

A rules writer performing an import of rules can now choose to ignore field dependency issues when they initiate a controls import. Previously, if the rules writer knows that these warnings will appear, they had to wait for the first import attempt to fail and show the dialog of issues, and then choose Continue to import the controls anyway. This allows the user to save time importing a large set of controls that are known to raise field level issues.

Controls Modified Since Filter

When the rules writer chooses to filter the list of controls with a modified since date, the system now returns the list of controls where either the control entity was modified since that date or any of its control points were modified since that date. Previously, the system was not returning those controls where a control point had been changed after that date but the control entity had not. This allows the rules writer to more easily see or export the subset of controls that have been changed since a certain point in time.

Security Profile Filters

Often, sets of related rules for a project or solution are secured by distinct security profiles within the system. Users may be granted visibility to rules and/or results in multiple project-specific security profiles. Now, these users can filter their view of the manage rule pages and results pages to the subset of items that are secured by a particular project-specific security profile. As the users move to different pages within the session, the system automatically applies the same project-specific security profile filter. This allows users who work on multiple projects to have a more focused view of rules and results when they are working on a particular project. Additionally, this feature helps security managers identify rules that are incorrectly secured.

Export Server Utility Commands

System administrators can now perform exports of control entities, applications, layouts, translations, result templates, result actions, calendars and security profiles from server-utility command line scripts. Export selection options include rules with particular names, names matching a pattern, rules modified since an indicated date, and rules secured by a particular security profile. Exports of control entities or applications can also be directed to find and include all controls referenced by the selected controls. This allows customers to automate the exporting of rules within their business processes.

Merge Replace Always

The merge rule for a capturing control point adds a “Replace Always” choice for a control field. This option will replace a previously captured and stored control field value with a null value captured at the new control point. This allows the rules writer to capture a null value and reset a control field that had previously captured a non-null value.

Maximum Retention Override

A new installation property is provided that defines a maximum retention period to apply to an installation of Infogix Assure. This value may reduce the computed retention period for any control when retention is run. This feature allows rules developers to define production oriented retention policies and not change them for different environments (development, test, production). System administrators can use the override to manage space for those environments whose database is not sized for production-levels of retained data.

New and Enhanced Functions: @rerun, @t_contains

A new rerun function is added in this release, which returns true if the current control point was executed with the is-rerun flag. This function allows the rules writer to change execute control point action processing, to either pass along the rerun flag to the control point being executed, or to evaluate in a condition whether or not to perform the execute control point action.

The function t_contains has been improved to allow failure when there are exceptions when producing a value. Previously, the function logged a warning with a stack trace and returned false whenever there was an internal error. The behavior of prior releases can be restored with a configuration change.

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.