currently we test whether we can upgrade from Pega 7.1.9 to 8.3 and ran into the following issue:
In our application we run an activity step which iterates over a page list. This pagelist property refers to a data page, and the data page gets it´s data sourced from an activity. This means that the mentioned pagelist property is only populated in case it can get / create its data by the mentioned data page activity. If not as you probably know the activity step is skipped since the property is not existing.
In 7.1.9 it works perfectly fine, we populate the data by using the mentioned data page (activity). In 8.3 somehow it doesn´t work for some pagelist propertys (we use different pagelists), for others it does work with the very same data page reference.
I traced it thoroughly and yet couldnt figure out why this is happening, also traced Pega engine rulesets. Here I realized that sometimes Pega checks for a specific Data-Admin-System-Settings instance with the following message : "Looking for instance Data-Admin-System-Settings DATA-ADMIN-SYSTEM-SETTINGS PEGA-ENGINE!DATAPAGE/NEWGENPAGES in the Instance cache " (Cache Hit not found). Maybe there is even no connection to my issue and this setting, however this is one difference I spotted when comparing my 7.1.9 vs 8.3 trace.
Are there any known issue with data pages after migrating? I did some rule revalidation for activities and data pages as well, didn´t help. Restarting the server also didn´t help ;-)
Many thanks in advance, any help would be highly appreciated.
Can you share any screen shots of how the data page is configured and how you are referencing it? When tracing with the Data Pages event type, what messages do you see when the Data Page is referenced?
I tried AutoPopulate too, it shows nothing, doesn´t even pop up in the tracer.
I tried many things, for example creating new page list properties in a higher ruleset version and switchting data access to copy. Also removing the Pega cache by truncating a bunch of (rules schema) sys tables which helped in the past in similar scenarios. Unfortunately it didn´t help.
The only thing which helped was creating new page list properties (with a new name). When I did this and implemented them in this problematic activity it ran as expected. But in our case this would be the worst case because this means we need to create new properties and change a lot of activities which reference these page lists.
So the page list property gets used in our process before we run the problematic activity, so Pega caching obviously "thinks" this page list property already got data access via data page / activity, however the input values changed in the process too. So reloading would be the proper way to go.
How did we find out?
By removing the page list property via Property-Remove method in the first step of our problem activity. When doing this the page list property will call the underlying data page / activity. In Pega 7 this definitely worked different, when page list properties used data access via data page it always called the underlying data page, although the parameters are hard coded / didn´t change.