The matches returned from api are different from matches shown on the web application

I was using the following request SEQ-2f, 4a, 8, 5b to retrieve the results for the keyword "CHINA":

{
"groupId":"{{group-id}}",
"entityType":"UNSPECIFIED",
"providerTypes":[
"WATCHLIST"
],
"name":"CHINA",
"customFields":[
]
}

and 7 matched results was returned. (using the production api)

However, if I enter the same keyword "China" and select "UNSPECIFIED" to search on the web application, then 8 results will be returned.

May I know the reason and how we could resolve it? Thank you.

Find more posts tagged with

world-check-one

world-check

Accepted answers

Prabhjyot

@henry.cheng,

In order to check the group using the API, you can use the API call - 'SEQ-case-investigate-case-details: Fetch full case details'.

For the UI, you can use the case-Id and filter the search using the group in the case manager.

In order to check the Ids of all the groups, you can use the API call - 'SEQ-pre-groups: Get my top-level groups'

Also, for the issues related in production, you may refer to this link going forward. I will get a support ticket raised for this issue on your behalf and we can continue to look into it.

All comments

Prabhjyot

@henry.cheng,

Thank you for your query.

That's strange! Can you please share the result details from the UI and the API to look into it?

henry.cheng

@Prabhjyot·

Attached please find the results from UI and API. Thanks.

api-results.txt ui-results.png

Prabhjyot

@henry.cheng,

Thank you for sharing the results.

Can you please share the request body of the case?

henry.cheng

Please find the body contents as follows
(SEQ-2f):

{
"groupId":"{{group-id}}",
"entityType":"UNSPECIFIED",
"providerTypes":[
"WATCHLIST"
],
"name":"CHINA",
"customFields":[
]
}

Thanks.

@Prabhjyot·

Prabhjyot

@henry.cheng,

Thank you for sharing the details.

Can you please confirm if both the cases are created using the same group or different groups?

Also can you please confirm if you are using the pilot environment or the production environment for the above case?

henry.cheng

@Prabhjyot·

The issue occurred in the production environment.

About the group, how could I confirm the groups used in API and UI are the same?

Prabhjyot

@henry.cheng,

In order to check the group using the API, you can use the API call - 'SEQ-case-investigate-case-details: Fetch full case details'.

For the UI, you can use the case-Id and filter the search using the group in the case manager.

In order to check the Ids of all the groups, you can use the API call - 'SEQ-pre-groups: Get my top-level groups'

Also, for the issues related in production, you may refer to this link going forward. I will get a support ticket raised for this issue on your behalf and we can continue to look into it.

LuWei.zhang

I have a question talk about
the request word check API method invoke
order.

I will get "matchStrngth" key from result values.

This request API invoke order is

SEQ-pre-groups: Get my
top-level groups
SEQ-case-create-individual:
Save a case: Individual
SEQ-case-retrieve: Get the
system ID of a case
SEQ-case-ogs-enable: Enable
ongoing screening for a case

Is the above correct?

Christiaan Meihsl

@LuWei.zhang

I would suggest posting the second query as a separate question, not as an answer to the first one.
Once an answer is accepted, marked as "correct", the community tends to only look at the accepted answer, and may miss your second question on the same topic. If required you can always refer to the original question by adding a link to it.
Kind regards, AHS

EXPLORE OUR SITES