#pega training/ How Pega creates case in the backend? | DEEP DISCUSSION

Guys,

Lets discuss today about

1. C R U D operations for a software product.

C--- Create
R--- Retrieve
U--- Update
D --- Delete

With this 4 operations only any software product will work.

First lets understand what is create?
Create is basically creating a record which will be stored in Database.

Retrieve: Retrieve is basically retrieve the created record from DB.

Update: If any changes/modifications needed in the Created record is called as update.

Delete: If created record is no longer required, then we delete the record from DB.
Lets discuss how we will implement this in Pega.

For that first let me explain from case level.

1. Whenever you create case from portal, how pega creates the case ?
Lets check it out.

This is my case type. If you want to see the case type rule which is created by pega. Then just follow this navigation
Actions--Open

This is the case type rule.

Whenever you create the case from portal pega calls the "pyStartCase" is the initial flow for any case creation.

Let me show you by tracing it.

In tracer settings you should enable flow otherwise you cannot see any flow in it.
Now trace completed for the creation.

Now search for pyStartCase

I think from Pega 8.6 pega has started calling the @(Pega-ProcessEngine:WorkUtilities).pzGetStartingFlow(param.InsClass) function to start the case creation process.

I will show you.

in step 11 in this activity pega is calling the process.

With this function it is calling the pyDefault casetype of the Quote work class.

createWorkPage activity is basically called for creating the case in Pega.

Which creates below two main properties along with other OOTB properties.

1. pyID
2. pzInsKey

pyID is nothing but caseID

pzInsKey is nothing but, its a combination of your workpool and pyID.

Let me show you in clipboard.

Your workpool is defined in your accessgroup Advanced tab.

I hope you know about workpool. Workpool means it has its own dedicated database table whichever casetypes you have created under this will be mapped to workpool table
THat means whatever cases you created from pega, all the cases will be stored under this workpool's dedicated database table.

Lets understand the pzInsKey combination.

pzInsKey = WorkPool+" "+pyId

pzInsKey is unique key property for each the cases.

Don't forget this pzInsKey combination.

Now we have created a quote case right now will see the clipboard.
You should always remember whenever you create a new case pega will create a
"pyWorkPage" clipboard page.

This pyWorkPage will hold all the case level data which is entered by the user.

If you see my example Under my pyWorkPage you are seeing many embbeded properties
like
FamilyDetails
PolicyDetails
PolicyHolder
these three properties I have created for my requirement.

now will see pyId

pyID is Q-7001

pzInsKey PLT-INSAPP-WORK Q-7001

As i told you its a combination of your workpool and pyid.

this is your workpool PLT-INSAPP-WORK
I hope you understand the pzInsKey in pega.

And also pyWorkPage as well.

As i explained earlier, below properties I have created for my requirement

FamilyDetails
PolicyDetails
PolicyHolder

let me show you that as well.

my case pxObjClass is PLT-InsApp-Work-Quote
Lets go to this class from pega app explorer.

Here you are seeing AcceptOrReject and FamilyDetailsAvailable.

How come below properties are shown?
FamilyDetails
PolicyDetails
PolicyHolder

Because properties are coming from inheritance

Let me show you

This class is belongs to a classgroup(PLT-InsApp-Work)

that means all the PLT-InsApp-Work-Quote instances/records/cases will be stored in
PLT-InsApp-Work dedicated table.

Lets see this class properties.

see this below properties are coming from work class.

FamilyDetails
PolicyDetails
PolicyHolder

so all these records will be stored in pc_PLT_InsApp_Work this table.

If you want to see the configuration for table

just follow this navigation.

Records explorer--SysAdmin---Database Table click on it.

Now filter the pc_PLT_InsApp_Work table or workclass PLT-InsApp-Work

See this class is mapped to this table.

To summarize this session

1. You have understood the case creation process in pega.
2. pyDefault casetype
3. pyId
4. pzInsKey
5. pyWorkPage
6. Database table configuration for work class.
7. Workpool

Thank you for watching my video.

in my next video I will explain about how to update a case through an activity.

Please subscribe my channel for more videos.

Thank you for watching.

If you have any questions please comment below.

Please like and subscribe to my channel.
You can follow my most updated knowledge
sharing on my Facebook page.

Please like and subscribe to my channel
#pegatraining #pegandomestresolo #pegacode #lowcodeplatform #lowcodenocode
Pega, PRPC, BPM, PegaPortal, Pega Portal
Pega tutorial for beginners
Pega Training videos
Pega Training for beginners
Pega Tutorial videos

[wvenugopalrao]

Amazing content..Thank you so much Bala👍