Pega is all about automating the tasks of the traditional application development. The Data transform is one such feature which helps for the best user experience by auto-filling forms, copying data among fields and even sometimes manipulating the data with the specified conditions. Pega by default inherits the data transform rule called “pydefault” which initializes the property values while creating the case and it also gives the feasibility to create customized data transform rules according to the application requirements.
Let us take a case where we automate the library process:
BOOK ISSUE
- Enter your name & id number
- Scan the book code authorize it with your id
- Book Issue mail is sent to the user specifying that the renewal time period is 1 month
BOOK RENEWAL
After a month the user go to the caseworker asking for the renewal
- Then, the irony is that the caseworker just types the unique id of the user then the rest of the user details is auto-filled.
- Now, If a user returns the book: The Case is dissolved else case updates.
Now, If we started thinking technically the questions we raise ourselves are
- Where the data entered in the fields are stored?
- Will the data in the fields be auto-filled the once after the case is resolved?
- What if we integrate two case types with Inheritance and we badly want the fields to be transformed?
- What if we integrate two applications and we still we need the data transform should happen between the steps of two application?
Yes, Fair enough !! rather than calling the Pega as a tool let us assume it as a software machine facilitating the different processes run simultaneously and executing on par with the request. To complete the processes it has execution engine as well as memory units to store the data.
- Pega stores the data in a persistent layer which is the abstract layer and helps to retrieve the case details even after the case is resolved ( Which can be compared with the primary memory of the system).
- The data storage cannot be permanent always because there is the kind of data which is of no use after a process. Eg: It is obvious and necessary to store the case id in the persistent layer for future use but it is not necessary to store the field values once the case is resolved until that time we store them at the temporary memory called ” Clipboard”.
- Yes, the data transform rules can be implemented at any connector and it is obvious that the fields of base class override the fields of the child class as well.
- Yes, The data transform can happen even if we integrate the two application. That can be happen using API and some representational state transfer protocol where the data transformation takes place through the internet.
// I just articulated what I knew sorry if I went wrong
PEGA 