System Architect Essentials I

Working with PMF

Lesson: Accessing a PRPC Application
July 2, 2012
 Accessing a PRPC Application

© 2013 Pegasystems Inc. 1

 Accessing a PRPC Application

Welcome to the lesson on Accessing a PRPC Application. In this lesson, we’ll discuss how users access an
application built in Pega 7. Like any enterprise application it requires that we set up users, their roles and
their privileges (or access rights). This lesson provides a brief introduction on the terminology used in Pega
7 for users, roles and the privileges. We’ll look at some examples to understand the relationship of these
concepts. Creation and configuration of these records are not covered in this course since these are usually
done by Lead System Architects or System Administrators.

© 2013 Pegasystems Inc. 2

 Accessing a PRPC Application

A user logging into a Pega 7 system is called an Operator and their information is saved as “Operator IDs”.
An Operator ID can be created manually by administrators or automatically. Each user logging in to the
application must have a corresponding Operator ID record.

This is a sample operator ID record that is in our application. The Operator ID stores the contact information
and other personal details of the user, the organizational setting for that user to determine what cases they
can work on, their managers and lastly the Security settings in terms of the passwords and so on.

© 2013 Pegasystems Inc. 3

 Accessing a PRPC Application

A standard Pega 7 installation comes with a default administrator operator ID that can be used to setup
other users. There are different sets of users accessing the application – an administrator who is involved in
setting up users and their roles, developers who are creating applications and end users who use the
application created by the developers.

© 2013 Pegasystems Inc. 4

 Accessing a PRPC Application

An Access group is a record assigned to each operator. Access groups provide two types of accesses for
the operator – the application the operator can access and the roles that an operator can perform in that
role.

Now that we have defined the terminology let’s see how they are related. In an operator ID record, the
access groups are identified. An Operator can belong to multiple access groups. When the operator logs in
to the system it uses the default access group. Users have the option to switch to a different access group if
there is more than one access group.

The Access group references a record named Application which lists the components of the application.
We’ll learn more about what represents an application in the lessons that follow.

The Access group record lists the portal rules that the user can view. The selected portal is the primary
portal and the secondary portals provide the ability for users to switch to a different workspace if required. In
this case all user portals are added to the developer operator so they can verify how it looks during
development.

Access groups also reference Access roles, Pega 7 comes with a set of standard Access roles for system
administrators, system architects, end users and managers. In most cases, the application also has specific
roles built by lead system architects.

© 2013 Pegasystems Inc. 5

 Accessing a PRPC Application

Lastly, the Portal defines the workspace of an operator. The Portal determines what is being displayed to
the operator after they login to the system.

© 2013 Pegasystems Inc. 6

 Accessing a PRPC Application

Work users are the end users of our applications. They create, update and resolve cases. For example, a
work user can be a customer who is entering a purchase request or a Customer care representative who is
entering the purchase request for a customer on the phone.

Work managers are the people who manage the work users. They manage the workloads, monitor the
activity of the users reporting to them and they can also run reports which help them in managing the work
users.

Business Architects are the users who capture application requirements and define business processes.
They primarily use the application to capture business requirements, model processes and design case
stages and so on.

System Architects are responsible for building the application, they are also referred to as application
developers or application architects.

These roles are shipped as a point of reference and in most cases project teams create additional roles that
are unique for the company.

© 2013 Pegasystems Inc. 7

 Accessing a PRPC Application

Pega 7 comes with a standard portal rule for Case Managers and provides a point of reference for
developers to create customized versions for end user portals. Creation of custom end user Portal is done
by a senior system architect.

Pega7 comes with a portal (workspace) for developers, this is called the Designer Studio. Typically this
portal is used as-is and very little customization is done. If customization is required, it is done by project
teams. Designer Studio has lot of features. We’ll primarily use this portal for doing exercises in this course.
Please take a look at the Tour of the Designer Studio lesson to learn more about the Designer Studio.

© 2013 Pegasystems Inc. 8

 Accessing a PRPC Application

In this lesson, we learned that: Operator IDs store information about the users accessing the application,
Access groups are the groups to which users belong, the system comes with Standard Project roles and
User Portals, the Case manager portal provides a starting point for developers to create customized portals
end users, and we also learned about the developer portal ( Designer studio)

© 2013 Pegasystems Inc. 9