Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!


If you have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Add a new idea Subscribe
Status Completed
Workspace Nintex Automation Cloud (formerly Nintex Workflow Cloud)
Categories Workflow Designer
Created by Russ Hancock
Created on Sep 2, 2020

RELATED IDEAS

Wait for Field Change in Change item

NWC desparately needs this action, with the same flexiibility and comparisons that are available in Nintex Workflow onPrem.
Please DON'T implement the same version as currently in Nintex for Sharepoint 365... that verison is missing the power of it predecessor.
  • Attach files
  • Russ Hancock
    Reply
    |     Sep 7, 2022
    The suggestion from support is that we have to build loops that re-query the values in the Sharepoint list. Even if I could get this working it seems hugely in efficient to loop every 5mins to simply look for a value change, that could exist in this state for days or weeks....
    OnPrem had a single action, wait for filed update, that included a full set of comparisons.
  • Gavin Adams
    Reply
    |     Sep 7, 2022
    Hi Lisa,
    The office 365 action 'Wait for field change in current item' is more limited when compared with the Sharepoint on-prem 'Wait for an item update' action.

    The key difference is the ability to select a particular operator.
    (see attached screenshot).

    Of most value is to enable a comparison of 'not equal to' a value.

    The office 365 version has no operator selection. You can only select a field and a value and 'equals' in the only operator.
  • Russ Hancock
    Reply
    |     Sep 7, 2022
    Hi Lisa,
    What Gavin said below..! basically a full set of comparisons, as shown in the screenshot...
    But also available against all field types... for example date fields and People pickers..

    A common requirement for us is waiting for a person to be assigned within a form field... or choice field not blank...

    But basically, the full set of operators against the full set of field types would be perfect!
    Thanks.