Skip to main content


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

Classes used to create a hierarchy and related instances

Updated on March 4, 2022

During application deployment, you create instances of the following classes:

  • Data-Admin-Organization — defines the top level of the hierarchy
  • Data-Admin-OrgDivision — defines the middle level of the hierarchy
  • Data-Admin-OrgUnit — defines the bottom level of the hierarchy

An organization is the top level of the three-level organizational hierarchy available to all your applications. The middle level instances are known as divisions. (Data-Admin-OrgDivisionclass). The lowest level is the organization unit level (Data-Admin-OrgUnit class). One PRPC system can support multiple organizations. By convention, organization names are in LDAP format — such as pega.com — also called the network domain format. The organizational structure affects Management reporting and statistics visible in the Monitor Activity workspace.

Below organizations, divisions are the middle level of the organizational hierarchy and are designed to correspond to cost centers. Most applications create one or more default division names, see Appendix A, Application-Specific Information. Do not delete these names.

Below divisions, organization units are the next level of the hierarchy, though they are not used in security. The installation process creates one or more organization units. See Appendix A, Application-Specific Information. Do not delete these units. Create one form for each unit. You can create an organizational hierarchy in which organization units report to other organization units, which lets the system model large organizations. This hierarchy does not affect execution.

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.

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

Close Deprecation Notice
Contact us