Question
Swedbank AB
SE
Last activity: 3 Feb 2018 21:27 EST
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
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:-
- Global Due Diligence – to load the questionnaire for global KYC and collect the names of related parties & submit it
- Related party KYC – to create the KYC cases for related parties captured during global due diligence
- KYC review – to perform the review of the global due diligence questionnaire
- 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
Accepted Solution
Pegasystems
GB
This feature is in 7.31, so you need to upgrade if you can.
Pegasystems
GB
Hi Deva, here are some responses:
1. Initiation of Fulfilment case post the due diligence activity
There is a switch you can use to implement the behaviour you are looking for.
In the OOTB CIB application in the Capture stage, Initiate flow, Define Business Objectives task there is a flag at the bottom of the screen: "Allow product fulfillment to begin for each jurisdiction, as soon as due diligence for that jurisdiction is complete.".
If this is left unchecked, then the Fulfillment will only start once ALL due diligence is complete, however if you check this, then Fulfillment will start for each jurisdiction once the required due diligence for that jurisdiction is completed.
2.Reshuffling of the Due Diligence case stages in GLOBAL KYC case
There is no issue with you reshuffling the order and rules around when to start the Related Party child cases.
Hi Deva, here are some responses:
1. Initiation of Fulfilment case post the due diligence activity
There is a switch you can use to implement the behaviour you are looking for.
In the OOTB CIB application in the Capture stage, Initiate flow, Define Business Objectives task there is a flag at the bottom of the screen: "Allow product fulfillment to begin for each jurisdiction, as soon as due diligence for that jurisdiction is complete.".
If this is left unchecked, then the Fulfillment will only start once ALL due diligence is complete, however if you check this, then Fulfillment will start for each jurisdiction once the required due diligence for that jurisdiction is completed.
2.Reshuffling of the Due Diligence case stages in GLOBAL KYC case
There is no issue with you reshuffling the order and rules around when to start the Related Party child cases.
One note of caution is that outcomes of Related Parties can impact the Global DD that needs to be performed, particularly if EDD is required based on the risk profile inherited from Related Parties. Therefore typically we have seen GKYC not being allowed to complete until all Related Party work is complete. So please validate this with your client.
3.Hide case stages in the summary screen which are being skipped
I am not aware of any roadmap items that would give an issue if you overrode this UX behaviour.
This sounds like a very reasonable requirement from the business users.
Overriding this should be done using standard rules within the Pega model, so we would not anticipate this needing "coding" as such. There is a good CLM style guide that shows some of the key "big ticket" items that we would want to protect. I have attached a pdf that describes this.
Swedbank AB
SE
Thanks for your reply.
We have question on point #1
Currently we are using CLMFS application and we could not find this option. Also as you mentioned this option available in OOTB CIB application, do we need to explicitly install this application. If yes please let us know the process.
Thanks,
Deva.
Pegasystems
GB
The CLMFS install automatically sets up all the CIB content, so you will have it.
I have attached screen shot of the task that enables you to switch on the country specific progress to Fulfillment
Swedbank AB
SE
Hi,
Thanks for reply. We are using CLMFS 7.21version not finding this option. Please find below screen shot for the same.
Thanks,
Deva.