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.

Poll the execution status summary from the Observability API using the execution_id. This works for both tenants using either the Rule Rerun API or the Rule Execution API endpoints

• GET /api/v1/rules/execution?execution_id={execution_id}

Poll the rule execution status summary using the execution_id retrieved only when using the Rule Execution API endpoint

• GET /api/rules/status/{execution_id}