Unable to establish Reference to Node Data Page In Strategy
SummaryIn Decision Strategy Manager (DSM) 7.2.1, when executing a strategy, and accessing a page list property back by a reference to a Data Page; the value from the page list property is not getting set on to the proposition, and the reference is not being established.
Issue cannot be replicated in base Pega 7.2 with DSM 7.2.1, but it is reproduced only in client environment with Pega 7.2.1 with HFix-26258 installed.
Error MessagesNot Applicable
Steps to Reproduce
1. Create a node level data page as a page list and:
(a) Create a page list property of the same type as the node level data page
(b) Configure to "Refer to a data page" using the Data Page created from step 1
(a) Create a strategy on the same class where the page list property is created
(b) Configure the strategy to import one proposition, followed by a set property that access the page list property with any index, and any property (for example, Primary.PageListProperty(1).pyNote)
3. Run the strategy, and observe that .pyNote is not set onto the proposition, nor does it establish the reference.
Root CauseThis is a side-effect of HFix-26258, which addresses performance issues.
After installing this hotfix, systems will behave such that the content of the primary page when initiating a strategy will be transformed into a DSM page.
Consequently, because DSM pages do not support declaratives at this moment, it cannot handle the loading of Data Page automatically.
Any embedded property reference (even if it's backed by Data Page) is resolved as if it is a normal property due to this limitation.
This behavior introduced with the performance hotfix is driven by the Dynamic System Setting "dsm/clipboard/optimize", which will default to "true" if not set.
ResolutionUser is able to get the system to function with the Dynamic System Settings (DSS) created and set to false.
Published May 11, 2017 - Updated May 23, 2017