Introduction of Pega Organization Structure and Its need

What is Pega Organization Structure? 

Every Organisation, depending upon its purposes, structured itself in many dissimilar ways. Its can be physical or efficient. An Organizational structure defines how work, task or undertakings are directed toward the achievement of organizational aims. It involves activities like task provisions, organisation, monitoring, reporting, managements, access and delivery of responsibilities etc.


When it comes to Pega organisation structure it is not essential that we will map actual present organisation structure of a company directly into Pega. Resolution will be same but drawing in Pega can be different.


To implement in Pega PRPC, SMEs, BAs and LSAs study the association thoroughly during requirement assembly sessions or Pega DCO sessions and map the administrations in efficient structure based on factors like access supervision, securities, work routing logic, reporting structure etc. This mapping is named as Organization Structure in Pega



Organization Consist of below module

Organization – This is Top layer of organisation construction

Separations are net layer under Societies. Organisation can be divided into various separations either on Functional basis or geographic basis

Units is 3rd level in administration ladder. More units layers can be moulded under a unit layer, but in most of cases only 3 Level administration hierarchy is preferred. All supervisory layers under Division layers are Units

Operators – Users of presentation

Work group – Alignment based on various business meanings

Workbaskets – It can be reflected as a Queue in which work item will stay till some operative will pick it to work upon

Calendar – this is business calendar specific to a business

Group, Division, units together can be termed as Organization Grading


What is need of Pega Organization Structure? 

Pega Applications help institutes to accomplish their work and tasks. To get work done, all pega request needs organisation structure directly or indirectly.


In Real time there can be requests like:

Providing access to some functionality across entire administration. Example, Grant access to company access to Employee Leave organization application

Restrict access of application functionality on Partition Level. For example, HR Department should not have access to Shipping Section Delivery management claim

Overpowering of Work Items. For Example, Leave Request of an employee should be automatically route to his broadcasting manager or HR or Both. Or In Bank Loan claim, if Loan request should be mechanically route to Bank manager for approval

Reporting based on various divisions and units

In absence of Administration structure we may need to do hard-coding and write to many lines of code to achieve above functionalities and that too will not be a flexible solution. For Example, Lets imagine, one-time in future HR Department moves under Admin Division. What will happen to your hard-coded logic? Explaining the problem will be no less then hell.  But using Pega PRPC such scenarios can be moved using centrally defined organisation structure.

For More Details About Pega Online Training Contact us @ +91 9550102466Untitled design

Comments are closed