Items included in the Reveal 2024.3 Patch release. Release Date 04/06/2024.
Summary |
Description |
Update to the latest version of Hyland Document Filters |
Updated that library that handles indexing and imaging of documents to 24.1.0.4978. |
Optimize Vectors Service when not creating Numeric vectors |
Performance Optimization of RAI Vectors service - Reduce vectors data movement across RAI Persistent storage when not needed for existing Vectors for a project. |
NEW Classifier Version property to remove Unwanted Metadata features |
Introduced versioning for Classifiers, to remove unwanted Metadata features for New Classifiers created from this version onwards. These are features that are not necessarily useful for classification purposes and AI model building, such as BegDocId, BegDocAttachId, etc. Existing Classifiers created before this version are not affected by this change. |
Field profile conflict with new permission "allow all field profile access" can cause filter modals to break |
Corrected issue with a new 2024.3 function that limits field visibility based on team membership and team-profile assignment. The issue affected filtering on certain fields shown in the Document Grid. |
Default roles that have "Allow All Fields/Tags for Search" updated |
The Allow All Fields/Tags for Search permission has been added to Client Administrator and Power Reviewer roles, by default. It can still be removed on a project-by-project basis if desired. |
The fields assigned to teams are not properly returning for the Default field profile |
Corrected issue with a new 2024.3 function that limits field visibility based on team membership and team-profile assignment. The issue affected use cases related to the Default field profile. |
Editing a saved search does not provide feedback of completion if the user doesn't execute the saved search |
Corrected a workflow issue, where saving a search before executing it would correctly save any changes but those changes would not be reflected in the search builder unless the user executed the edited search prior to saving it. |
Empty folder shows on projects without document level security |
An unnecessary empty folder node, called Unsecured, was appearing in the left sidebar for projects that did not have Document Level Security enabled. |
Comms graph settings are not scrollable on smaller screens |
Fix. Scrolling the communication graph settings on certain screen sizes was malfunctioning. This issue has been fixed. |
Domain cards show no values on the Comm graph |
Fix. The Domain view of the communication graph had an issue that rendered details invisible on the small 'info cards' available from clicking a domain in the graph. This issue has been fixed. |
Custodian and Extension widget default field visibility issue |
Corrected issue with a new 2024.3 function that limits field visibility based on team membership and team-profile assignment. The issue affected the Custodian and Extension widgets on the Dashboard. |
Timeline widget field list not always driven by user's teams |
Corrected issue with a new 2024.3 function that limits field visibility based on team membership and team-profile assignment. The issue affected the list of fields on the Timeline widget on the Dashboard. |
Timezone could affect nightly runs of tagging efficiency report |
Fixed a timezone issue that could potentially affect the frequency of scheduled updates of a stored procedure that populates the tagging efficiency report. |
Production export splitting value of multi-value fields on semi-colon |
Fix. A multi-value field that needs to have the semicolon replaced with the delimiter in the desired output format caused an error if the field value also contained the exact delimiter inside the field. |
Error loading the reports charts on Tagging Breakdown Report |
Fix. The Tagging Breakdown Report was showing an error 'Failed to load resource' instead of a chart in certain conditions. This issue has been resolved. |
Slipsheet condition order is not preserved on Production jobs |
Fix. In a slipsheet template with multiple conditions, following execution of a production job the order of the conditions could get overwritten in some cases. What had originally been the last condition was moving the second position in the list, and so on. |
Fix the OOM error for the incremental communicator report generation |
Fixes out-of-memory issue when incremental data processing in the analytics pipeline runs against a dataset with very large documents in the existing data set. The issue occurred when the pipeline stage to collect email aliases, which normally requires a modest amount of memory, loaded a very large document and the memory allocation was overwhelmed. The pipeline stage now gets a full memory allocation. |
License audit log DB corrupted when component goes down |
Fixes an issue where, in some rare circumstances, analytics features become unavailable due to an Out of Memory error. |
Last updated: April 4, 2024