Setting up organizations
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.
- Classes used to create a hierarchy and related instances
- Understanding security basics
- Creating smart investigate for payments security levels
- Defining evaluation logic for Rule-Declare-DecisionTree
- Defining the decision table for SetLevel1Instance
- Setting the initial data-admin-operator-security instances
- Creating access roles
- Application privileges
- Associating access roles, privileges, and classes
- Understanding access role obj rules
Previous topic Setting up account number validations Next topic Classes used to create a hierarchy and related instances