Operator Roles in PEGA
In any project team, we have different team members playing different roles. There are a project manager, business analyst, architects, designers, developers, testers, quality analyst etc. in the team who play a different role in the team.
Anyone who can login into PEGA PRPRC system is called Operator. Each of the operators has an Operator ID and password, and they are attached to an access group.
In PEGA PRPC system there are seven pre-defined standard roles. These are following
Every role has its own portal. A business analyst role requires capturing requirements and design process and workflow for the application. To perform their role business analyst, they have to go to the Business Architect Portal.
A System Architects or application developer need to design the user interface, business logic, process rules, etc. so they go to Designer studio portal to do their work.
An End-user or work user is one who actually uses the application. The end user has their own Case Worker portal where they go and create work items.
A Work Manager goes to the Case Manager Portal to approve or reject the works submitted by the work users.
PEGA PRPC system allows us to create additional roles.
How To Create Operator ID In PEGA PRPC ?
Purpose Of Operator ID Creation In PEGA:
An Operator ID data instance provides a user identifier (ID), a password and other facts and preferences. This data instance also locates a user within an organization structure and identifies appropriate access roles and other characteristics.
An Operator ID data instance is sometimes called a profile. To view your Operator ID instance, click the link containing your name in the Designer Studio navigation panel.
Administrators can create new Operator ID data instances. All users can view, but not alter, information for themselves on the Operator tab. Managers can update information on the Operator tab. Through the profile display, users can change their own password.
To list all Operator ID instances in your system,
select–> Org & Security– > Organization > Operators.
These core tutorials will help you to learn the fundamentals of Pega. For an in-depth understanding and practical experience, explore Pega Training.
The Data-Admin-Operator-ID class contains Operator ID data instances. They are part of the Organization category.
Operator ID instances are normally stored in the PegaRULES database as rows of the pr_operators table.
When you save an Operator ID data instance, if the Associated RuleSet is [none], the system completes this field with a RuleSet from the current application. This association assists with application packaging. You can update the associated RuleSet using the field in the upper right corner of the form. See Identifying parts of rule and data forms.
If there is no RuleSet associated with the data instance (for example, for existing instances not previously associated with a RuleSet)
Operator ID Creation for Organization
Three data instance names together identify the organization, division, and unit that this operator belongs to.
|Change Organization Unit||Click to select an organization, division and unit from the pop-up window.|
|Work Group||Select the name of a work group (a Data-Admin-WorkGroupinstance). Work groups are the basis of many standard management reports.
The system does not constrain work group membership based on organization structure. Members of a work group may belong to different organization units, divisions, or even different organizations.
|Reports To||Optional. Select the Operator ID of another user to whom this operator reports.
The specified value is used by the display shown when you click Reporting Structure. The field has no additional uses.
|Reporting Structure||Click to display the reporting structure for this operator, based on the values specified in the Reports To field for this operator and for other operators. A new window opens displaying the reporting structure. The system assembles and displays a hierarchy (tree) view.
In the displayed hierarchy, the names of operators who are not available are marked with a distinctive light blue background.
For in-depth understanding of Pega click on