Skip to main content

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

Creating the custom accounts class

Updated on October 19, 2020

You extend an accounts class by creating and configuring a custom accounts class that inherits from the PegaMarketingFS-Data-Customer-Accounts base class.

  1. In the header of Dev Studio, click RecordsSysAdminClass.
  2. On the Class tab, from the list of results, click PegaMarketingFS-Data-Customer-Accounts.
  3. On the Marketing account data tab, click Save as.
  4. In the Class Record Configuration section, in the Class Name field, enter the name for the new accounts class: Customer-Class-Accounts
    Customer-Class is the name of your custom customer class.
  5. Click Create and open.
  6. In the Keys section, ensure that only the correct key is listed.
  7. In the Class inheritance section:
    1. Ensure that the Find by name first (Pattern) check box is selected.
    2. In the Parent class (Directed) field, enter the base accounts class: PegaMarketingFS-Data-Customer-Accounts
  8. To either point to the base accounts table (pmfs_acct) or to use the custom table created for accounts, update the database rule for the class.
  9. Click Save.
  10. To validate that the class is pointing to the correct table, in the Test connection section of the accounts class, click Test connection.
  11. On the External Mapping tab of the class rule, specify the properties that are available on the accounts record and their backing columns in the accounts table. Ensure that these mappings meet the following requirements:
    • The column name does not exceed 27 characters
    • The property name starts with a period
    • The table does not contain empty rows
  12. 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us