In Nintex 2016 (v220.127.116.11), the "wait for item update" action does not allow for multiple conditions. I've read and successfully used Vadim Tabakman's approach (Nintex Workflow - Wait for Item Change) with a loop wrapped around the "wait for item update" on the Modified field, then checking the (multiple) conditions to determine whether or not to break out of the loop and progress the state machine.
Consider the example where the "Wait for" condition is:
What if I wanted to extend this to:
While this can be achieved using Vadim's method above, I noticed that the "wait for item update" has a "match regular expression" as an available operator. Can this be used to check for multiple values on the same field?
However, the issue I'm facing is that myField is a choice field and while I'm allowed to change the operator to "match regular expression", I'm not permitted to enter a regular expression since the choice values are shown instead:
Is this a bug, limitation, or am I doing something wrong?
Solved! Go to Solution.
I'd say it's a limitation. Reach out to support and they should be able to raise it as a ticket with the dev/prod management team.
Did you try just throwing the regex into a variable and selecting "workflow data" and that variable? It seemed to work for me here. I did notice that if the choice column accepts multiple values the choice values are not presented and you can enter the regular expression. So perhaps that could work for you.
Interesting approach Steve, but I'm not sure I follow how the regex action works in relation to the "Wait for item update" action?
My problem was that while "waiting" for a change in the field, I only wanted to proceed if the changed field matched a regex pattern. A separate regex action, as you're suggesting, evaluated prior to the "wait for item update" would not work in this instance, because the input value it's trying to match has not yet changed.
I was thinking just creating a variable with whatever expression is required (even as the default value) and plugging that in to the wait for item update action as workflow data. No need to use the regex action.
Thanks Steve! I originally misunderstood what you meant by storing the regex in a variable, but this works. Intuitively, I thought I could simply enter the value of my regex directly in the Wait for item update configuration form, but instead I need to tell it where to find the regex (e.g. Workflow Data, etc).