Property configured as Text that uses a pxRadioButtons as UI Control does not work in a Pega 25 constellation edit view

I have a property that it is configured like this:

I have a OOTB Edit view as this:

So the radio button with the 2 options that I have as field values does not render in the UI. I also tried to used Local list as Table type for this property and the results are the same no radio button at the UI.

I have another property that I use datapage as table type and it works, so does anybody knows what I am missing here?

Oh almost forgot, this ootb edit view it is used in a list view for the same data type.

@MarioM17642831

Based on your screenshots and configuration, the behavior appears to be related to the Table type defined on the property rule. I was able to reproduce the issue locally, and it seems that Constellation does not support radio button properties that use either Field Value or Local List as the table type.

When you create a new picklist or radio-button property through the Data Model tab in the Case Designer (rather than making changes directly in the property instance rule in dev studio) , Constellation automatically uses Prompt List as the table type rather than Local List or Field Value. This table type is supported by Constellation and renders correctly at runtime.

If you do not need separate “Standard” vs. “Prompt” values, you can simply set them to the same values.

Try changing the Table type on your property to Prompt List and verify whether this resolves the issue. It aligned with Constellation behavior in my reproduction.

More generally, I recommend configuring properties via the Data Model in Case Designer rather than editing rule forms directly in Dev Studio. Constellation’s UI rendering logic is tightly coupled with the data model, and modifying backend property definitions outside of that model can lead to the types of issues you’re seeing.

See the example below showing what I mean.

@Marc Alderman thanks for the prompt response, yes that is true, I already had changed to use the prompt list and forgot to update this post. But I do not understand why it does not work with field value neither with local list, also I do not understand why Pega does not make things clear about somethings on constellation, and this is one of the things it should be very clear for us, because we had to burn our brains to find out a workaround. In my humbled opinion somethings is getting worst than before.