Skip to main content

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

Copying Database Table instances to your class hierarchy

Updated on March 4, 2022

You must copy the Data-Admin-DB-Table instances for MyCoSI- classes to your class hierarchy to specify the correct database tables for your new classes. This includes all the classes that begin with MyCoSI except the instance for MyCoSI-Work (which you created using the Direct Inheritance wizard), as well as the instances for History-MyCoSI-Work and Index-MyCoSI- WorkParty.

To copy DB Table instances:

  1. Open the Records Explorer, expand SysAdmin and select Database Table. A list of instances appears.
  2. Scroll down the list until you see MyCoSI- and open the instance. The Database Table form appears.

  3. Click SaveAs.
  4. Change the Class Name field, replacing MyCoSI with ClassName. (You only need to replace the MyCoSI portion of the name with your class name.) Click Save As to save the instance in your class.
  5. Change the Short Description field to replace MyCoSI with ClassName when appropriate.
  6. ClickSave.
  7. Repeat steps 3 to 6 for each instance in the MyCoSI- class.
  8. Repeat steps 3 to 6 for each instance in the History-MyCoSI-Work class.
  9. Repeat steps 3 to 6 for each instance in the Index-MyCoSI-WorkParty class.
    Note: For the instances of ClassName-RM- classes created, it is expected the Database property will also need to be updated when PegaRESEARCH Manager integration occurs.
  10. Open the Access Group instance from the operator instance and navigate to Advanced tab. Update the work pool to <Application name>-Work.
  11. Open the application definition of the newly created implementation layer and delete SmartInvestigateForPayments_Sample entry. Click the Savebutton.
Pega Smart Investigate for Payments Implementation Guide

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