question

Upvotes
Accepted
Andreas.Neidhart avatar image
16 ●0 ●2 ●5

SEQ-8: Audit returning wrong values

I have the following issue, received from a client.

They submit a case through API which results into 2 unresolved matches:

They use SEQ-8 to check the audit of the case to validate if there are unresolved matches that require review. The following issue occurs:

  • 1.)noOfReviewRequiredResults is showing 0
  • 2.)in case there is a possible match that is autoresolved, noOfAutoResolvedResults also always shows 0

Re 1)

{
"query": "actionType==SCREENED_CASE;eventDate>2010-01-01T00:00:00Z;eventDate<2020-01-01T00:00:00Z",
"sort": null,
"totalResultCount": 1,
"pagination": {
"currentPage": 1,
"itemsPerPage": 100,
"totalItems": 1
},
"results": [
{
"id": "0a3687cf-631d-1d24-98c8-eb8c00010541",
"objectId": "0a3687d0-631d-1ad5-98c8-eb8900000be7",
"eventDate": "2018-05-03T01:46:48.431Z",
"actionedByUserId": "0a3687cf-5f54-129b-97f2-419d0000117f",
"actionedByUserName": "Andreas Neidhart",
"note": null,
"entityType": "CASE",
"actionType": "SCREENED_CASE",
"auditEventToDate": null,
"details": {
"detailsType": "ScreenCaseAuditDetails",
"userId": null,
"statusCode": "COMPLETED",
"screeningState": "INITIAL",
"noOfNewResults": 2,
"noOfReviewRequiredResults": 0, --> should be 2
"noOfExcludedResults": 0,
"noOfAutoResolvedResults": 0,
"providerTypes": [
"WATCHLIST"
],
"caseScreenRequestor": null,
"caseSystemId": "0a3687d0-631d-1ad5-98c8-eb8900000be7"
}
}
]
}

Re 2) (secondary identifier Japan used)

{
"query": "actionType==SCREENED_CASE;eventDate>2010-01-01T00:00:00Z;eventDate<2020-01-01T00:00:00Z",
"sort": null,
"totalResultCount": 1,
"pagination": {
"currentPage": 1,
"itemsPerPage": 100,
"totalItems": 1
},
"results": [
{
"id": "0a3687cf-631d-1d24-98c8-fa8e000105fb",
"objectId": "0a3687d0-631d-1ad5-98c8-fa8c00000c5d",
"eventDate": "2018-05-03T02:52:23.202Z",
"actionedByUserId": "0a3687cf-5f54-129b-97f2-419d0000117f",
"actionedByUserName": "Andreas Neidhart",
"note": null,
"entityType": "CASE",
"actionType": "SCREENED_CASE",
"auditEventToDate": null,
"details": {
"detailsType": "ScreenCaseAuditDetails",
"userId": null,
"statusCode": "COMPLETED",
"screeningState": "INITIAL",
"noOfNewResults": 2,
"noOfReviewRequiredResults": 0, --> Should be 1
"noOfExcludedResults": 0,
"noOfAutoResolvedResults": 0, --> Should be 1
"providerTypes": [
"WATCHLIST"
],
"caseScreenRequestor": null,
"caseSystemId": "0a3687d0-631d-1ad5-98c8-fa8c00000c5d"
}
}
]
}

Could you kindly confirm if we're missing something?

world-checkworld-check-one
pic1.png (102.2 KiB)
pic2.png (93.0 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvotes
Accepted
Irfan.Khan avatar image
4.2k ●8 ●5 ●6

Hello @Andreas.Neidhart ,

Regarding the "noOfReviewRequiredResults", I think the value being displayed is correct.

As per the API documentation, "reviewRequired" stands for flag to indicate Review Required after re-screening the CASE for the result. Hence the field "noOfReviewRequiredResults" will show results if there is new information regarding the entity name due to

changes in the WC database for that particular name. The pre requisite for this to be triggered is if the case has been re screened with new details and if there is OGS activated for that case. Let me check this internally and get this confirmed.

Regarding the "noOfAutoResolvedResults" field, there is definitely something strange with its response and is not expected. It should clearly say the number of results that has been auto resolved, instead of retuning a default value 0. I was able to reproduce the scenario and am writing to product team for scrutiny.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.