Scribd
Upload
4 views2 pages

ECS - Enterprise Class Structure

The document outlines the enterprise class structure and inheritance patterns in a system, detailing how rules are accessible at various organizational levels. It distinguishes between abstract and concrete classes, and explains the implications of class group membership on table associations. Additionally, it describes two types of locking mechanisms and the roles of nodes, requestors, and threads in managing data within the system.

Uploaded by

pranaisj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views2 pages

ECS - Enterprise Class Structure

The document outlines the enterprise class structure and inheritance patterns in a system, detailing how rules are accessible at various organizational levels. It distinguishes between abstract and concrete classes, and explains the implications of class group membership on table associations. Additionally, it describes two types of locking mechanisms and the roles of nodes, requestors, and threads in managing data within the system.

Uploaded by

pranaisj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

ECS------------Enterprise class structure

Inheritence---------------is for rule reusability

2 types of Inheritence pattern,Direct

Class structure-------- org-div-unit-imp/fw-Application-work/data/int

 When we create a rule in the org level it will be accessable to all div,unit,application in that
particular class
 When we create a rule in the div level it will be accessable to all unit,application in that
particular class
 When we create a rule in the Application level it will be accessable to all application in that
particular application
 If we created rule in A-B-C-D class in application level but want to access in the A-B-E-F then
need to create rule in @baseclass then all organizations can access.
 First the pega will check the rule in the pattern inheritance which is check its immediate
parent classes. When check box in enabled in respective class
 For Direct Inheritence it will check for the parent class given in respective class rule.
 Whave 2 types of classes Abstract,Concrete
 Abstract means no table associated with that class.

 Concrete class will have table associated in diff ways


 Does not belong to a class group ----------- means this class will have separate table but will
not be shared with other class.
 Is a class group ---------- have separate table but can be shareable
 Belongs to a class group ----------------- this will be for table accessed by the class having Is a
class group.

We have 2 types of locking they are default locking, Optimized locking

default locking:-single person can able to make the changes

Optimized locking:-multiple can lock the same case but changes can be saved by only one at a time.

Data Pages:-

Node has multiple requestors has multiple Threads

Thread------------- for dynamic changing data for each work object

Requestor-----------------particular session for single application can access and only one operator

Node-------------------for static data like server contains multiple applications when data is similar for
multiple applications under single server

Functions in pega:-

Fallout –priororder

What is DQ is done , what are the code is available

Kusuma ,

Verify garantuee and outside Garantee

You might also like