Issue
After creating a Flow Action on a Portal and adding a table that is sourced with Operator ID OOTB property ,the values do not populate or persist as expected.
The controls appear to render on the form, but the values entered or set programmatically are not retained when the Flow Action is submitted.
Symptoms
Values entered through a Flow Action on a table fail to save.
Developers who built this pattern in earlier releases may observe it silently break following an upgrade, with no error message displayed to the end user. The impact is data loss at the UI layer — values appear to be entered but are not committed.
Steps to Reproduce
- In Dev Studio, create or open a flowaction .
- Within that Flow Action, create a section and configure editable table with Operator ID property as source .
- Open the Portal and trigger the Flow Action.
- Enter values in the text controls of the table .
- Submit the Flow Action.
- Result: The values entered in step 4 are not saved. Returning to the Data Portal view or inspecting the clipboard confirms the fields are empty.
Root Cause
The Operator ID page (Data-Admin-Operator-ID) is a session-scoped, operator-specific clipboard page. It is designed to hold operator profile and session data, not transactional business data. The session-scoped nature of the operator page causes data persistence to fail — values are not committed across the interaction boundary.
This behavior is by design. The operator page is not a supported target for dynamically added or user-edited page list rows.
Solution
Refactor the implementation to store transactional or user-entered data on the case page (for example, pyWorkPage) or on a dedicated data structure designed for business data management, rather than on the Operator ID page.
To do this:
- In Dev Studio, open the Flow Action on the Data Portal.
- Replace any Page List properties that reference the Operator page with a Page List property defined on the case class (for example, pyWorkPage.<YourPageList>).
- Update the section and its controls to reference the case-level Page List property.
- If cross-context calculations are required (for example, copying a calculated field from one Page List to another), add the logic to the pyRefresh Data Transform on the top-level (work) class.
- Save and test the Flow Action at runtime to confirm that Page List values now populate and persist after submission