Question
GE Healthcare
PL
Last activity: 21 Dec 2022 11:43 EST
A lot of memory consumed by pzAutoPopulateNamedPageLinks but this property is nowhere to be found
Hello,
During Obj-Open and Obj-Save methods we see constant alerts and increasing time for processing (similar to the https://support.pega.com/question/ootb-activity-causing-pega0035-alerts?), however we can't fins this property anywhere and no clue how to fix this.
The same happening for .pxStatusList and .pzMessageContent.pxStatusList
Does anybody fixed this?
Sincerely,
Olga
***Edited by Moderator Marije to add Capability tags***
Pegasystems Inc.
GB
'pzAutoPopulateNamedPageLinks' is the metadata property used by AutoPopulate internally.
This property is stored in blob but before creating the clipboard page we remove these property so it is not part of clipboard page.
It sounds like you are making use of a special Property known as AutoPopulate property. This property is configured with Data Page and retrieves the data from Data Page whenever we want to retrieve value from it. This feature is known as AutoPopulate Event.
Perhaps Status is one of those. That property only keeps the reference of Data Page, so for keeping the reference it is needed to maintain some meta-data related with configuration between Data Page and AutoPopulate Property. All that required meta-data is kept by property ' 'pzAutoPopulateNamedPageLinks'.
'pzAutoPopulateNamedPageLinks' will be retrieved from Database only in case when AutoPopulate property (eg 'Address ' or 'Status ') will come in use. In case AutoPopulate property is not in use than this property will not come out of Database. So it will not cause any performance issue.
Please try the following
'pzAutoPopulateNamedPageLinks' is the metadata property used by AutoPopulate internally.
This property is stored in blob but before creating the clipboard page we remove these property so it is not part of clipboard page.
It sounds like you are making use of a special Property known as AutoPopulate property. This property is configured with Data Page and retrieves the data from Data Page whenever we want to retrieve value from it. This feature is known as AutoPopulate Event.
Perhaps Status is one of those. That property only keeps the reference of Data Page, so for keeping the reference it is needed to maintain some meta-data related with configuration between Data Page and AutoPopulate Property. All that required meta-data is kept by property ' 'pzAutoPopulateNamedPageLinks'.
'pzAutoPopulateNamedPageLinks' will be retrieved from Database only in case when AutoPopulate property (eg 'Address ' or 'Status ') will come in use. In case AutoPopulate property is not in use than this property will not come out of Database. So it will not cause any performance issue.
Please try the following
- Change the Autopopulate property to 'Refer To a Data Page'
- Uncheck the checkbox 'Save parameters with this property for access on reopen'.
- Now Save the Property.
- Test your OBJ-OPEN
You may need to open a support incident if you require a more in-depth review of your issue.
GE Healthcare
PL
@MarijeSchillern Hi,
I've tried your solution, but while monitoring it, I have a question: will it be the same with "Copy data from a data page" option?
We are using property with 'Refer To a Data Page' to set correct ReasonDesc the moment it needs in the audit - could it be an issue there?
Sincerely,
Olga
Pegasystems Inc.
GB
@OlgaElizova When you copy data from a data page, the data is stored in the property. The data page is not accessed again unless it has a parameter that changes. When the parameter changes, a new data page is created. The impacted data is copied to the property and overwrites the existing data.
This external explanation might help explain.
Does the documentation Data page reference and Use case: Loading data into a page property help you at all?
It might be best if you log a support incident if you need a review of what you have implemented.
GE Healthcare
PL
@MarijeSchillern Hi,
Unfortunately it didn't help me, as alert still in place after change was implemented. And I know the difference between them, but curious if this alert could still be appearing.
It's not clear for me why this metadata is triggering such alert, even if we are not using only small DP (less than 30 results) to reference on a property.
Sincerely,
Olga
Pegasystems Inc.
GB
@OlgaElizova I think it would be best if you log a support incident for this. Please let us know the INC reference if you decide to go down that route.
LTIMindtree
SA
DId the issue resolved by following the above instructions?