Hi Team,
We have a scenario in Pega Constellation where a table is displayed within an assignment. Users can add/edit records in the table using the Add/Edit action.
In Model dialogue need to display picklist whixh is sourced from Datapage with param as pyID.
After selecting Picklist value again this will be source to nested Pagelist column.
As part of the Add/Edit action, we have configured a Pre-Data Transform (Pre-DT) to initialize/default certain values before displaying the modal.
We are seeing different Pre-DT execution contexts between Pega 25.1.1 and 25.1.3.
Behavior in 25.1.1
In 25.1.1, the Pre-DT executes on a TempPage context.
Because the DT is running against this temporary page. We are unable to use current page context fields to load picklists.
Behavior in 25.1.3
In 25.1.3, the same Pre-DT executes against the current Page List record context.
This allows us to initialize properties relative to the current record, which is different from the TempPage behavior observed in 25.1.1.
Case / Assignment
→ Page List 1 – Table
→ Add/Edit Record – Modal (Pick list field)
→ Page List 2 – Nested Table
→ Add/Edit Subsequent Records in a table not on model window.
Within the first Add/Edit modal, the user can add subsequent records into another Page List.
We also have a Picklist within the modal whose source requires the case-level pyID.
Because the user can continue adding records into a nested Page List from within the modal, we cannot simply use pyWorkPage or Top directly. The execution/context can change as the user navigates through the nested Page List records.
What we need is a reliable and supported way to access or propagate the selected Picklist value from model dialogue to load nested pagelist values
Questions
- Is the change from TempPage context in 25.1.1 to current Page List record context in 25.1.3 an intentional Constellation behavior change?
- In 25.1.1, what is the recommended way for a Pre-DT running on a TempPage to access data from the parent case and current page?
- For nested Page Lists, what is the recommended Constellation approach to maintain/reference the original case context when users perform multiple levels of Add/Edit actions?