Pega Basics

Below are the topics which are covering in this post.

• Operator ID
• Access Group
• Organization – Division – Unit
• Roles & Portals
• Properties
• Status of a Work Object

Any work object  will have the flowing status

• New — Not yet reviewed or qualified.
• Open — Responsibility for processing is with the processing organization.
• Pending — Responsibility for processing is currently with an external organization.
• Resolved-Duplicate — Resolved, as this work object is judged to be a duplicate of another work object.
• Resolved-Rejected — Resolved, not accepted.
• Resolved-Revoked — Resolved, reviewer has ended processing.
• Resolved-Completed — Resolved, work completed.

Operator ID

    An Operator ID is an identifier (ID), a password, and other facts and preferences that are associated with a user. Operator ID is a data instance in Pega, to tell about you (user) and 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.

Operator ID is an instance of the ‘Data-Admin-Operator-ID’ class. Operators are part of the Organization category.

Access Group

    Access Group determines the application accessible to the user, the layout of the user’s home page, and roles assigned to the user.

Every user is typically assigned to Access Group and more than one user can be assigned to the same Access Group.

Access Group is the set of RuleSet versions accessible to a user. It also determines Which Rule Sets appear at the top of their ‘Rule Set’ list. Optionally, Access Group also defines the access roles available to this user.

An access group is an instance of the Data-Admin-Operator-AccessGroup class. 

Organization – Division – Unit 

    Pega Application maintains the organizational structure and it is three-level structure, it helps to manage the RuleSet visible to users in that Organization when they log in. This structure affects management reports and statistics.

An Organization is the top level of the three-level organizational hierarchy available to all our applications. An organization is an instance of the Data-Admin-Organization class.

The division is the middle-level instance. (Data-Admin-OrgDivision class). The unit is the lowest level instance. (Data-Admin-OrgUnit class).

Roles

Pega defines a different kind of Roles,

User

  The end-user of the application, in general, creates and resolves work

Manager

  Creates, approves, resolves and manages work.

  Monitor activities and consumes reports.

Business Architect

  Captures business objectives

  Define business process.

  Creates and manages business rules.

System Architect

  Develops and Builds the system.

System Administrator

  Manages the system.

Portals

Portal is the standard browser-based user interface for Process Commander workers, managers, and developers.

The Portal Rule (Instance of Rule-Portal class) defines the tabs, arrangement, and  labeling of anchors and features known as gadgets.

Can be customized to reflect the terminology, styles, layout, and facilities appropriate to each user community.

Portals available in PRPC are

•User Portal

•Manager Portal

•Business Analyst Portal

•Developer Portal

Properties

Defines and labels a value and that can be associated with Class. Different types and modes of Properties are available in Pega. We also have Pages and Data Tables in Pega to store data in structures. We can also write / declare conditions/rules on properties like OnChange, Constraints, Expressions, EditInputs, Validations, etc.

‘Property’ an instance of the ‘Rule-Obj-Property’ rule type

Properties in Pega are categorized as two types,

1.Standard Properties.

2.Custom Properties

Standard Properties

These are by default provided by the Pega,

Standard properties start with ‘px’, ‘py’, or ’pz’,

These properties are in ‘Pega-RULES’, ‘Pega-IntSvcs’, ‘Pega-WB’, and ‘Pega-ProCom’ RuleSets

Px – The property with the ‘px’ prefix says that, they are Special and values cannot be input by the user

Py – ‘py’ prefix says that they are not special and values can be input by users.

Pz—Pz’ prefix properties are for the internal system processing and values cannot be manipulated by the users, the application uses these values, but cannot set these values.

Custom Properties

These are what we create as per our application requirement, these can be again Scalar (single value) or Aggregate (set of values like Array)

Property Modes: 

         In Pega, we have eleven modes for ‘Property’, they are

Type Value Mode         Page Mode          Java Object Mode          Single          Single Value               Page          Java Object          Array          Value List               Page List           Java Object List          Group          Value Group            Page Group          Java Object Group                Java Property List