Posted: 9 Aug 2019 3:03 EDT Last activity: 12 Aug 2019 8:59 EDT
Design solution for an application which shows data as snapshot but not store them in case
i need some help for design for the below requirement. Pega is a internal application and need to show in screen some entities like bulding details etc... but pega doesn't have this information. This info comes through GET of a Microservice . Pega should store only building id in case and do aget whenever required to show the info in UI. Now question is how to store the information of building ? I have explored several options as below, need some suggestion which might be the best
Do GET in PRE datatransform of flow action using datapage and copy data to pyworkpage.building and in POSt DT remove the info. [not very much maintainable as new fields introduced have to remove manually]
Create a building single page in pyWorkPage which refers to datapage which in turn does a GET , later remove the building Info in POST DT [Still data is stored in pyworkpage and needs to be removed manually]
Create a Top level page Building independent of pyWorkPage and show the buiilding section on this named page in pyWorkpage and later in POST DT remove the top level page. [easy to implement and maintain as whole top level page is removed]
Thank you for the response . The problem with saveable datapage is , according to requirements Pega shouldn't store any information apart from building id locally. Each time it needs to show building info, a GET to building block will be done and then immediately discarded once assignment is finished.
I found another option in the property rule Advance tab to skip saving. Not sure that is a valid solution.