Skip to main content


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

Mapping case type or data type classes to a database table

Updated on March 21, 2023

When you run the New Application wizard to create your initial case types and data types, the system creates a default class group mapping for each case type and data type. The wizard also creates associated database tables. The wizard maps the new implementation class to the appropriate database table.

Pega Smart Dispute for Issuers Implementation Guide
Mapping a class to a physical database table affects data storage and security decisions. For example, if you expect the volume of the case types to be low, consider sharing the table with other case types.

To update the default database table to a user-specified database table, perform the following steps:

  1. In the Dev Studio Explorer panel, click RecordsSysAdminDatabase Table.
  2. Open the class that you want to modify.
  3. Review the default database name and the table name that the class points to.
  4. To point the chosen database table to your specific class, edit the database name and table name.
  5. To confirm your changes, click Save.
  6. Click Test connectivity to check if the configuration succeeded. If the test results display errors, for example, missing properties, review the data and correct them.
  7. Update the class to point to the table specified above:
    1. In the Dev Studio Explorer panel, click App.
    2. Right-click the class name that you referred to in the steps above and select Definition.
    3. On the General tab, click Test connection to check if the configuration succeeded.
  8. Perform the steps above for the other case type or data type classes, if needed.

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