Hi Praveen,

By definition a boolean value can never be empty. It is either True or False. So if its unchecked if your using a check box control, you can expect it to be False and that check can be done in the workflow depending on what the result of the check e.g. a split would have an option for custom rules which you can pull the parameter of the boolean to check if False or read directly using the list or read method from the smart object. That should resolve your issue. Let me know how it goes

Ahmad, Technically speaking you are right, but in our case the Yes/No field is non-mandatory and hence could be null.

Anyways, anyone looking for the answer on how to do it, the workaround is to assign the boolean to a text variable in the workflow and then doing the text compare in your decision node.