Skip to main content


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

Adding a new AML CDD profile to the application

Updated on June 11, 2021

Add a new AML CDD profile to Pega Client Lifecycle Management and KYC.

Adding a new AML CDD profile to the decision table

Add the new AML CDD profile to the decision table. The application allocates the new AML profile according to the business logic in the modified decision table.

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Decision category, and then click Decision Table.
  3. In the Decision Table tab, search for and select the decision table that you want to modify, for example, AMLCDDProfileContractingOrg.
  4. Save the rule into your implementation layer by clicking Save as.
    For more information, see Copying rule or data instance.
  5. In the decision table, modify an existing row or create a new one if new logic is required.
  6. In the Return column, modify the decision table to either include or edit a value, for example, MediumCDD.
  7. In the CDD AML Profile rational column, enter the name of a field value that describes the new AML profile value.
    For example: Enter CDDProfile_AMLRational or @baseclass.
  8. Click Save.
    If the new logic requires data that is not available in the PegaFS-Data-Party class, make a copy of the data transform with the same name as the decision table (in this case AMLCDDProfileContractingOrg), with the Init suffix (for example, AMLCDDProfileContractingOrgInit), and then initialize the data.

Optional: Creating a decision table

Create a decision table if the logic of your new AML CDD profile does not fit well in any of the existing decision tables.

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Decision category, and then click Decision Table.
  3. In the Decision Table tab, select any of the AML CDD decision tables listed in your implementation ruleset, and then make a copy of it with a new name, for example, AMLCDDProfileContractingDiv.
    For more information, see Copying rule or data instance.
  4. In the decision table, remove all of the existing rows and add the logic specific to your business scenario.
    Be sure to set default values in the otherwise row.
  5. Click Save.
  6. Create a data transform in the PegaFS-Data-Party class with the same name as the decision table and add the suffix Init.
    For example: Enter AMLCDDProfileContractingDivInit
  7. Add any logic to the data transform that might be required to initialize the data that the decision table uses.
    Leave the data transform empty if no logic is required, for example, all required data is available in the PegaFS-Data-Party class.
  8. Make a copy of the AMLCDDProfilePartyRouter decision table and add a row with business logic that triggers the execution of the new table.
    Ensure that the new row is reachable as expected because the decision table stops executing after the first time that an applicable row is found.

Adding a new AML CDD profile to KYC types

You can start referring to the new AML CDD profile from the appropriate KYC types.

Open the KYC type form and create a local profile configured as inheritance. For more information, see KYC due diligence profile.
  1. In the header of Dev Studio, click the Launch portalKYC Rule Manager Studio.
  2. In the KYC Rule Manager Studio, select and open the KYC type that you need to modify.
  3. In the Type Definition tab, in the Profiles list section, click Add Local Profile.
  4. In the Profile ID field, enter a new unique profile identifier, for example CPMDD.
    The unique identifier can differ from what the modified decision tables return.
  5. In the Description field, provide a description. and select Active based on Inheritance.
  6. From the Active Based On drop-down list, select the Inheritance value.
  7. Click Submit.
  8. In the Item Definition tab, open the items that you want to show or hide based on this new profile, and configure them accordingly.
  9. Save the KYC type.
  10. Optional: To overwrite the Default KYC DD Profile Suite that Pega Know Your Customer Regulatory Compliance provides and add the profile there instead if the majority of your types are impacted, perform the following actions:
    1. In the navigation pane of Dev Studio, click Records.
    2. Expand the Technical category and click KYC Profiles Suite.
    3. Open the rule with name Default that is applied to the PegaKYC-Data-Type-Policies-Global rule type. Make a copy of the Default rule in your implementation ruleset.
      For more information, see Copying rule or data instance.
    4. Click Add Profile and enter the profile data as described in step 4.
    5. Save the new copy of the Default KYC Profiles Suite.
    Result:

    The new profile is available to all of the KYC types under the PegaKYC-Data-Type-Policies-Global class.

Adding a new AML CDD profile to the mapping rule

Modify the DDProfilesMap mapping rule to translate the profile as defined in "Adding the new AML CDD profile to the decision table" to its definition in the KYC Due Diligence profile that is created before.

  1. In the header of Dev Studio, in the search box, enter DDProfilesMap and select the decision table, that is applied to the PegaFS-Work 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 Decision Table tab, add a row to the decision table by clicking the Insert Row button.
  4. In the Customer AML Profile column, enter the value returned by the AML decision table that you create in the chapter Adding the new AML profile to the decision table, see Adding a new AML CDD profile to the decision table.
    For example: Enter MediumCDD.
  5. In the Return column, enter the value that is entered in the Local Profile Suite or in the Default Profile Suite, for example, CPMDD.
  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