Hi , I am new to pega so please excuse and guide me through this task .
I have got a Case With three stages , in the first stage i am collecting Customer Information attached in the picture , I am trying to save this Customer Info in DataBase
Step 1 :
From Records , SysAdmin created the below class
Step 2 :
Under the Above Customer class , created the follwoing properties as needed .
Age , City , FirstName , LastName , State , City , Street , Zip
Step 3 :
Under My case XXXX-Exchange-Work-Auto , created a Single Page Property mapping to above class (XXXX-Exchange-Data-Customer)
Step 4 :
The defination of XXXX-Exchange-Data-Customer is
Concrete , does not belong to class Group , and when clicked on Test Connection to DataBase , this is mapped to
to table fsshuffle.pr_other in database PegaDATA.
My Question is , Do i need to create the Data Table (Data Type ) with the above Customer Information ?? and whether should i write a Activicty to do this ?
is my approach correct ??
When i ran the Case the Customer Page is getting displayed and when clicked on Submit Button , its not saving the Customer
***Edited by Moderator Marissa to update categories***
The Pega system automatically saves your work page, but not your data page. If you have created a TOP-LEVEL page whose pxObjClass is XXXX-Exchange-Data-Customer, you would need to do an obj-save of that page yourself.
However, if you created an EMBEDDED page within your work object where the pxObjClass of the embedded page is that same XXXX-Exchange-Data-Customer class, you would NOT need to do an obj-save of that data page (and should not, actually).
In step 1 you created data class from Records--> Sysadmin.But instead of that you can create the data classes from data explorer and it is easy to use also.
As another user mentioned Pega system automatically saves your work page. So all your embedded page data also stored in work page. If you want to fetch that data from all your work objects then you can use Report Definitions(RDs).
In RDs; in column tab follow like "EmbeddedPage.propertyName" like ".CustomerInfo.Age", ".CustomerInfo.City" so on. But it results in performance issues. To avoid that you can go for optimization.