Question

6
Replies
670
Views
Deva_Prathapaneni Member since 2014 30 posts
Cognizant
Posted: 2 years ago
Last activity: 2 years 8 months ago
Closed
Solved

Clarification required on CLM frame work

Hi All,

We have few clarification required in CLM framework.

1.Initiation of Fulfilment case post the due diligence activity

CLM OOTB behavior – In Pega CLM OOTB, the country specific fulfilment cases are created in stage 4 (fulfilment stage) when all the cases/stage before this stage are completed. There is no parallel orchestration between stages.

Our requirement – As per the business, once the local due diligence for the onboarding entity is completed for a country, that country specific fulfilment case must be triggered in the fulfilment stage. This is to avoid the delay in the fulfilment activity of the approved geography due to a delay in due diligence of other onboarding countries. This involves parallel orchestration between stages.

2.Reshuffling of the Due Diligence case stages in GLOBAL KYC case

CLM OOTB behavior – In Pega CLM OOTB, the GKYC i.e. Global KYC case type consist of 4 stages as below

a. Related party KYC – to create the KYC cases for related parties captured during Enrich stage

b. Global Due Diligence – to load the questionnaire for global KYC and submit it

c. KYC review – to perform the review of the global due diligence questionnaire

d. Local due diligence – to create cases for local due diligence for each of the onboarding country

Our requirement – As per our business, the related parties are gathered as a part of collection of due diligence data and documents. Thus these are collected during the global due diligence stage and then once the data collection is completed and submitted, the KYC cases for these related parties are created to perform their due diligence. Hence due to this requirement, will it be ok to reshuffle the GKYC case stages as below:-

  1. Global Due Diligence – to load the questionnaire for global KYC and collect the names of related parties & submit it
  2. Related party KYC – to create the KYC cases for related parties captured during global due diligence
  3. KYC review – to perform the review of the global due diligence questionnaire
  4. Local due diligence – to create cases for local due diligence for each of the onboarding country

3.Hide case stages in the summary screen which are being skipped

CLM OOTB behavior – In Pega CLM OOTB, whenever a stage is skipped for a case type – it is still made visible on the summary screen of the case

Our business requirement – As per our business, whenever an entire stage is skipped for a condition – the stage should not be ma visible on the summary screen. This avoids confusion for the business users and gives a flexibility to re-use the case type if only some stage are required

Thus we would like to understand from PEGA GCS , if Pega CLM has any roadmap to achieve the below requirements in future upgrades. Also, if we achieve the same by placing custom code in the current version then will it cause any issues in future upgrades aligning with the Pega CLM future plans.

Thanks,

Deva

Low-Code App Development Upgrades
Moderation Team has archived post
Share this page LinkedIn