Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Creating a KYC due diligence case

Updated on June 11, 2021

An important aspect of onboarding a new customer is assessing their integrity. Pega Client Lifecycle Management and KYC provides several cases that you can use to collect due diligence information.

To collect additional information, you can create a new subcase based on existing KYC due diligence subcases. For example, you can add a new due diligence section, Miscellaneous, to the Due Diligence stage that contains a single subcase to collect Crown Dependencies and Overseas Territories (CDOT) regulation information.

For more information about how the existing case is implemented, see Due diligence case creation.

Creating a subclass for reusable assets

Create a PegaCLMFS-Work-Misc subclass to contain reusable assets that are associated with the new subcase.

  1. In the navigation pane of Dev Studio, click App.
  2. Expand the SysAdmin category, and then click Class.
  3. In the editor window, click Create.
  4. In the Label field, enter a short description or a title for the new record.
  5. In the Class Name field, enter PegaCLMFS-Work-Misc.
  6. Click Create and open.
  7. Click Save.

Creating a subclass for specialization rules for new regulations

Create a PegaCLMFS-Work-Misc-CDOT subclass to contain the specialization for the CDOT regulations.

  1. In the navigation pane of Dev Studio, click App.
  2. Expand the SysAdmin category, and then click Class.
  3. In the editor window, click Create.
  4. In the Label field, enter a short description or a title for the new record.
  5. In the Class Name field, enter PegaCLMFS-Work-Misc-CDOT.
  6. Click Create and open.
  7. Click Save.

Including CDOT work types

To include work types for the CDOT case type that you created, add the subcase to the parent case in the case type rule. In the case type form, add a data propagation data transform to propagate data from the child to the parent class.

  1. In the navigation pane of Dev Studio, click App.
  2. In the search box, enter PegaCLMFS-Work-CLM.
  3. Expand the Process category, and then click Case Type.
  4. On the list of records, click pyDefault.
  5. Save the rule into your implementation layer by clicking Save as.
    For more information, see Copying rule or data instance.
  6. In the Child case types section, click Add a row.
  7. In an appeared row, enter PegaCLMFS-Work-Misc.
  8. Click the Data propagation button for the PegaCLMFS-Work-Misc case type.
  9. Click Submit.
  10. Click Save.

Adding work parties for the new Miscellaneous case type

The new Miscellaneous case type requires new case-specific work parties in the pyCaseManagementDefault rule.

  1. In the navigation pane of Dev Studio, click App.
  2. In the search box, enter PegaCLMFS-Work-CLM.
  3. Expand the Process category, and then click Work Parties.
  4. On the list of records, click pyCaseManagementDefault.
  5. Save the rule into your implementation layer by clicking Save as.
    For more information, see Copying rule or data instance.
  6. For each new work party that you want to add, define a new row.
    1. In the List of valid parties section, click Add a row.
    2. Enter the name for the new work party, for example, Misc, MiscManager, or MiscReview.
  7. Click Save.

Creating a flow diagram for a new due diligence subcase

Create a flow to prevent the subcase from completing until the parent KYC cases are complete.

  1. In the navigation pane of Dev Studio, click App.
  2. In the App explorer, expand the CLMProcess categories, and then click Flow.
  3. In the editor window, click Create.
  4. In the Label field, enter the flow name, for example, Misc.
  5. Click Create and open.
  6. In the Diagram tab, add decision shapes that prevent the subcase from completing until the parent KYC cases are complete.
  7. In the Due Diligence stage, include the Misc flow, and then create when rules and service rules to check when to initiate the Misc flow.
    Note: Open and check KYC, Legal, or Tax due diligence flows for examples of how to create your flow.

Creating an activity to reroute workbaskets

Create an activity that checks for a valid work party role. If the party role is available on the case, then the activity checks for the default workbasket that is associated with that work party and assigns the assignment to that work party. If the work party role is not available on the case, then the case is routed to routing_error@clmfs, and the system sends an error message.

For example, if the SSManager role is passed as a parameter, then the activity rule checks the pyWorkParty(SSManager) property rule for a routing workbasket name and assigns the assignment accordingly. If pyWorkParty(SSManager) is not available, then the assignment is routed to routing_error@clmfs.

  1. In the header of Dev Studio, in the search box, enter ToCasePartyWB, and then select the activity rule that is applied to the PegaCLMFS-Work-Tax class.
  2. Save the rule into your implementation layer by clicking Save as.
    For more information, see Copying rule or data instance.
  3. In the Applies to field, enter PegaCLMFS-Work-Misc.
  4. Click Create and open.
  5. Edit the conditions for the when rules as necessary.
  6. Click Save.

Creating a data transform to populate a list of subcases

Create a data transform to populate a list of subcases that are initiated from your new due diligence subcase.

  1. In the header of Dev Studio, in the search box, enter PopulateTaxCasesList, and then select the data transform rule that is applied to the PegaCLMFS-Work-CLM class.
  2. Copy the rule by clicking Save as.
    For more information, see Copying rule or data instance.
  3. In the Label field, enter PopulateMiscCasesList.
  4. Click Create and open.
  5. Edit the actions, as necessary.
  6. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us