Relativity Server release notes
This page contains release notes for Relativity Server versions 2023 and later, including release notes for Patches and Hot Fixes. For a list of known issues in Relativity, see Known issues.
Note: To view release notes for Relativity Server 2022, Relativity Server 2021, and Relativity Server 10.3, please see the Release Notes page in the Relativity Server 2022 documentation.
- Relativity releases hot fixes and patches to remediate select defects and vulnerabilities found in supported Relativity Server versions. Hot fixes are unscheduled update releases to resolve higher impact defects or vulnerabilities. Patches are scheduled update releases that also include fixes for less severe/lower impact issues
- Hot fixes and patches are associated with a specific version of Relativity Server. In other words, Relativity Server 2024 hot fix #1 is built for Relativity Server 2024 and cannot be applied to Relativity Server 2023. However, fixes in a hot fix for Relativity Server 2023 may be included in a separate hot fix for Relativity Server 2022.
- Hot fixes and patches are cumulative for a base version of Relativity Server. Each hot fix and patch that Relativity Releases includes all previously-released hot fix and patch content for that base version. In other words, hot fix #2 for Relativity Server 2024 includes hot fix #1 for Relativity Server 2024. Patch #2 for Relativity Server 2024 includes patch #1, as well as any hot fixes released between patch #1 and patch #2.
- This means you do not need to separately install previous hot fixes; the latest hot fix/patch will always include all preceding hot fixes and patches for that version of Relativity server.
- Starting with Relativity Server 2024, we are introducing a new versioning scheme for hot fixes and patches. The first digit represents the patch number, and the second digit represents the hot fix number relative to the patch. This new versioning attribute is referred to as the update version.
Consider the diagram below, which illustrates how the new update versioning scheme for Server 2024 would be applied during sequential hot fix and patch releases. In this diagram:
- Hot fix #2 (update.0.2) also includes hot fix #1 (update.0.1) changes
- Patch #1 (update.1.0) includes hot fix #1 and #2, as well as additional new fixes for the patch. (Since hot fix #2 includes hot fix #1, patch #1 includes hot fix #1 as well.)
- Hot fix #3 (update.1.1) includes everything in patch #1. (Therefore, hot fix #3 includes hot fixes #1 and #2, as well as the additional fixes included in patch #1.)
- Hot fix #4 (update.1.2) includes everything in hot fix #3. (And since hot fix #3 includes patch #1, everything up to an including hot fix #3 is included in hot fix #4.)
- Patch #2 (update 2.0) includes patch #1 (update 1.0), hot fixes #3 and #4 (updates 1.1 and 1.2), and additional new fixes for the patch.
In the following table, click on any column heading to sort the column in alphanumeric order. You can also select the drop-down to set filters for certain columns, or use the Search box to search for specific text in the Description column.
For example:
- To see a list of available Hot Fixes for Relativity Server 2024, select Server 2024 from the Version column, and then select Hot fix from the Update Type column. You can click the Original Release Date column to sort the filtered results by release date, descending or ascending.
- To see a list of Hot fixes included in a specific patch for Server 2024, select Server 2024 from the Version column, and then select the desired patch name in the Patch Version column. You can then select Hot fix from the Update Type column, which will show hot fixes that are included in the patch version that you selected.
- To see if a particular fix is included in a patch or hot fix for different versions of Relativity Server, enter the text of the fix in the Search box. This will return all release notes containing the entered text. If a particular item was released for both Server 2024 and Server 2023, you should see at least two rows in the list of Release note items.
- Product Version: This is the 'base' version of Relativity Server, for example Server 2024 or Server 2023. Remember that Hot Fixes and Patches apply only to specific versions of Relativity Server.
- Update Type: this is the type of installer that the release item was first released in. Some items are first released in Hot Fixes, while others are first released in Patches.
- Base: these items are included in the initial release for that version of Relativity Server.
- Hot fix: these items were first released in a Hot Fix (but may subsequently be included in a Patch; if there is a value in the Patch version column, it means that this item is also available in that Patch)
- Patch: these items were first released in a Patch.
- Hot Fix Version: If the item was first released as a Hot Fix, this column shows the Hot Fix version that the item was first released in. Note that Hot Fixes are cumulative, see Learn more about hot fixes and patches.
- If Hot Fix version is blank, that particular item was not first released as a separate Hot Fox, but was included in the Base release or in a Patch.
- Patch Version: This is the Patch version that the release item is included in. Patches are essentially collections of all preceding Hot Fixes for that version of Relativity Server, but can include additional fixes as well.
- If Patch version is blank, that item was either included in the initial base release, or is only available as a Hot Fix and is not yet included in a Patch.
- Initial Release Date: This is the date when that item was released for the first time.
- Type: This categories the change type of the item, for example a Resolved Defect or an Enhancement.
- Feature: This is the feature/application within Relativity that the item applies to.
- Description: This is the release item description.
Tip: you can search the Description field by entering text into the Search box. If you want to determine if the same fix was released for both Server 2024 and Server 2023 for example, use the Search box to filter rows for the specific item you are looking for, which will then tell you which release that item is included in for Server 2024 and in which release that item is included for Server 2023.
Product version | Update type | Hot fix version | Patch version | Initial release date | Type | Feature | Description |
---|---|---|---|---|---|---|---|
Server 2024 | Base | 2024/11/15 | Resolved defect | Relational Pane | When coding documents using the relational items card in the Viewer, if the user applies an item list filter and selects the ‘All’ mass-coding option in order to make a coding decision, that coding decision is applied to the top (X) documents in the unfiltered document list where (X) is the number of documents that satisfy the filter. This issue has been resolved so that only the filtered documents are mass-coded when the user selects the ‘All’ mass-coding option. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Search Term Report | Resolved an issue in the population phase of Search Term Reports (STR) where timeouts during the SQL copy of document IDs to a temporary job table could lead to under-inclusive results. This fix ensures accurate and comprehensive reporting, particularly for STRs with document volumes exceeding 20 million. Detection Tool: A detection tool is also included in the new dtSearch-Search application that helps users identify impacted STRs. The detection tool does not currently work in workspaces that do not have the Audit application installed. We will be releasing an updated version of the dtSearch-Search application that resolves the detection tool issue in workspaces where Audit is not installed in the coming days. For workspaces that do not have Audit installed, the STR fix will still be addressed by this hot fix package, but you will need to deploy the new dtSearch-Search application when it becomes available in order to use the detection tool. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | List Page | Resolves latency with initial Workspaces list page loads in instances that have a fresh install of Server 2024 or were upgraded to Server 2024 from a version prior to Server 2022 | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Object Rules | If a user is restricted from accessing a layout defined in a 'Default Layout' type Object Rule and the rule condition is met on an object, the user will be shown a message indicating that the layout is not accessible and they will be restricted from accessing any other layout for the object where the rule condition is met. Prior to this change, the user would be presented with another layout that they have access to. | ||
Server 2024 | Base | 2024/11/15 | Enhancement | Logging | In Server 2024, system health checks are recorded in EDDSLogging as Information level logs. A new rule on the EDDSLogging.Rule table called 'HealthCheck' enables Information level health check logs to be persisted without requiring the overall log level to be set to Information. This rule is enabled by default (set to 2 - Information). For a standard server you can expect to see about 2,000 health check Information level log entries per day | ||
Server 2024 | Base | 2024/11/15 | Enhancement | Installation & Deployment | The About Relativity screen now indicates the hot fix or patch version applied to the instance. Run the Relativity Update Version Check script available in the Relativity Script Library to see the hot fix or patch version applied to each server in an instance. | ||
Server 2024 | Base | 2024/11/15 | Enhancement | ADS | Custom tab icons can now be exported and imported as part of a Relativity application. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Authentication | Resolved an issue preventing RSA authentication from functioning. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | ADS | An application will now successfully upgrade when a user publishes a new version using the Publish to Relativity tool even if the application is locked and DeveloperMode is turned off in the instance. | ||
Server 2024 | Base | 2024/11/15 | Enhancement | RSMF Slicing | RSMF Slicing will allow customers to create a new RSMF from the original that contains only the relevant messages. This will allow customers to code and produce certain message / portion of the conversation that is relevant. All RSMF slices will be traceable back to the original. | ||
Server 2024 | Base | 2024/11/15 | Enhancement | Viewer | When viewing a supported audio/video file, you can toggle on/off the waveform visualization to track the intensity of the sound and skip through silence. | ||
Server 2024 | Base | 2024/11/15 | Enhancement | Viewer | The Viewer is now able to render Excel comments formatted as Modern Comments. | ||
Server 2024 | Base | 2024/11/15 | Enhancement | Viewer | Improved navigation experience in the Viewer for PowerPoint comments formatted as Modern Comments | ||
Server 2024 | Base | 2024/11/15 | Enhancement | Processing | OCR during Processing now supports Arabic, Hebrew, Thai, and Vietnamese | ||
Server 2024 | Base | 2024/11/15 | Enhancement | Name Normalization | We’ve enhanced Name Normalization with options to analyze only the latest email in a chain and to assign up to 500 aliases to an entity in a single operation. | ||
Server 2024 | Base | 2024/11/15 | Enhancement | Viewer | Microsoft OneNote SOAP/HTTP File is now supported in the native viewer. This enhancement is only available in the GA release starting on 9/6. It is not available in the EA release | ||
Server 2024 | Base | 2024/11/15 | Enhancement | Processing | When processing RSMF files you can now extract files up to 2 GB, map all RSMF 2.0 header metadata, and introduce your own custom X-RSMF headers. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Email Threading | Resolves an issue in email threading where presence of a ">" character in the author/recipient name would result in an incorrect participant merge. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Processing | The relevant error message is now displayed when errors are encountered during new Processing Set creation, rather than a static error message. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Script - Case Permission Audit Report | The Case Permission Audit Report will run successfully even when a workspace is marked for deletion. | ||
Server 2024 | Base | 2024/11/15 | Enhancement | Processing | For default and new processing profile 'Relativity' is set as default option for office files. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Conversion Cache Manager | Resolved an issue which prevented automatic cleanup of the conversion cache for mass PDFs. Now the cache will automatic remove entries older than 7 days. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Workspace Creation | Resolves an issue where workspace creation requests were occasionally duplicated. This ensures proper handling of duplicate requests and provides better visibility into the request outcomes. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Forms | Resolves an issue where the mass edit modal would occasionally appear in the classic forms styling rather than new newer Relativity forms appearance. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Analytics | Resolves an issue where documents listed in the Find Similar Documents card were missing a hyperlink after the control number field had been renamed. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Processing Jobs | Resolves an issue where clicking on the 'File Errors' link occasionally incorrectly redirected a user to the 'Document Errors' tab instead of the 'Files' tab. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Processing Compressed Files | Resolves a Processing issue that occasionally caused unexpected file extrication behavior from zip files encrypted via ZipCrypto. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Relativity Integration Points Sync | Resolved issue where non-admin users encountered failures during Sync job in newly created Destination Workspace due to missing Tag creation permissions. Implemented solution ensures system objects are now created by Service Account, ensuring seamless job execution. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Conversion Cache Manager | Resolved an issue which prevented automatic cleanup of the conversion cache for mass PDFs. Now the cache will automatic remove entries older than 7 days. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Authentication Provider | Resolved an issue preventing RSA authentication from functioning. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Structured Analytics | Improves resiliency for large, complex email threading jobs. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Custom Pages | Improved resiliency and success rate for custom page deployments. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Processing | Improved handling of MHT emails to ensure that the time zone displayed in the viewer matches the metadata settings, resulting in more accurate timestamp. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Application Installation Manager | An application will now successfully upgrade when a user publishes a new version using the Publish to Relativity tool even if the application is locked and DeveloperMode is turned off in the instance. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Structured Analytics Manager Agent | Addresses an issue where Structured Analytics jobs become stuck during the Export phase due to erroneous batch orphaning by the Structured Analytics Manager agent. | ||
Server 2024 | Base | 2024/11/15 | Resolved defect | Relativity Upgrade Tool(Procuro) | Improved resiliency and error reporting for Procuro | ||
Server 2023 | Hot fix | Hot fix 17 | 2024/11/15 | Resolved defect | Search Term Report | Server 2023 Hot fix 15 resolved an issue in the population phase of Search Term Reports (STR) where timeouts during the SQL copy of document IDs to a temporary job table could lead to under-inclusive results. The fix also included a detection tool within the dtSearch-Search application that helps users identify impacted STRs. With this hot fix, the the detection tool will now work in workspaces where the EDDSDBO.AuditRecord_PrimaryPartition table ID column datatype is set to int. The previous version of the detection tool was only working when the ID column datatype was set to bigint. Note: this hot fix is initially being released as a standalone RAP file. We will release the same fix as part of the cumulative update tool package later next week. The hot fix version number will remain the same once the cumulative update package is released. | |
Server 2023 | Hot fix | Hot fix 16 | 2024/10/09 | Resolved defect | Search Term Report | In Server 2023 Hotfix 15, an issue was resolved in the population phase of Search Term Reports (STR). Specifically, the fix addressed timeouts during the SQL copy of document IDs to a temporary job table, which could lead to under-inclusive results. This fix ensures accurate and comprehensive reporting, particularly for STRs with document volumes exceeding 20 million. It also included a detection tool within the dtSearch-Search application designed to help users identify impacted STRs. However, detection tool was not functional in workspaces where Audit application was not installed. With this release, the detection tool in the dtSearch-Search application has been fixed and is now functional in workspaces without the Audit application. | |
Server 2023 | Hot fix | Hotfix 15 | 2024/10/04 | Resolved defect | Relational Pane | When coding documents using the relational items card in the Viewer, if the user applies an item list filter and selects the ‘All’ mass-coding option in order to make a coding decision, that coding decision is applied to the top (X) documents in the unfiltered document list where (X) is the number of documents that satisfy the filter. This issue has been resolved so that only the filtered documents are mass-coded when the user selects the ‘All’ mass-coding option. | |
Server 2023 | Hot fix | Hotfix 15 | 2024/10/04 | Resolved defect | Search Term Report | Resolved an issue in the population phase of Search Term Reports (STR) where timeouts during the SQL copy of document IDs to a temporary job table could lead to under-inclusive results. This fix ensures accurate and comprehensive reporting, particularly for STRs with document volumes exceeding 20 million. Detection Tool: A detection tool is also included in the new dtSearch-Search application that helps users identify impacted STRs. The detection tool does not currently work in workspaces that do not have the Audit application installed. We will be releasing an updated version of the dtSearch-Search application that resolves the detection tool issue in workspaces where Audit is not installed in the coming days. For workspaces that do not have Audit installed, the STR fix will still be addressed by this hot fix package, but you will need to deploy the new dtSearch-Search application when it becomes available in order to use the detection tool. | |
Server 2023 | Hot fix | Hotfix 15 | 2024/10/04 | Resolved defect | Imaging | Fixed an issue where AdminPermissionRepository.IsUserSystemAdminAsync used the workspace UserID instead of the required EDDS UserID, which caused Imaging on the fly to fail. This fix ensures to use correct user id i.e. EDDS UserID | |
Server 2023 | Hot fix | Hot fix 14 | 2024/09/06 | Resolved defect | Workspace Portal | Resolves latency with initial Workspaces list page loads in instances that have a fresh install of Server 2023 or were upgraded to Server 2023 from a version prior to Server 2022. | |
Server 2023 | Hot fix | Hot fix 14 | 2024/09/06 | Resolved defect | Object Rules | If a user is restricted from accessing a layout defined in a 'Default Layout' type Object Rule and the rule condition is met on an object, the user will be shown a message indicating that the layout is not accessible and they will be restricted from accessing any other layout for the object where the rule condition is met. Prior to this change, the user would be presented with another layout that they have access to. | |
Server 2023 | Hot fix | Hot fix 13 | 2024/07/03 | Resolved defect | Addresses a security vulnerability | ||
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Authentication | Logging for OAuth2 clients has been added to enable enhanced troubleshooting of OAuth2-related issues. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Network | DNS health checks now exclude on-prem server clients reliant on VPNs for communication. This change enhances efficiency and also resolves issues for clients in regions with domain restrictions, like China's inability to resolve some of domains for e.g. google.com. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Sync | Resolved issue where non-admin users encountered failures during Sync job in newly created Destination Workspace due to missing Tag creation permissions. Implemented solution ensures system objects are now created by Service Account, ensuring seamless job execution. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Admin Page for Resource Servers | Resolves an issue where the 'Delete' button was occasionally displayed on a web server object page despite 'delete' not being a supported action on web servers. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | ADS | Resolves an issue where global applications were occasionally incorrectly queued for workspace upgrades, resulting in workspace upgrade failures. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Relativity Lists | Beginning in 2017, if you edited a saved search or view that included a date condition when Daylight Saving Time began or ended, the time component of the search or view would shift back or forward one hour. This only impacted existing saved searches and views and was able to be remediated manually if you corrected the time component change before saving. We developed a SQL script to identify impacted saved searches and a list of Daylight Saving Time dates from 2017 - 2023 by region. Both links along with detailed steps are available in the Community Article. Please review those dates and re-run any saved searches or views with those date conditions. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Instance Settings Framework | Resolves an issue where users occasionally encountered an error when attempting to delete an instance setting immediately after successfully deleting a separate instance setting. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Extensibility Points | Non-temporary Relativity program files are no longer saved in Windows Temp folders. The automatic deletion of files from these folders (e.g. by anti-virus software or Microsoft Storage Sense) would occasionally cause Relativity product functionality issues. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Email Threading | Resolves an issue in Email Threading where the presence of unsupported 'When' headers in email 'To' headers resulted in excessive alias merging. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Find Similar Documents | Resolves an issue where viewing of documents beyond the first 1,000 results failed upon clicking Control Number in 'Find Similar Document' Card. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Analytics Index | The Document Exceptions section of the Analytics Index pages now displays all pagination options consistent with other lists in Relativity. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Structured Analytics Manager Agent | Addresses an issue where Structured Analytics jobs become stuck during the Export phase due to erroneous batch orphaning by the Structured Analytics Manager agent. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | DropIt | An update is done for the setup.bat file to allow all date and time formats, ensuring successful patch installation. This is created to avoid the error that occurred during the creation of sub-folder during extraction. The installation was failing if the date and time format is set to English (United Kingdom) as dd/MM/yyyy or other Formats. The installation is only successful with the English (United States) format. This is addressed as part of update. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Creation of Workspace | A result column (HttpResponseCode/Message) is added to the WorkspaceCreateRequestGuid table that can indicate whether the request has completed and return the appropriate code. This is done to resolve an issue where workspace creation requests were occasionally duplicated. This ensures proper handling of duplicate requests and provides better visibility into the request outcomes. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Field Mapping | Resolves an issue with Excel Pivot Table Field Mapping enabling seamless Native Extraction | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | ARM Processing | Resolves an issue with ARM jobs stalling during storage table file copying due to non-repository file endings. | |
Server 2023 | Patch | Patch 2 | 2024/06/10 | Resolved defect | Processing | The Files processed allows all the Errored-out file messages and displays it under the Files section. | |
Server 2023 | Hot fix | Hot fix 11 | Patch 2 | 2024/04/24 | Resolved defect | Relativity Integration Points | DNS health checks now exclude on-prem server clients reliant on VPNs for communication. This change enhances efficiency and also resolves issues for clients in regions with domain restrictions, like China's inability to resolve google.com. |
Server 2023 | Hot fix | Hot fix 12 | Patch 2 | 2024/04/24 | Resolved defect | Addresses a security vulnerability | |
Server 2023 | Hot fix | Hot fix 10 | Patch 2 | 2024/04/15 | Resolved defect | List Page | Corrects an issue with how the Active Learning "[project name] Reviewed On" field was formatted that could have resulted in incorrect results for saved searches using 'is' conditions on the field. |
Server 2023 | Hot fix | Hot fix 9 | Patch 2 | 2024/04/08 | Resolved defect | Reset Password | The 'Send Password Reset Email' button on the User object page now successfully sends a password reset email to the respective end user. |
Server 2023 | Hot fix | Hot fix 8 | Patch 2 | 2024/04/02 | Resolved defect | RabbitMQ | For customers that have previously applied Server 2023 Patch 1, the Conversion Cache Manager is now able to successfully auto-delete expired conversion cache files during the instance off-hours window. If you have not applied Server 2023 Patch 1, this issue will not impact your instance. |
Server 2023 | Hot fix | Hot fix 6 | Patch 2 | 2024/03/06 | Resolved defect | ARM Core | Resolves issue where ARM move jobs are failing during restore. |
Server 2023 | Hot fix | Hot fix 7 | Patch 2 | 2024/03/06 | Resolved defect | Addresses a security vulnerability | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Create | Update the UI for workspace level application imports to display errors when the instance level install for that application has errors. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Relativity Forms | As a consumer of object manager, I want ObjectManager to allow saves to pass on user fields when the value has not changed, even when the user is not in the workspace. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Coding Pane | By repositioning the "saveandnext" completion line, we address a potential race condition in coding-card.ts, which has the potential to lead to form errors. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | RabbitMQ | Code changes for REL-859181-Missing RabbitMQ Bindings are not restored by restarting and version update of ServiceBus | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Authentication | This PR is to cleanup identity rap repo. This will include the removal of Required claims references, JIT settings references | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Production | Resolved the issue where Soft-deleted Productions were not appearing in the available list for the Assign Legacy Documents Bates Field script. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Redactions & Highlights | The API has been enhanced to eliminate the requirement for converting Redaction to RedactionData array and generating additional array copies, effectively resolving the problem of high memory usage on webserver. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Script - Assign Legacy Document Bates Fields | Enhanced the error message for cases where failure occurs due to field length issues in the Assign Legacy Document Bates Script. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Data Grid Audit Manager | It was observed that Data Grid Audit Manager was trying to access a workspace when the workspace upgrade was in progress and then it resulted in error. When workspace upgrade is in progress, Data Grid Audit Manager should not access the workspace and should not spam any error. To fix that, a check for workspace upgrade status is added and some informational logs also included. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Relativity Compare | Resolved the issue of missing custom formatting in Document Comparison | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Application Library | Cancel button is cut off when choosing a long application name. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Relativity Lists | The defect has been identified during regression testing of SQL PaaS automatic failover as a solution updated MultiSubnetFailover property set to 'True' in SQL connection string. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Structured Analytics | Spamming of logs issue has been fixed. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Branding | Fixed the defect that occurred when using specific font settings for producing images with small dimensions. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | RSMF Files | Resolves an issue where the RSMF "MessageHeader" field value was being incorrectly displayed as "Invalid Date" | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Agents - dtSearch Search Agent | Implemented measures to prevent the occurrence of extensive log spams when multiple agents are added to a specific server. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | ADS | Update to a LogWarning message for IncompleteTemplateException | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Graphical Image Files | Arabic, Hebrew, Thai, Vietnamese, and Belarusian unsupported languages show up under 'Default OCR languages' in Processing profile. Processing files with these languages will result in gibberish for OCR extracted text in the viewer. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | List Page | When testing a new provisioning pipeline that starts with an environment without any workspaces, Home Page installation failures were observed. Backported the changes for Post Install Event Handler. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Enhancement | Instance Details | An 'Alerts' indicator in the top right corner of Relativity notifies a user that active alerts are present on the Instance Details tab. Permission to see the Alerts indicator is inherited from Instance Details tab visibility. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Admin Page for Resource Servers | When deleting a Cache Location Server, File Share Server getting an unhelpful error message, fixed the issue by updating proper error message | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | ARM | Update Legal Hold Schema to allow different guids for certain fields. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Transcripts | In some cases, POST requests were being made as GET requests when called using JQuery Ajax methods with the "type" property used to identify the request type instead of the currently recommended "method" property. In this change, we updated all uses of JQuery Ajax methods to use "method" instead of "type." | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Permissions | In some cases, POST requests were being made as GET requests when called using JQuery Ajax methods with the "type" property used to identify the request type instead of the currently recommended "method" property. In this change, we updated all uses of JQuery Ajax methods to use "method" instead of "type." | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Structured Analytics | When running the "Merge" mass operation from the Entities tab or the "Assign to Entity" mass operation from the Aliases tab, the mass operation progress bar shows the following error message "Failed to check progress of the mass operation". These operations will complete successfully despite the error message. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Kepler | A potential memory leak in the Kepler Services hosting framework was addressed. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Relativity Compare | Doc compare re encoding wrong streaming for other language. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Processing | Add support for missing reports such as Document Exception report | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Include Processing | The Processing Migration process will now rely on the Storage table to determine which files to copy, rather than using the Invariant Settings table. This adjustment is made due to the observed inaccuracy in the Settings table, and utilizing the Storage file copy method is expected to provide increased accuracy and speed. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Processing Migration | Address the issue to ensure accurate setting of the RetryStatus column. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Email Files | Improved the parsing logic for identifying domains in exchange address. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Processing | Resolves an issue related to broken parent child relationships | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Text Files | Resolved an issue where certain RTF content was not processed correctly through our Text Handler, preventing the extraction of text. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Email Files | Addresses the issue of emails with journaled email attachments, ensuring that their bodies are rendered correctly. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Email Files | Resolves an issue where certain Russian and Korean characters were not displayed correctly in extracted text. Please note that this change will alter the deduplication hash of the affected files. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Processing | Resolved an issue with the 'Other Fields' filter not functioning correctly for Field Mapping. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Relativity Desktop Client | RDC installer defaults to a Relativity Server configuration | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Relativity Forms | Exit viewer navigation occasionally fails when navigating to viewer from Forms | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Field Mapping | Resolves an issue where Field Mapping for Excel Pivot Table was not working for Native Extraction | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | ARM Core | Resolves an issue where ARM Move jobs were failing during restore. | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Review Service | Resolves an issue where Workspace upgrade was throwing an error if the workspace had 0 documents | |
Server 2023 | Patch | Patch 1 | 2024/03/01 | Resolved defect | Processing Sets | The relevant error message is now displayed when errors are encountered during new Processing Set creation, rather than a static error message. | |
Server 2023 | Hot fix | Hot fix 5 | Patch 1 | 2023/12/04 | Resolved defect | List Page | Updating List Page to disregard carriage returns at the beginning and end of text conditions in saved searches. |
Server 2023 | Hot fix | Hot fix 4 | Patch 1 | 2023/11/15 | Resolved defect | Object Manager API | The change was to modify the query used, when the condition involved a reflected field for a Choice condition. |
Server 2023 | Hot fix | Hot fix 1 | Patch 1 | 2023/11/13 | Resolved defect | Query | There was an error in code path for multi-object when querying with "all of these" condition. Instead of using table-value parameter, we will use CSV in query as default to fix the issue |
Server 2023 | Hot fix | Hot fix 2 | Patch 1 | 2023/11/13 | Resolved defect | Review Service | Backported change to resolve the issue with document history pane not working for clients who do not have Audit app installed/configured |
Server 2023 | Hot fix | Hot fix 3 | Patch 1 | 2023/11/13 | Resolved defect | Processing | New and existing Processing jobs are not able to run when upgrading from a pre-Server 2022 version to Server 2023. While processing backfill jobs to populate a new field 'Is Published', Processing set manager throws errors and becomes unresponsive. The issue is happening due to concurrent sql connection requests which were failing. The fix removes the concurrent calls and resolves the issue. |
Server 2023 | Base | 2023/09/15 | Resolved defect | Legal Hold | Updated the Legal Hold application to save time stamps in UTC going forward. This will decrease discrepancies for customers who have Server time zones set to something other than UTC | ||
Server 2023 | Base | 2023/09/17 | Enhancement | Product Documentation | You can now mouse-over section headings in product documentation to get (and copy) a hyperlink directly to that heading. | ||
Server 2023 | Base | 2023/09/18 | Enhancement | .NET Framework | .NET Framework 4.8 and 4.8.1 is now supported. | ||
Server 2023 | Base | 2023/09/19 | Enhancement | Active Learning | Active Learning can now use any single-choice field as its designation, not just fields with exactly two choices. During project setup, one choice is selected as positive, another choice as negative, and the rest of the choices are treated as "neutral" and will not train the model. | ||
Server 2023 | Base | 2023/09/20 | Enhancement | Active Learning | You now have the option to turn off index health documents in an Active Learning Prioritized Review Queue. This allows stable projects to substantially reduce review overhead. | ||
Server 2023 | Base | 2023/09/21 | Enhancement | Active Learning | We increased document-to-document speed in active learning queues by approximately 30%. | ||
Server 2023 | Base | 2023/09/22 | Deprecation | Analytics | The Conceptual Resource Manager Agent was removed. Indexes that are inactive for seven (or the configured number of days) will no longer be deactivated. | ||
Server 2023 | Base | 2023/09/23 | Enhancement | Case Dynamics | We updated the Add Fact logic from the Viewer and selected text is no longer copied to the Description field. | ||
Server 2023 | Base | 2023/09/24 | Resolved defect | Discovery | Emails and Calendar items sent using the "On Behalf Of" feature will now correctly display that text in extracted text. | ||
Server 2023 | Base | 2023/09/25 | Enhancement | Legal Hold | You now have increased flexibility to configure escalations, including the number of recurrences, the email subject line, and the email recipient. This offers a customizable experience when including escalations in your legal hold communications. | ||
Server 2023 | Base | 2023/09/26 | Enhancement | Legal Hold | You can now send legal hold emails using the values set in the instance settings, without having to enter email credentials into a workspace. | ||
Server 2023 | Base | 2023/09/27 | Enhancement | Legal Hold | We added timezone labeling throughout a variety of lists within the Legal Hold application including within the Mailbox tab. | ||
Server 2023 | Base | 2023/09/28 | Enhancement | Legal Hold | We added timezone labeling in the legal hold confirmation emails. | ||
Server 2023 | Base | 2023/09/29 | Enhancement | Legal Hold | Using an apostrophe in a preservation case name is no longer prohibited. | ||
Server 2023 | Base | 2023/09/30 | Enhancement | Legal Hold | You are no longer required to include a portal link for hold notice communications that do not require acknowledgement and do not have an associated questionnaire. | ||
Server 2023 | Base | 2023/10/01 | Resolved defect | Legal Hold | You can now close projects that have custodians on active Microsoft 365 preservation holds. The holds will automatically be closed as part of closing the project. | ||
Server 2023 | Base | 2023/10/02 | Enhancement | Legal Hold | You can now use modern authentication, certificate based, for setting up Preservation Hold Settings. Basic authentication, username and password, is no longer available for Preservation Hold Settings. | ||
Server 2023 | Base | 2023/10/03 | Resolved defect | List Page | Fixed a responsive UI issue with the Only link in the list filter so that it is now fully visible. | ||
Server 2023 | Base | 2023/10/04 | Enhancement | OCR | The OCR engine now provides faster throughput and better text recognition results. These improvents impact non-Latin-based alphabet languages as well. | ||
Server 2023 | Base | 2023/10/05 | Enhancement | Processing | The Copy mass operation is now available on the Processing Profiles tab. | ||
Server 2023 | Base | 2023/10/06 | Enhancement | Processing | Fix native imaging issue for Japanese PDF file without embedded fonts. | ||
Server 2023 | Base | 2023/10/07 | Enhancement | Processing | Removed UvmSqlUser check for Logging. | ||
Server 2023 | Base | 2023/10/08 | Resolved defect | Processing Administration | Processing Source Locations will function as expected regardless of if the UNC path provided has a trailing slash or not. | ||
Server 2023 | Base | 2023/10/09 | Enhancement | Review | The Edit mass operation is available for Similar Documents and Concept Search cards in the Viewer. | ||
Server 2023 | Base | 2023/10/10 | Enhancement | Review Interface | When a coding decision is made, updates to coding layout values visible in the Related Items card will automatically refresh to display those new values. Additionally, any information in the Related Items card can be refreshed whenever the user manually clicks on the Refresh icon in the Related Items card. | ||
Server 2023 | Base | 2023/10/11 | Enhancement | Review Interface | The Replace Native and Image feature will be implemented in the new Viewer as a drop-down selection from the document name. When clicking on the document name in the Viewer, the option to either Replace document native or Replace images for this document are available. Following this selection, you can select a file to upload. | ||
Server 2023 | Base | 2023/10/12 | Enhancement | Review-AI | The Filtering & sorting option is now available for Find Similar Documents, Concept Search and Keyword Expansion AI cards in the Viewer. | ||
Server 2023 | Base | 2023/10/13 | Enhancement | Review-AI | The Copy Selected Keywords option is now available for Keyword Expansion AI card in the Viewer. | ||
Server 2023 | Base | 2023/10/14 | Enhancement | Review-AI | Dynamic columns option is now available for Find Similar Documents and Concept Search AI cards in the Viewer. | ||
Server 2023 | Base | 2023/10/15 | Deprecation | RSAPI | RSAPI endpoints are no longer available for consumption. All applications must use Kepler endpoints instead. | ||
Server 2023 | Base | 2023/10/16 | Deprecation | Service Bus | Service Bus for Windows is no longer supported. You need to convert Service Bus to RabbitMQ before upgrading to Server 2023. Server 2023 supports RabbitMQ version 3.10.x, 3.11.x, and 3.12.x | ||
Server 2023 | Base | 2023/10/17 | Enhancement | SQL Server | SQL Server 2022 is now supported. | ||
Server 2023 | Base | 2023/10/18 | Enhancement | Structured Analytics | Signature blocks are no longer considered part of segment bodies when it comes to email threading analysis. This improves how email signature blocks impact the inclusiveness designation of an email are reduces over-inclusiveness based on signature blocks. | ||
Server 2023 | Base | 2023/10/19 | Enhancement | Structured Analytics | Structured Analytics now appears in Aero styling. | ||
Server 2023 | Base | 2023/10/20 | Enhancement | Structured Analytics | You can now copy the results of the domains identified by Name Normalization into new multi-object fields. These new fields remove empty entries, remove duplicated domains, and support expanded filter options. You can also create a tab in your workspace that includes all the domains identified by the Name Normalization to export your results. | ||
Server 2023 | Base | 2023/10/21 | Deprecation | Viewer | The Classic Viewer has been removed in Server 2023. Users will no longer have the option to revert to the Classic Viewer. All review functionality is now standardized on the new Viewer introduced with Aero UI. We’re making this change to enable your teams with a faster, more consistent review experience across native, image, and text documents. | ||
Server 2023 | Base | 2023/10/22 | Enhancement | Viewer | Reviewers now have the ability to rotate native documents. | ||
Server 2023 | Base | 2023/10/23 | Enhancement | Viewer | The Export to CSV option is now available for Find Similar Documents, Concept Search, and Keyword Expansion AI cards in the Viewer. | ||
Server 2023 | Base | 2023/10/24 | Enhancement | Viewer | Save as Search functionality is available for documents in Concept Search and View Similar documents cards in Viewer. | ||
Server 2023 | Base | 2023/10/25 | Enhancement | Viewer | The Export to CSV option is now available for Find Similar Documents, Concept Search, and Keyword Expansion AI cards in the Viewer. | ||
Server 2023 | Base | 2023/10/26 | Enhancement | Windows Server | Windows Server 2022 is now supported. | ||
Server 2023 | Base | 2023/10/27 | Enhancement | Windows Server | Windows Server 2012 R2 is no longer supported. | ||
Server 2023 | Base | 2023/10/28 | Deprecation | RSAPI | RSAPI endpoints are no longer available for consumption. All applications must use Kepler endpoints instead. | ||