***** This document is subjected to changes until production ******

These release notes detail the information related to Enhancements, Improvements, and Resolved Issues in LegalHold 4.3.0 release. And this release introduces a range of exciting and highly requested features aimed at enhancing the LegalHold workflow for our clients:

• Non‑Custodial Data Source Enhancements: Legal Hold Managers can now configure systems with multiple owners, send Preservation Notices to all associated owners, and track responses end‑to‑end. Ownership changes are automatically recorded with full historical traceability, ensuring auditability throughout active holds. System Owners are now included in reporting workflows, and streamlined digest notifications consolidate removal and restoration alerts into a single, clear communication.

• Configurable Date Ranges for In‑Place Preservation: Legal Administrators can define optional custom date ranges when creating a legal hold, allowing preservation to be precisely scoped to relevant time periods. The selected range is clearly displayed throughout the workflow and available as a variable for notification templates. The feature supports both in‑place preservation scenarios and standard legal holds, including environments without Purview integration.

• Expanded Person Data Management: Ten new custom person fields can now be added, viewed, and bulk‑imported through the Manage People UI, CSV uploads, and the People API. A new collapsible Additional Fields panel improves usability, and a Comment field next to “On Hold” provides contextual visibility. All new fields remain fully backward‑compatible and can be relabeled using the Custom Report Designer.

• Unified System Ownership for Collections: A new CollectionSystemOwners data model aligns collections with the broader ownership framework, ensuring consistent behavior across collection‑related tasks and preventing workflow interruptions.

• Improved Preservation Error Notifications: A new task‑level flag controls whether custodians already in an Error state should be included in subsequent notification runs. The associated email label has been updated from “Failed” to “Error” for clearer communication.

• Multi‑Domain Support for Microsoft Integration: The Microsoft integration now supports multiple email domains per tenant, enabling normalized, case‑insensitive custodian validation across complex multi‑domain environments.

Enhancements/Improvements

Enhancement: Implemented Non-Custodial Data Sources (NCDS) Preservation initiative and improved digest email notifications
Description: Legal Hold Managers can now select systems, add multiple System Owners per application, and send Preservation Notices to all configured owners. System Owners can receive notices, respond, and comply with holds, ensuring complete participation in the preservation process. Data integrity logic tracks ownership changes, marking former owners and adding new ones automatically.
Additionally, Legal Hold Administrators can enable System Owners of non-custodial data sources to respond and comply with holds, with proper system variable resolution and historical ownership tracking. This ensures non-custodial preservation remains auditable and aligned with compliance requirements even when ownership changes during an active hold. Improved the Custom Report Designer to include System Owners in the same reporting workflow as Data Stewards, enabling consistent, filterable reports for non‑custodial data sources.

     We introduced digest email notifications to streamline communication when a system owner is removed from or returned to an associated system. Instead of sending multiple individual alerts, the system now delivers a single consolidated digest using the approved template, with titles and message text automatically adjusted based on whether the action is a removal or a restoration.
Tracking code:  LH-18810, LH-19198, LH-19199, LH-19580

Enhancement: In-Place Preservation with Configurable Date Ranges
Description: Legal Administrators can now configure an optional custom date range when creating a legal hold, ensuring preservation is limited to the relevant timeframe and data stewards receive the complete information.  The date range is clearly visible throughout the hold workflow for improved compliance and usability, and are also available as variables for email notifications.
Note: The configurable date range is primarily intended for in‑place preservation, but can also be used with standard legal holds, including environments without Microsoft Purview integration.
Tracking code: LH-18811, LH-19200, LH-19361

Enhancement: Custom Person Fields in Manage People
Description: Legal Hold administrators can now add, view and bulk import 10 new custom person fields (Field1–Field10) through the Manage People UI, HR CSV imports, and the People API, enabling storage of additional HR-related data. The UI includes a collapsible “Additional Fields” section with user preference retention, and the API supports these fields for POST/PUT/GET operations, while remaining backward compatible with earlier CSV formats. A Comment field is also added next to “On Hold” in the UI for better context.is not included in the People file or API, and the custom field labels can be renamed via the CRD.
Tracking code: LH-19314, LH-19317, LH-19318

Enhancement: Introduced a new CollectionSystemOwners table to align collections and related tasks with a unified data model, ensuring consistency and preventing workflow disruptions across the collection process.
Tracking code: LH-19369

Enhancement: New flag in the “Failed Preservation Status Notification” task
Description: Introduced a task-level flag that determines whether the next run should ignore custodians already in an Error state or include them again. Also, update the email template label from “Failed” to “Error.”
Tracking code: LH-19489

Enhancement: Enhanced Microsoft Integration now supports multiple email domains per tenant, enabling custodian validation across multi‑domain environments. Domains can be entered as comma‑separated values with full normalization and case‑insensitive matching.
Tracking code: LH-19623

Bug Fixes 

Issue: Resolved an issue where users were blocked from updating the Owner field on a Non-Custodial Datasource (NCDS) record associated with a Collection. The system now allows necessary updates, including deleting an existing owner, adding a new owner, or replacing an existing owner, to support proper data maintenance.
Tracking code: LH-19201

Issue: Fixed an issue for all recipients, where the action link in legal hold notification emails sent to custodians was not functional. Additionally, an issue in the Notice and Preservation Notice screens was resolved where clicking the space between buttons could incorrectly trigger the Continue action.
Tracking code: LH-19290

Issue: Fixed an issue where inactive users added to an active legal hold were not displayed in the No Response section on the hold tile when no changes were made after the hold was sent. Inactive users are now correctly reflected in the tile status.
Tracking code: LH-17881

Issue: Resolved an issue where the API did not return the manage matter and historical matter flags, causing incomplete data handling and preventing matters from appearing in hold creation.
Tracking code: LH-19504

Issue: We fixed an issue where inactive employees who had not responded to their legal hold were still receiving escalation notices sent to their managers.
Tracking code: LH-19295