Wait for field change in current item - multiple values with OR
I would like to be able to say "wait for the field to change to this value OR that value, then do this action" - there is currently no option for entering multiple values.
Anonymous
shared this idea
Please have a look at the condition builder just released as part of conditional start. Is this the kind of condition builder that you need in “wait for field change in current item” ?
23 comments
-
Deanna Velasco
commented
Bump on this. Waiting for a field to change is greatly needed with "Contains, Not Equal, Begins with, Ends With. At least Not Equal to so that we can compare if the Item is Modified" like the others have said.
I am currently using "Wait for event in list item" but it's not working properly. Even though I have it to trigger when this list item's GUID is changed, It's actually triggering every time any item in the list gets updated, so my workflow is continuously looping, bogging down the environment.
I can't use the current Wait for Field Change in Current Item because it requires only a "equals" a value, which is not helpful in my situation at all. -
Anonymous
commented
Status = Submit
There's just no workaround for this on O365 -
Sridhar Kandadai
commented
It is close to a year and no updates. Is this user voice going to be considered?
-
Lucky
commented
Yes, we do need similar condition builder as we have many workflows in on-prem, built using this action. Can we know by when this can be started?
-
Vikrant Behal
commented
*Wait for item update* action in Nintex on-prem enables developer to use different operator based on need. Please enable operators in Nintex online action *Wait for field change in current item action*
e.g. Status != Submitted
-
Srinu
commented
Is there any update on this functionality. Most of our workflow has a condition to continue only after updating a value. So, mostly we used "is not empty". Is there any workaround?
-
Mond
commented
Any update on this functionality? Like Russ H mentioned we need "Contains, Not Equal, Begins with, Ends With. At least Not Equal to so that we can compare if the Item is Modified"
-
Russ
commented
Hi Jon,
Yes that is exactly what we need... Thanks...So surely it's just a copy n paste of the code and we're good to go!!!!! ;-)
Cheers
Russ. -
sushil s pai
commented
is this feature available now?
-
Michael Campbell
commented
I have a lot of Nintex 2013 On Premise Workflows that I have to re-create in our new Office 365 SharePoint/Nintex environment and I am getting more and more frustrated with the changes (and not the better) between OnPrem and OnLine. This is one example; many of my current on-prem forms have an action "Wait for Approval Status to be not empty"......but in Office 365....you cannot do this. The new "Wait for Field Change in Current Item" only allows for a single option. For example, I can wait until the status = approved OR wait until the status = rejected.....but not either!
-
Anonymous
commented
Is there an estimated timeline when the additional logic will be available on this workflow action?
-
Russ
commented
Any plans,comments from Nintex on this request, it is a serious limitation compared to OnPremise?
-
Russ
commented
Please add Contains, Not Equal, Begins with, Ends With. At least Not Equal to so that we can compare if the Item is Modified
-
Keith
commented
Please add Contains, Not Equal, Begins With, and Is Not Empty. Without these other options, this workflow activity is barely usable.
-
Pradipta
commented
Please add Contains, Not Equal, Begins with, Ends With. At least Not Equal to so that we can compare if the Item is Modified
-
Oskia
commented
Add the option to wait a field is empty in the action "Wait for field change in current ítem"
-
D. M.
commented
The fact that you cannot wait for a field to 'not be empty' is incredibly limiting.
-
Cedric
commented
Could you pelase add more options to the "wait for field change in current item" action ?
in Nintex for SharePoint 2010 you have to possibility to use the wait action in order for a field to wait for being filled in... but here this is not possible. you can only wait until a field equals the value of the current field.
this is useless when you want (as I do...) to wait for a column to be filled in with the name of the approvers after the document creation.
Thanks
-
Tim Allison (CDH)
commented
Would love this action to support not equals, is empty is not empty as options. It is difficult to use just equals for DateTime fields.
-
Tom Castiglia commented
Also Contains, Not Equal, Begins with, Ends With