Infogix Assure is now Assure DQ
As part of the Precisely rebranding strategy, Infogix Assure product is now rebranded as Assure DQ. Within the user interface, users will see the new Assure DQ naming being used.
Note that there may still be some underlying references to "Infogix Assure", but those have been kept to reduce any issues with the broader backend name dependencies.
Test Translation Rule
A rules developer can now test a translation rule. The rules developer can define one or more tests including values for all translation inputs, run the test, and view the translation outputs for all the tests performed. This allows the rules developer to quickly verify their translations before using them in control point capture logic.
Improved Reference Reports
Reference and Referenced by reports are now shown in a flattened layout, without the use of expand/collapse sections. This improves readability as well as printability.
Translation Usage Independent Caching
A rules developer can now specify the lifetime of a loaded translation table by specifying a time of day at which the translation should be reloaded. Previously, translation data was always discarded as soon as control points were no longer using the translation and reloaded on the next use. Now, by specifying a time of day, the system can reuse translations across control point executions at different times of the day, potentially improving control point processing speed.
Work Field Increment
A new work field increment extract rule is added on the Extract tab for capturing control points. This simplifies rule building for the rules developer who often needs to perform this activity.
Detecting Control Point Executions Deletion During Import
When a controls export zip is loaded by the import process, the system will detect control points that are being deleted which have execution history in the system and will warn the user about those control entities that have this condition. The user can then get further information about the control points being deleted and how many executions will be deleted by the import. The user must confirm that the executions will be deleted to complete the import. This ensures the user performing the import understands the consequences of the rules being imported, and why the import might take longer than normal.
Expanded Sublayout References
HTML, JSON and External Service layouts can now define sublayout elements that can parse the data at a location according to another type of layout. For example, the text of a JSON field might be parsed as a record of a positional layout. This gives the rules developer greater flexibility in the definition and reuse of layout rules used for capture processing.
File Monitor from Archive File
A File Monitor capture source can now process an archive file that contains many files, and obtain information about each file, or initiate separate control point processing for the contained files. For example, a zip file of a folder containing many csv files can be processed as a file monitor control point and trigger the capturing of each contained csv file in a separate control point execution.
Control Data Export File Extension
Previously, the export control data utility always produced files ending with the extension ‘cdt’. Now, by default, the system will generate a file name that ends with csv if the field delimiter used is a comma, or a file name that ends with tab if the field delimiter used is a tab, or a file name that ends with cdt for anything else. The user can also specify the file extension to use with the -ext option on the command line.
User Activity Tracking
The system now writes a user activity log file which logs the activity of logged in users navigating throughout the system. Actions taken by users which are written to the audit history such as saving, importing, or deleting rules are also written to the user activity log file. Administrators can use this information for research or diagnostic purposes.
Customer Logo on Reports
Customers can configure the system to use their own logo on the reports produced by the system.
Runtime Fields in Left/Right Include/Exclude
The rules developer can now specify an expression that includes runtime fields for a reconciliation task side include/exclude when condition. This allows control points to be defined that apply only to subsets of data specified at runtime.
Reconciliation Task Reports to Data360 DQ+
The system will now establish data stores in DQ+ for reconciliation task reports, including child data stores for the left and right matching items. This allows data analysts in DQ+ to perform additional analysis on the reconciliation task results produced by the control point.