Introduction

I am building a custom DX component in Pega Constellation that includes the following list-based UI elements:

• Multi-select search box
• Multi-select table

Rendering the UI is straightforward, but I am facing challenges persisting selections for list-type reference properties.

For Scalar properties, updates work fine with triggerFieldChange. For Page List properties, I need to ensure that pageInstructions are correctly generated, so that selected/unselected rows are reflected on the case at submit.

While tracing the OOTB behavior in developer tools, I observed that Constellation triggers a refresh API call with updated pageInstructions, which handles add/delete operations on the list.

As i keep saying every time, that building custom components should be your last resort, but know-hows of working with custom components is always nice to have.

What I Need Help With

From a custom DX component, what is the recommended OOTB approach to:

• Add/remove entries in a Page List using pageInstructions
• Handle multi-select selection and un-selection correctly
• Stay aligned with Constellation’s standard persistence lifecycle

What I’ve Tried

• ListActions (pConn / PCore APIs) – experimented with CRUD operations, but not sure if they’re being used correctly
• save / loadView APIs – partially working, but failing in some edge cases; would prefer not to rely on this approach

Ask

Which pConn / PCore APIs should be used to update pageInstructions for list-type data references from a custom DX component? Is ListActions the right pattern for multi-select add/remove scenarios?

Any guidance or best practices would be appreciated.

Regards

JC