Conversation
Pegasystems Inc.
CH
Last activity: 25 Sep 2025 11:18 EDT
Checkboxes in Read only view
Hi all, a(n old design) question regarding check boxes and how they appear in a read-only view: We've got some check boxes in the UI, which are unchecked by default. Therefore when user views this case in read-only format (e.g. in the overview panel), such fields display a 'No' value. I get it, this is because this field is a boolean. But I also get that users can find this misleading - Sometimes users need to view the case in read-only even before starting to work on it, so it's confusing that those questions already have answers 'No' next to them.
Have you encountered similar questions? What do you do to solve this? The only thing I can think of is NOT to use checkboxes but use a radio button, so when not answered, the value is null. TIA!
FusionAIx
NL
The answer is what you expect from the end-user during entering the data;
- if you expect that the user either (deliberately) selects either 'yes' or 'no' -> Radio-button control - e.g. "Customer understands the terms and conditions"
- if you expect that the question is set to 'yes' in certain cases, than a boolean may suffice (but it should not lead to confusion) - e.g. "Customer acknowledged the terms and conditions"
Technically you can hide the boolean if it not filled with a when rule if it causes confusion
Pegasystems Inc.
GB
@niuz1I believe your scenario is like this?
The "no" is correct - as that is what the value is "false". As @RonaldDeLignie has said the intent of the field is important. If we need an explicit answer, then maybe a checkbox is not appropriate.
I'd go further than just hiding this field though, I am wondering why we are showing this detail at all? By showing the read only "case tabs" and the same details in forms, we open up the User to be further confused. Once I tick this box or fill out form details, then I don't see this represented in the case tabs. I commonly see this causing user confusion.
- We know that is because the form is inflight information - until its saved/submitted the user has not indicated the data should be saved. Case tabs will only show what is actually saved/submitted.
I would normally not show this until after the right point in the case lifecycle to show that details - this would eliminate the confusion.
