ER 3.1 enhancements include:
Configurability of Notes Activity Logging
User and time information for notes activity is recorded with the notes. If notes activity logging is not required for audit purposes, the AUDIT_ADD_NOTES property can be turned off in the reconciliation.properties, adjustments.properties, and cashdifferences.properties files. This reduces the database size.
OBJREFID Type Conversion
Release 3.1 has built in OBJREFID type conversion which provides enhanced data model optimization that improves database query performance. The database migration process will take longer when upgrading the database tables for previous versions.
Configurability of System Aging and Routing Activity Logging
Activities for system aging and routing activity logging are logged by the system. If activity logging is not required for audit purposes, the AUDIT_SYSTEM_AGING_ACTIVITY AND AUDIT_SYSTEM_ROUTING_ACTIVITY properties can be turned off in the reconciliation.properties file. This reduces the database size and data loading time.
System Field Display Name for Imported Recons Corrected
ACTMATCHSETUUID (Item Active MatchSet UUID) is a system field in the Reconciliation Item table. When selecting this field for the User Interface, the display name is overridden to be Relevant Match Set UUID.
When some recons from earlier releases were imported into release 3.0 instead of Relevant Match Set UUID displaying for the system field, the old Item Active MatchSet UUID display name displayed. In a few cases, both displays names would be displayed.
In Release 3.1, only the Relevant Match Set UUID name is displayed when selecting the system field for the UI.
Cash Differences Detail Screen Updates after Note Added
The Cash Differences Detail screen now updates after a note is added. This allows users to make other changes on the Detail screen without the need to force the screen to refresh.
Update Fields when User Profile Changes
Previously, the User Profile fields moduserid and modtimestamp were updated only once if the fields were not set originally and not updated any time after if changes were made to a user’s profile.
In Release 3.1, the moduserid and modtimestamp files are now updated whenever there is a change to a user’s profile.
Matching Type with Zero Items on Left or Right
Users can now configure a matching type in which there can be zero items on the left side and multiple items on the right side, as well as a match consisting of many items on the left side and zero items on the right side.
Prevent Two Users from Submitting Adjustment with Same Item
Previously, it was possible for two users to submit an adjustment with the same item. With this release, the system now prevents two users from submitting an adjustment with the same item.
Ability to Configure the Teller ID Input Size
The Teller EID field is a system-generated text field of 50 characters. When creating a new teller, there may be a need to limit the number of characters that can be entered in this field to reduce errors.
In Release 3.1, the size of the Teller EID field is now configurable. The TELLERID_INPUT_SIZE_LIMIT property in the cashdifferences.properties file can be set to whatever limit is desired.
Enhanced Excel Export
In Release 3.1, the Excel Export feature now allows 65335 rows to be exported which is the upper limit for Excel. An export that is greater than 64K will fail and displays an error message.
New Difference Calculation in Matching Rules
In Release 3.1 for a Reconciliation Matching Rules, a new Difference Computation option is available. The option (Left Total) + (Right Total) accommodates cases where the left and right total have different signs and using absolute values to compute the difference is not suitable.
Separate Match Recon Data and Adjust Recon Data Permissions
Two new permissions are available in Release 3.1: Match Recon Data and Adjust Recon Data. The existing Match/Adjust Recon Data permission implies the Match Recon Data and Adjust Recon data permissions. Both Match Recon Data and Adjust Recon Data permissions would imply the View Recon Data permission.
For customers using the existing Match/Adjust Recon Data permission, there is no functional change.
The Match Recon Data permission allows the user to perform the following Match Set operations:
- Create a manual match
- Un-match a match
- Confirm and create a match set
The Adjust Recon Data permission allows the user to perform the following Adjust operations:
- Add items to an adjustment
The Match/Adjust Recon Data permission or both the Match Recon Data and Adjust Recon Data permissions are needed to allow the user to perform the following operation:
- Confirm and adjust match sets
Linked Fields in Forms
In certain cases, a customer wants to ensure that the value entered by a reconciler on a form is always consistent with another field’s value. For example, a field completed by a user must have the same value as the system side indicator field when entering new Recon Items. In previous versions, such a constraint could not be automatically enforced and required manual workarounds.
In Release 3.1, the Reconciliation User Interface Definition Item Detail tab now allows the customer to define an editable source field as linked to another field. The source field must have the same data type and be of equal or lesser size.
For form editing screens, editing for the linked fields is disabled and the linked field always takes it value from the editable source field.
This new functionality does not change the existing customer UI definition or UI functionality.
Icon Displays when Note Attached to an Item
Previously, customers found it difficult to quickly identify which items had notes attached, which indicates that work is being performed in the system. In Release 3.1, a notes icon now displays for that item in the search results. The icon helps a customer quickly identify when an item has a non-empty note attached. The notes icon displays in the search results pane for items, match sets, recon entities, adjustments, cash differences, tellers, and CD exceptions.
Duplicate a Reconciliation Definition
In previous Infogix ER releases, a customer was required to enter all the information to create a new reconciliation based on a reconciliation with a similar model and rules. This process was time-consuming and prone to errors.
In Release 3.1, a reconciliation definition can now be duplicated and saved based on an existing recon definition with the following changes.
- The Recon ID and Name are appended with “_COPY”. The Recon ID and Name can be changed before the duplicate is saved.
- The Model Definition table names are reset based on the new Recon ID.
- The Assure control execution rules are removed.
When a top-level Recon is duplicated, its subrecons are not duplicated. When a subrecon is duplicated, it is duplicated to a parent recon. The top-level recon, to which the subrecon belongs, and any descending recons are eligible to be the parent of the subrecon being duplicated.
Saved Search Criteria and Recall
Previously, recon workers needed to repeatedly enter the same search criteria every time they performed a search because there was no way to save the search and reuse it. In Release 3.1, a recon worker can save a search as the default search filter for that item and that user. The saved search includes the fields, their values and formats, and the order of the results fields.
To perform a search using a previously saved default search filter, the recon worker opens the Search window and recalls the search filter. The system fills the search filter with the saved filter field values for the Recon item and user. The recon worker than performs the search and reviews the search results.
The Save Search and Recall Search features are available when performing searches for items, match sets, recon entities, adjustments, cash differences, tellers, and CD exceptions.
Reduce Potential for Inconsistent Status for Reversed Adjustments
When adjustments are reversed, the reversal may be sent to an external Adjustment output, outside the ER database transaction. In a failure scenario, it is possible for the adjustment reversal database transaction to be rolled back on the ER side, but the reversal to the external adjustment output has already been sent and cannot be reversed. This causes an inconsistency between the two system states.
For Release 3.1, to minimize or reduce the possibility of this inconsistent state occurring, the sequence of the internal reversal operations has been reversed so the Adjustment Output is the last step. This change minimizes the chance of an output reversal request being sent before other potential errors could occur.
Enhanced WebSphere Deployments
Many of the tasks to deploy on WebSphere have been automated. The following enhancements simplify deployment on a WebSphere application server:
- The validate-config script now validates the following settings, which reduces the chance of deployment errors:
- WebSphere server settings
- Node names
- Whether Java 2 security is disabled. If Java 2 security is enabled, the system sends a message.
- When creating data sources, the system automatically configures the path for the JDBC drivers.
- The deployment process sets the value for the HTTP, SSL, and transaction timeouts.
- The deployment process configures the class loaders.
- The deployment process automatically sets the heap size.
- The deployment process automatically sets the JVM arguments.
- For Windows, UNIX, and Linux, the system configures the JVM settings for your Infogix application to use Internet Protocol version 4 (IPv4).
Control Override Values
Previously, files in the CONFIG_OVERRIDE folder were not copied over during migration. As a result, customers who upgraded did not retain the customized properties in this folder.
Beginning with this release, you have the option to override the values on a file by file or property by property basis.
The migrate-config script brings in the values from your previous configuration and the deployment process overrides the properties with your customized values.
Several enhancements improve the process of setting up a clustered environment.
Duplicate Cluster Settings
For all application servers, the validate-config script checks the multicast port and multicast address to look for duplicates in other environments. This change helps to eliminate errors and to prevent unanticipated behavior that can occur if two or more products use the same multicast port and address.
Unique Log File Names
You are no longer required to set up a local configuration for a clustered environment. The host name is added as a prefix to the log file name to identify the log for each configuration.
For JBoss and WebSphere, the property that controls the JVM arguments for the server also controls the naming of the server log files to reflect the unique server name.
In JBoss, the property is JBOSS_APP_TARGETx.JBOSS_APP_JAVA_OPTIONS, and in WebSphere, the property is WEBSPHERE_APP_TARGET.JAVA_OPTIONS.x, where x represents the server.
Infogix Assure API Settings
For a WebSphere cluster, the deployment automatically sets the value for the following API settings: DIA.TOTAL_PROCESSORS, DIA.PARTITION_START, and DIA.PARTITION_END. Previously, a user had to specify the startup options.
Infogix Administrative Console
Infogix applications now have access to an administrative console. From within the console user interface, an administrator can collect diagnostic data without third-party intervention.
Customers can work with support personnel to generate the necessary data to diagnose run-time problems, and to send the data to support, as applicable.
You can use the console to perform the following tasks:
- Configure logging for a specific area of your Infogix application
- Enable the collection of data to show memory and CPU usage
- Generate heap dumps on demand and copy them to a specified location
- Generate thread dumps
- Create a diagnostic package that includes thread dumps, log files, configuration files, and system information
- View specific configuration or log files
Multiple Deployments of the Same Solution on a Single Server
You can now deploy multiple instances of an Infogix application under a single application server instance. This reduces the number of application server instances that an administrator must run and maintain. The instances can run simultaneously; the only constraint is the memory available on the application server. Patches must be applied separately to each instance of the application.