FYI, since this feature was very impactful, we've decided to defer it to PPM 9.64. It should be available very soon for testing on PPM Beta for anyone participating in our Design Review program.

Thanks for the update Etienne - i am happy with the logic MicroFocus is going with. 

Hoping to see this come out soon  

Ajay

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.

Absolutely get that and therefore parked it here; lets see how much of traction we get here.

with re: to screenshots it is just an example, the Yes/No radio button only has options like yes and no.. the dropdowns above has Yes and N/A (so only reason the business preferred a checkbox is if they dont select anything it means N/A according to them)

Anyways this is one use-case but the underlying fact is check box will be useful and impactful when it comes to user experience - that is my take. 

I get that Checkbox would be the best option here, but yes/no button would also be better than DDL on your screenshot, so in the meantime you might want to leverage them for immediate usability improvement.

Adding a new validation type is a significant & impactful change, so the votes bar before we consider it for implementation is pretty high - in other words, it may not be available any time soon and anything already available it worth considering.