Conversation
IDEXX Laboratories, Inc.
Last activity: 29 Dec 2025 14:58 EST
Reusing Pega UI to maintain decision table (checkin/checkout/in branch)
I have issues with reusing Pega UI which is responsible to show the decision table. I tried to add a piece of UI with the table content from the delegation area and from the Dev Studio tabs area (where you simply open the decision table rule) to the Flow Action's section but it didn’t work.
Do you have the same issue? My aim is to not rewrite UI from the scratch.
Pegasystems Inc.
US
Pegasystems Inc.
PL
@len01Configuration Sets are the way definitely.
AleksS: rewriting from scratch solutions from Traditional UI will be a major development work. Consider your business use case and if you can solve it with Configuration Sets.
IDEXX Laboratories, Inc.
@AleksShank you for your input @len01 , @Kamil Janeczek
Our use case of POC is to create a simple process where one could open and close one or several decision tables one by one.
@AleksShis is the reason why I am stick to the decision table UI reuse in my question.
Looking forward to your thoughts.
Aleksandr
@AleksS I believe the new way of doing this is to use Configuration Sets in App Studio. It's not a 100% match of the delegation functionality, but it is an OOTB mechanism that allows you to maintain values / decision tables without needing to deploy application changes.
Here are the docs on Config Sets. The example doesn't show exactly a decision table, but hopefully enough so you can figure out the rest.