Added validation in the receptor for the ScreenResponseDto to ensure that entities is not null. This is not a breaking change, because sending entities as null was silently failing before, but now we've improved the endpoint so it returns a 400 with the details of the error instead of silently failing down the line.

The response now includes rule_description. The alert_count field has been removed and replaced with total_alerts_received and unique_alerts_after_deduplication in the response for obervability rule execution API.

Added conditional retention periods support to Data Protection Regime query endpoints.

The overview endpoint now returns a boolean flag indicating whether a regime has conditional retention periods configured. The detailed endpoint returns the full list of conditional retention periods with their logic engine conditions.

Added ConditionalRetentionPeriods support to Regime create and update endpoints.

Data protection regimes can now be configured with conditional retention periods in addition to the standard data retention period.

Added new endpoints for Automatic Re-Onboarding.

Data Protection Query API​

• GET /dataprotectionquery/api/configuration/automatic-reonboarding/status

  • Returns Automatic Re-Onboarding Configuration Status.

• GET /dataprotectionquery/api/datadeletionprocess/{entityId}/journey/{journeyId}

  • Returns all data deletion processes for given entity and journey Id.

Data Protection Command API​

• PUT /dataprotectioncommand/api/configuration/automatic-reonboarding/{id}

  • Updates data protection configuration.

• POST /dataprotectioncommand/api/datadeletionprocess/pause

  • Pauses data deletion process for a specified entity, jurisdiction, and journey.
  • Example Payload

        "data": {
            "entityId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "journeyId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "jurisdiction": "Argentina"
        }

• POST /dataprotectioncommand/api/datadeletionprocess/unpause
  • Unpauses data deletion process for a specified entity, jurisdiction, and journey.
  • Example Payload

        "data": {
            "entityId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "journeyId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "jurisdiction": "Argentina"
        }

Includes pre-signed URLs in the response for batch transaction error file.

Fetch batch transaction information either by batch IDs or by date range.

Added property ForbiddenEntityDrafts to SearchEntityDrafts response.

Affected Endpoints​

• POST /entitydataquery/api/v2/entity/search-entity-drafts

Added support for unknown entity type in transaction.

Added DriversLicense, SocialSecurityNumber (SSN), and EmployerIdentificationNumber (EIN) to SearchCriteria in batch and to SecondaryIdentifiers in configuration. Right now it's only supported for LexisNexis and any custom providers that want to implement it.