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.

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.

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}

The previously deprecated failed_transaction_modification_ids and progress_percentage fields are no longer returned in the batch status response.

The Rule Schedule API provides visibility into rules execution schedule.

• POST /api/rules/schedule

The progress_percentage field in the batch status response has been marked as deprecated and will be removed in a future version.

Request and retrieve data export reports for specific dates through the Transaction Monitoring Observability API.

The failed_transaction_modification_ids field in the batch status response has been marked as deprecated and will be removed in a future version.