Really disappoint to hear you will not be re-introducing this feature to 365.... I was under the impression from various sources at Nintex that 365 would be developed in parallel to NWC...

Since NWC is also currently missing key features like assigning tasks to SharePoint groups, it is not current practical to migrate to NWC either...

Guess we'll have to continue with 5min loop checks ;-(

Any progress on this.. it's been open over 7 years and has plenty of votes!
Currently having to build complex 5 min loops and checks that are super inefficient and a bit embarrassing really!

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.

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.

Status = Submit
There's just no workaround for this on O365

It is close to a year and no updates. Is this user voice going to be considered?

It would even be better if you could use the "Wait for Field in Current Item" to have a "if field does not equal" option instead of must equal option. But this request is my compromise.

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?

*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

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?

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"

Can we have waiting until "Is Not Empty" or "Not Equal To" as options, as in the OnPrem version. Many times I have actions that are waiting until a fields IS NOT EQUAL to the current value.

The current 'Wait for Event in List Item' runs every time an item is added or changed in the current list. The GUID in that action is an output.

It would be great to have an action where the GUID is the input, so the action only runs when an item with that specific GUID is changed.

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.

is this feature available now?

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!

Is there an estimated timeline when the additional logic will be available on this workflow action?

Any plans,comments from Nintex on this request, it is a serious limitation compared to OnPremise?

Please add Contains, Not Equal, Begins with, Ends With. At least Not Equal to so that we can compare if the Item is Modified

Please add Contains, Not Equal, Begins With, and Is Not Empty. Without these other options, this workflow activity is barely usable.