Yes, this would work in a 'Set A Condition' action. I didn't even think of that. I guess I'm thinking in programming terms. It still doesn't make sense why that Run If doesn't work. Is it a bug or what?
And now if you have time, and before I can test a 2010 setup, can you switch the run if to "If anything equals" then do a list lookup to the current item, same fields, and then test against the value. Does it still force a YesNo drop down?
What build # of Nintex Workflow do you have on SharePoint 2010? By any chance, was your Run If action within a User Defined Action (UDA)?
In my experience, the Run If action has always handled this scenario properly. You are correct that the underlying value of the Yes/No field resolves to "True" when "Yes" is selected. But even though the Run If configuration displays values of Yes / No in the drop down list these values are evaluated as True / False at runtime.
Anyway, I noticed in the Nintex Workflow 2010 - Release Notes that there was a bug that was resolved in Nintex WF 2.4.3 ("Corrected the evaluation of parameters in the "Run If" and "Set a Condition" actions when included in a UDA"), so if this is within a UDA and your Nintex WF version is prior to 2.4.3, perhaps an update would fix this.
So I got a 2010 farm spun up and tested. Here are my results.
1. Create a custom list
2. Create a column that is type Yes/No
3. Create test workflow
This list item i'm running the workflow on:
It Ran the run if as expected
And My message was in the history!
So it doesn't appear to be an issue with the Run If action. And this was on a 2010, 220.127.116.11 workflow version. Did I follow your steps the same way as you did? I would love to figure out what is causing a difference for you.
And when I flip the checkbox to NO, it skips the log in history action.
Hi Andrew Glasser,
I am new to nintex workflow I am trying to check the checkbox value is checked or not if its checked then I need to send mail.
please help me to achieve this