Skip to main content

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

Setting up organizations

Updated on March 4, 2022

Pega 8 applications use a three-level organizational hierarchy that you can create and modify as necessary. The hierarchy defines the business reporting structure in nested levels of organization, division, and organization unit.

In addition to the three organization levels, Pega 8 uses work groups to define a group of workers with a common work manager. A work group does not have to follow the organizational hierarchy, however; work groups can include people from various departments in the organization. The importance of work groups to your application is that they are used by flows to route and escalate work. A user who has a worklist to which you want to route work must belong to at least one work group.

Most applications come with a sample organizational hierarchy, described in Appendix A, Application-Specific Information. The application supports extension and growth of the organizational structure as the need arises. As you think about how to define your organization, you may want to look at the business structure of your company and your company’s organization chart.

The organizational hierarchy that comes with Smart Investigate can be extended. Each division in the organization hierarchy also has workbaskets that have been defined. The following shows the organization hierarchy. To leverage this organization hierarchy, copy it to your ruleset.

Pega Smart Investigate for Payments Implementation Guide
  • Previous topic Setting up account number validations
  • Next topic Classes used to create a hierarchy and related instances

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