Added new endpoint to query risk assessments for related parties by task id and entity ids.

Affected Endpoints​

• POST /riskquery/api/risk-assessment/related-parties/{taskId:guid}

Added validations in the Screening Receptor when a batch is created and results are sent back from the provider to check:

• That all the entities being returned for the batch search results to the receptor belong to the batch.
• That the match.providerId returned for the batch search results to the receptor exists in the list of the batch providers.

Also, added fields to the Screening Command API in order to support implementation of Alias Screening. For all the endpoints, entityAliases can be sent as null or an empty list if not using Alias Screening.

Added new endpoint to query risk assessment for a related party by task id and entity id.

Affected Endpoints​

• GET /riskquery/api/risk-assessment/related-parties/{taskId:guid}/entity/{entityId:guid}

Affected Endpoints​

Added optional properties to role configuration

• POST /api/portal-roles/createrole - EntityPageConfig - EnableAccessLayers (optional)
• PUT /api/portal-roles/updateroledetails - EntityPageConfig - EnableAccessLayers (optional)
• GET /api/portal-roles/portalRole/{id} - EntityPageConfig - EnableAccessLayers (optional)
• GET /api/portal-roles/portalRoles - EntityPageConfig - EnableAccessLayers (optional)

Added optional properties to user endpoints

• GET /api/portal-users/getPortalUserDetails - AccessLayersConfig (optional)
• GET /api/portal-users/getPortalUserDetailsWithoutLinkedEntities - AccessLayersConfig (optional)
• PUT /api/portal-users/updateUserDetails - AccessLayersConfig (optional)

Updated response to include entity type.

Affected Endpoints​

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

Trigger the execution of scheduled rules for a specific date

• POST /api/rules/execute

This endpoint is marked as obsolete but will continue to be supported with no planned termination date. However, its usage is not recommended as it does not support full field-level validation.

Update BatchExternalIds to use their own model (BatchExternalId instead of ExternalId), as it does not make sense for a BatchExternalId to have EntityAliasId since BatchExternalId is specifically related to the batch, not any of its entities. This should not affect any clients as Alias Screening has not been enabled yet.

Added fields to support implementation of Alias Screening. There are no breaking changes here, so adapter implementations will continue to work as normal without the need of making any change.

Extend configuration to support capturing a list of data keys for document expiry data fields