Question
WIPRO
IN
Last activity: 7 Mar 2024 6:34 EST
KYCType configuration
Hi - I have a KYCType which is live in production. Now business asking for numerous changes in the questions and the changes should be applicable only for new cases. Inflight cases should continue to display existing questions and behave as it is. Can anyone please advise best way to modify the existing KYCtype such that it works for both inflight and new cases?
***Edited by Moderator Rupashree to add Capability tags***
Accepted Solution
Updated: 7 Mar 2024 6:34 EST
Pegasystems Inc.
FR
@MOHANRAJS7274, KYC types are copied to the pyWorkPage when running Determine Valid KYC Types step at the begining of the Collect KYC Data. Once copied, it will stick with this version in COllect KYC data and KYC Review. So even if there is a new version of the KYC type, it will be copied to only newly created cases executing Determine Valid KYC Types step. However there is a mechanism OOTB that will go through inflight cases to refresh KYC Types with new version. As you don't want that, you need to disable that mechanism. https://docs.pega.com/bundle/client-lifecycle-management/page/client-lifecycle-management/kyc-engine/kyc-configuring/surgical-policy-updates.html
Aaseya IT Services Pvt Ltd
SA
You have to create the new questiion if there is any changes in the question. But you can display the question on based on the requirement.
if you update the existing question it will applicable to all the cases.
Accenture
NL
@MOHANRAJS7274 https://academy.pega.com/topic/managing-flow-changes-cases-flight/v4/in/62316/69216/67331
check this link. Approaches 2 3 and 4 might work for your requirement
Bits in Glass
IN
@MOHANRAJS7274 you can circumstance the kyctype rule based on pxCreateDateTime. So cases created after deployment will use the latest rule, existing cases will use base version of rule.
Accepted Solution
Updated: 7 Mar 2024 6:34 EST
Pegasystems Inc.
FR
@MOHANRAJS7274, KYC types are copied to the pyWorkPage when running Determine Valid KYC Types step at the begining of the Collect KYC Data. Once copied, it will stick with this version in COllect KYC data and KYC Review. So even if there is a new version of the KYC type, it will be copied to only newly created cases executing Determine Valid KYC Types step. However there is a mechanism OOTB that will go through inflight cases to refresh KYC Types with new version. As you don't want that, you need to disable that mechanism. https://docs.pega.com/bundle/client-lifecycle-management/page/client-lifecycle-management/kyc-engine/kyc-configuring/surgical-policy-updates.html