@surinder.kumar

After the compliance team has resolved the case as Positive-Declined in the WC1 UI, in the back end, the "resolutionStatus" attribute of the result set gets changed to:

"resolution":{"statusId":"0a3687cf-65b4-1aaa-99b1-9b030000282e","riskId":"0a3687cf-65b4-1aaa-99b1-9b030000282d","reasonId":"0a3687cf-65b4-1aaa-99b1-9b0300002825"

Kindly note if the case has not been resolved, the value that the resolutionStatus will bear is "null".

So in order to identify if the compliance team has declined/approved a client, you need to find out if the "resolutionStatus" has a value different than "null". You can use the API call "

SEQ-case-investigate-results: Get screening results" to fetch the result set and to find out the value of the resolutionStatus attribute. The key here is to find out the value of statusId, riskId and reasonId and what each stands for to make sense of whether the case was marked as positive, false, etc.

You can use the API call "SEQ-1f: Get the resolution toolkit for a group" to find out which statusId value found in the resolutionStatus attributes corresponds to which status. It is important to use the correct group Id to fetch this JSON of this API call as the resolution toolkit and its values changes for each group.

Regarding the question, "Since user is declining it on WC1 site, should this rescreening call be resulting in flag or not?"

This will not result in any flag. As this has been marked as Positive, only the resolutionStatus attribute would change. But kindly the event that changes the resolutionStatus is the action of resolving cases and not rescreening. Rescreening the already screened case, would make our system to search for new hits if any or updates on the existing matches. In both cases, the re screening would not update the resolutionStatus of any match. If you re screen the case and the WC1 system finds that there is an update on the match that was previously marked as positive/false or resolved in general, only then it would raise a flag. The flag would be in the form of marking a change in the attribute "reviewRequired".

As you can see currently, the "reviewRequired" has the below values:

"resultReview":{"reviewRequired":false,"reviewRequiredDate":"2018-11-08T00:00:00.000Z","reviewRemark":null,"reviewDate":null}

If there was a new update on this already resolved case due to re screening today, the above JSON would change to

"resultReview":{"reviewRequired":true,"reviewRequiredDate":"2018-12-12T00:00:00.000Z","reviewRemark":null,"reviewDate":null}