Question
Cognizant Technology Solutions India Ltd.
ES
Last activity: 12 Aug 2019 8:59 EDT
Design solution for an application which shows data as snapshot but not store them in case
Hi,
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]
Please suggest which option suits the best.
Pegasystems Inc.
US
Sounds like a Saveable Data Page use case.
With a Saveable Data Page you can conditionally source a Connector or a Lookup.
You can use the Building ID to GET the information originally using a Connector.
You can save the response locally using a "Save Data Page" step in a step .
Afterward you can conditionally have the Data Page do a Lookup as opposed to a GET.
Your section does not have to know what the Data Page does "behind the scenes", you case logic controls that.
Cognizant Technology Solutions India Ltd.
ES
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.
Pegasystems Inc.
US
You can configure more than just an empty Page / Field Group property when using the SOR pattern. You can have a real embedded page that contains lookup foreign keys, in your case Building ID.
EX. D_Building[key:.BuildPage.BuildingID]
.BuildPage is an embedded page / Field Group within your case data model.
.BuildPage.BuildingID contains the key to a Data-Building instance.
.BuildPage is configured as "Refer to a data page" not "Copy data from a data page"