We've started working on this feature - however the implementation is closer from an ACL than it is from a Yes/No Radio Button.

The way it's implemented is by creating a new validation field type (CheckBox) which is validated by a List (same way as a DDL or an ACL would be). Then all options from the list will be displayed in the field, and checking the checkbox next to each value will result in that value from the list being selected for the field, just like if they were selected in an ACL.

This also means that converting a "Yes/No Radio Button" to this new checkbox may not be completely straightforward: You can create a single List value with whatever text you'll want to display next to the checkbox as the Meaning, and "Y" as the Code. This will behave like the "Yes/No Radio Button" when it's selected, but if it's not checked, the field will be empty, and won't hold the "N" value like a Radio Button would.  This may require some change to your logic if you make the distinction between "N" and "null" in the field value.

Like all other "Accepted" ideas, the current plan - which is always subject to changes - is to deliver this in next PPM version (9.63), tentatively planned for late November/early December.

Comments and further feedback are welcome.

We've started working on this feature - however the implementation is closer from an ACL than it is from a Yes/No Radio Button.

The way it's implemented is by creating a new validation field type (CheckBox) which is validated by a List (same way as a DDL or an ACL would be). Then all options from the list will be displayed in the field, and checking the checkbox next to each value will result in that value from the list being selected for the field, just like if they were selected in an ACL.

This also means that converting a "Yes/No Radio Button" to this new checkbox may not be completely straightforward: You can create a single List value with whatever text you'll want to display next to the checkbox as the Meaning, and "Y" as the Code. This will behave like the "Yes/No Radio Button" when it's selected, but if it's not checked, the field will be empty, and won't hold the "N" value like a Radio Button would.  This may require some change to your logic if you make the distinction between "N" and "null" in the field value.

Like all other "Accepted" ideas, the current plan - which is always subject to changes - is to deliver this in next PPM version (9.63), tentatively planned for late November/early December.

Comments and further feedback are welcome.