Two new SLA Event Notifications have been added to the journey feed:

• journey:slaapproachingdue — published every 10 minutes when one or more SLA instances reach their Approaching Due threshold.
• journey:slapastdue — published every 5 minutes when one or more SLA instances pass their Committed Date without being completed.

Both events apply to Journey-, Stage-, and Task-level SLAs and are published as collection events. They are off by default per Journey Schema and must be enabled via the Journey Configuration modal in Journey Builder before any notifications will be published.

Please refer to Notifications Event Registry for sample payloads.

New endpoint that returns the entity id, draft id (when applicable), type, display name, and aggregate version for each requested entity within a journey context. Uses the journey's draft when present, falling back to the verified entity record otherwise. Only accessible records are returned; inaccessible and forbidden records are silently omitted.

Affected Endpoints​

• POST /entitydataquery/api/v2/entity/drafts/names

The conflicts-exist check now persists a conflict-free result once a comparison finds no data conflicts, clearing the phantom conflict badge with no client-visible API change.

Affected Endpoints​

• GET /entitydataquery/api/v1/entity/{entityId}/draft/{draftId}/conflicts-exist (internal behaviour change only)

Journey Level Data (JLD) property values are now surfaced in Advanced Reporting: entity draft properties (scalars, Data Groups, and custom properties) are projected into the reporting data store alongside regular entity draft data.

Affected Endpoints​

• No endpoint change — internal reporting data enrichment only.

The Agency Product Verified endpoint now accepts an optional journeyId query parameter to check whether all associations for a completed journey are verified.

Added new endpoints for Legal Hold management.

Legal hold allows placing an entity under a legal hold, which prevents data deletion processes from proceeding.

Extended the requirement set retrieval API to support a configurable limit on the number of versions returned per jurisdiction.

New query parameter versionsLimit (optional): An integer to specify the maximum number of versions per jurisdiction. If not provided, it returns all.

Validation error messages now use the field's friendly name (e.g. "First Name") instead of the internal datakey (e.g. firstName).

Affected Endpoints​

• PUT /entitydatacommand/api/v3/entity/{entityId}/draft/{id}

The batch transaction response status now includes two additional intermediate values:

• pending_ingestion
• ingestion_in_progress

This applies to batch transaction status responses in the Observability API.

New endpoints used by the Manage Products task. The summaries endpoint returns lightweight product summaries for a journey (excluding full properties, jurisdictions, risk assessments, and access layers) so the side panel can load quickly and fetch each product's full data only when it is selected. The validate-all endpoint validates every product draft in a journey and returns the results for any that fail, used when completing the task. The save-without-validation endpoint saves a product draft without enforcing mandatory field validation, used to auto-save work in progress as the user moves between products.