Pega Client Lifecycle Management and KYC 8.7 Post-update tasks
The topics in this section briefly describe the new features introduced by Pega Client Lifecycle Management and KYC 8.7 and the next steps for their adoption. Review these topics to ensure that your implementation uses the latest features available as soon as possible and a smooth transition into the new version of the product.
New features
The new version of the application comes with various features. Some of the features introduced in the new application version are active by default without any additional configuration after the update. Other features need to be activated and configured by an administrator to avoid disruption.
To identify the new features which might require activation, configuration, or both, use the following table. For more information about the required configuration, see the Implementation Guide on Pega Documentation.
Features available for updates from any previous application version
| Feature | Description |
| Generation of PDF documentation | The new version of the product uses compact styling for PDF document generation. If you update a Pega Client Lifecycle Management instance from an 8.6 or earlier version, any styles that you might have customized for the generation of out-of-the-box documents must be moved into compact styling CSS extension (pyCompactStylesforPDF_Ext). For more information about the activation of the new orchestration modes, see the Implementation Guide on Pega Documentation. |
| Background processing using queue processors | There are multiple background processes in Pega Client Lifecycle Management implemented using queue-processors. The new version of the Pega Platform, 8.7, introduces some changes in the default number of partitions associated with queue processors and their overall throughput capacity. While these changes will not impact the majority of queue-processors and deployments, they might impact some queue-processors of extensive use like AsyncProcessing or TrackKYCTypeUpdates under certain load conditions. Monitor those queue-processors in your production environment and ensure items queued have reasonable waiting times (see PEGA0137: Ready-to-process items not picked by queue processor). For more details, see Pega Platform changes with update impact. |
Features available for updates from the 8.5 version or earlier versions of the application
| Feature | Description |
| Due diligence orchestration modes | The orchestration process that controls the lifecycle and dependencies of due diligence cases (AML Global, AML Local, Regulatory, Tax) is modified to support different orchestration modes that allow customers to group KYC questionnaires and cases according to their operational and regulatory needs. For more information about the activation of the new orchestration modes, see the Implementation Guide on Pega Documentation. |
| KYC smart filtering | A new filtering mechanism is introduced in 8.6 to improve performance during the applicability of KYC types. Customers with a high number of KYC types and or complex applicability logic based on decision tables see performance improvements during the assessment of applicability. For more information about the activation of this functionality, see KYC Engine Configuration Guide on Pega Documentation. |
| KYC rule database tables | KYC rules are stored in the platform table pr4_rule. The update to 8.6 automatically migrates the KYC rules into new dedicated database tables (kyc_type, kyc_supporting_evidence) that provide more flexibility to the solution. In the unlikely case that you have some custom functionality pointing to these tables, you need to make it a point to the new tables. |
| KYC circular dependencies | Some circular dependencies in visibility conditions between KYC items required that some customers included explicit invocations to EvaluateItems from on-change data transforms. This logic is now available in the KYC Core Engine to manage the dependencies without additional changes. To avoid unnecessary performance overhead, you can remove the explicit invocations to EvaluateItems now. For more information, see KYC Engine Configuration Guide on Pega Documentation. |
| Third-party components activation | The 8.6 introduces few changes in how the components used to obtain data from third-party data providers are managed. Before this version, the system checks for the presence of the components in the stack to decide whether to execute the associated business logic. A new configuration mechanism is introduced to give some more flexibility to that process. If you want to leverage this functionality, the configuration mechanism must be activated after the upgrade. For more details, see the Implementation Guide on Pega Documentation. |
| Pega Known Your Customer for Financial Services rules deprecation | In 8.6, Pega Known Your Customer for Financial Services is sunset as a product and its main capabilities, and rules are now part of Pega Client Lifecycle Management and KYC. The rules that made up Pega Known Your Customer for Financial Services reference application are officially deprecated. For more details, see Deprecated rules. |
Features available for updates from the 8.4 version or earlier versions of the application
| Feature | Description |
| Requirements and document collection | The 8.6 version of the application includes major changes in the requirements and document collection functionality Requirements Next Generation (RNG). By default, this new functionality is not active after the update. The system behaves in the same way as in previous versions, and the feature requires activation and configuration. For more information, see the Implementation Guide on Pega Documentation. |
| SWIFT KYC | The new version of the application supports the enrichment or creation of cases from customer data that is available at SWIFT KYC. This functionality is disabled by default and requires activation. For more information, see the Implementation Guide on Pega Documentation. |
| Related party data-model | In order to implement the enhancements in the related party management functionality that are introduced in the 8.5 version, a few changes were made to the data model. During the update to the newest version of the application, the system automatically takes care of the data transformation for you. However, if you have some customization in that area, you must make additional changes to ensure continuity. For more information, see chapter Managing related parties > Updating from a previous version to 8.5 in the Implementation Guide on Pega Documentation. |
| Relationship codes and entity type | The new version of the application includes changes in the existing relationship codes and entity types. If you use default values, you do not need to do anything to pick up these changes are visible automatically. If your organization changed the default values, you might need to assess how the new values impact your implementation. For more information about access to these two data types, see the Implementation Guide on Pega Documentation. |
| Master Profile loading mechanism | To reduce the memory footprint of the application, the data page that gives access to the Master Profile imposes a limit on the number of active instances in memory. You can configure default thresholds and the availability of this functionality. For more information, see the Implementation Guide on Pega Documentation. |
| Retail Web Self-Service | The Uplus WSS demo application that was included in earlier versions of the application is replaced by the new Pega Retail Web Self-Service demo application. For more information, see Pega WSS demo application. If you used this demo asset to show the product capabilities with your earlier application version, discard the Uplus WSS configuration and configure the new one. For more information, see the Implementation Guide on Pega Documentation. |
| Group Management | The Group Management functionality is extended in the new version of the application. To make full use of the new capabilities, see the section Database Column Mapping in the Implementation Guide on Pega Documentation. |
| KYC declare indexes | The declare indexes that enabled the reporting on KYC types and items that present significant performance issues are deprecated. Disable these indexes by changing the PegaKYCFS/EnableDueDiligenceIndexing dynamic system setting to false. If your organization needs to report across KYC types, consider exporting the data for its consumption in an external reporting system. For more information, see the KYC Engine Configuration Guide on Pega Documentation. |
| KYC questions complete condition | The complete condition on KYC questions has been made mandatory to show in the UI the completion status of a KYC. These changes come into effect when KYC Types are saved using the new KYC Engine. If you want to use this functionality, you must review all KYC questions and create when rules for denoting the completion of Complex questions. |
Features available for updates from the 8.3 version or earlier versions of the application
| Feature | Description |
| Supporting Evidence | The Supporting Documents feature is replaced by the Supporting Evidence feature, which can be configured to support a wide range of evidence types. The KYC Types that are built on older versions of the KYC Engine continue to support the Supporting Documents feature, but they are automatically upgraded to use the new Supporting Evidence feature. For more information on this feature, see the KYC Engine Configuration Guide on Pega Documentation. |
Features available for updates from the 8.1 version or earlier versions of the application
| Feature | Description |
| Asynchronous processing | From the 8.2 version and earlier, the application changes the method of running certain operations at different points of the case lifecycle. Heavy operations, such as the transition between the Capture and Enrich stages or the creation of KYC cases, are moved to background processes to improve the user experience. After updating to this new version from the 8.1 version and earlier, you experience a change in the behavior of the application. No additional configuration is required to activate this configuration. However, you can change the default behavior or extend that behavior to other processes. For more information, see the Implementation Guide on Pega Documentation. |
| KYC Policy Profile | To make the master profile more lightweight and enable faster access, KYC Types are externalized to the dedicated table. No additional configurations are required for adoption. However, if your implementation accesses the KYC Types on the master profile using the D_GetMasterProfile data page, update the references to pass an additional parameter to fetch the KYC Types. |
Features available for updates from the 7.3 version or earlier versions of the application
| Fature | Description |
| KYC Engine | The performance of the KYC Engine is improved by using the latest Pega Platform features. If your application customized the engine in any way, you can use the legacy engine by setting the dynamic system setting UseLegacyKYCEngine. However, the legacy KYC engine will be discontinued in a subsequent release. To ensure continuity of the implementation, all of the customizations built on the legacy Pega Know Your Customer for Financial Services Engine must be migrated to the latest version of the engine using strategically placed extension points. |
Reviewing changes in the base application
To evolve the application functionality and improve its maintenance, some of the rules might be deprecated or withdrawn in the new version. These changes do not affect standard implementations, but may affect customized implementations. Review the deprecated and withdrawn rules to ensure that they do not impact your implementation of Pega Client Lifecycle Management and KYC. For a detailed list, see Deprecated and Withdrawn Rules on Pega Documentation.