Efficient API Strategy for WC1 Case Creation, Deduplication & Rescreen Workflow

Question

Process till now:

Our organisation has created Cases in WC1 using lseg website.

New process we are implementing:

* Automate the case creation in WC1 using API endpoints.
* While creating cases, we would like to do these validations and actionsa. We do not want to create duplicate cases for the same entity. So we would like to check if the case exists and then call the "Save and screen multiple cases" using bulk operation.

b. If a case exists in WC1 and the status is Unarchived, we want to get the latest screening results using rescreen API endpoint.

c. If a case exists in WC1 in Archived status, We would like to unarchive the case and then get the latest screening results using rescreen API endpoint.

We want to know the best way of doing these API calls to keep the performance under control. Can someone suggest how to handle this scenario?

ram_nitish · Answer

Thanks for the detailed breakdown.

I’ll follow up with you over email to take this forward.

Thanks,

Ram.

Vijay_SPL · Answer

Hi ram_nitish

Thanks for the response. Our approach is aligned with your suggestion. This will work well for screening a single entity end to end.

We plan to execute these steps to retrieve the latest screening status of an existing case in WC1.

[SEQ-case-check-id-availablity]: Check caseId availability

-> [SEQ-case-retrieve]: Get the system ID of a case

-> [SEQ-case-investigate-details]: Fetch full case details for a given case.(LifecycleStatus:UNARCHIVED)

		-> [SEQ-case-update-partial] – Partial update an existing case by its caseSystemId

-> [SEQ-case-investigate-details]: Fetch full case details for a given case.(LifecycleStatus:ARCHIVED)

		-> [SEQ-cases-bulk-archive]: UnArchive multiple cases

			->[SEQ-case-screening-statuses]: Retrieve case screening status

Our requirement is, we will be screening for a quote (internal to our application) which will have more than one entity and also consist of multiple entity types as well. Our concern is that these many API Calls for a list of entities in one quote shouldn't have high performance impacts.

Considering all these API Calls accept only one entity as input at a time, is there any other better way to minimize the API Calls to WC1 to keep the performance within admissible limits?

ram_nitish · Answer

Hi @Vijay_SPL,

Thank you for outlining your requirements. Please find below some guidance and recommendations for each of your points:

1. Automate the case creation in WC1 using API endpoints

Could you please clarify what you mean by “automate”?

2. Avoiding duplicate case creation

To prevent duplicate cases for the same entity:

* You can leverage the [SEQ-case-check-id-availability] – Check caseId availability endpoint.
* This endpoint enables you to verify whether a given caseId already exists before attempting to create a new case. - You may refer to the documentation link here - link

3. Handling existing cases

a. If the case exists and is Unarchived

To retrieve the latest screening results:

* Use the [SEQ-case-update-partial] – Partial update an existing case by its caseSystemId endpoint.
* This PATCH endpoint supports query parameters:

?screen=NONE | ASYNC | SYNC | DELTA_SYNC

You can choose the mode depending on your performance and response time requirements. Please refer to the API documentation link for further details - link
b. If the case exists and is Archived

In this scenario:

* First, unarchive the case using: * [SEQ-case-unarchive] – Unarchive a case

* Once the case is unarchived again, trigger rescreening using: * [SEQ-case-update-partial] – Partial update endpoint with the appropriate screen parameter.

If you're starting your integration, we’re happy to involve an Integration Consultant to help guide you on approach.

Thanks,

Ram.

EXPLORE OUR SITES