Russ

My feedback

  1. 37 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  5 - Nintex Workflow Cloud » Workflow Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Russ commented  · 

    This is critical to adoption of NWC, both onPrem and Nintex for o365 support task assignment to Sharepoint Groups.
    It would be impractical to a modify the WF everytime some joins/leaves the Sharepoint site.

    We use multiple Sharepoint online groups to easily manager task assignment to teams of users.

    looks like NWC is back on the shelf until there is an answer to this...

    Russ supported this idea  · 
  2. 228 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Russ commented  · 

    any update on this... no response since 2017! and has a significant number of votes...
    Simple text based audit is essential, visual as per onpremise would be ideal, but not a key requirement.

    Russ supported this idea  · 
  3. 23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  5 - Nintex Workflow Cloud » Workflow Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Russ commented  · 

    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.

    An error occurred while saving the comment
    Russ commented  · 

    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.

    Russ shared this idea  · 
  4. 32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  1 - Nintex Workflow for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Russ commented  · 

    What's the point in being able to build a validation rule, but then not being able to highlight the particular people picker field that failed the validation... surely this is an easy one to fix?

    Russ supported this idea  · 
  5. 33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  5 - Nintex Workflow Cloud » Form Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Russ supported this idea  · 
  6. 53 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  5 - Nintex Workflow Cloud » Other  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Russ commented  · 

    When you have many workflows running within a single list, it would be useful to be able to either define the Instance Name from the workflow.
    Or have another column the WF could write to, to enable easier identification of a single instance.. Currently you have to open each one OR match the Date Initiated with the create date.

    Being able to add an identifier from the list item (ID, Title etc) would really help,

    Russ supported this idea  · 
  7. 20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Russ supported this idea  · 
  8. 8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Russ supported this idea  · 
  9. 46 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  5 - Nintex Workflow Cloud » Workflow Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Russ supported this idea  · 
  10. 13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    Russ supported this idea  · 
  11. 15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Russ supported this idea  · 
  12. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    Lisa Tam responded

    Hey Elisabeth,

    Have you tried using ‘Wait for percentage of a response’ as a Completion Criteria, setting the Required Percentage as 100%? With this setup, if all users have not selected the required outcome, it will then use the default outcome.

    Russ supported this idea  · 
  13. 98 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Russ commented  · 

    Really need some form of export to PDF (or at least print!)... It's pretty poor to have to screenshot a page at a time..

    Russ supported this idea  · 
  14. 161 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    Russ supported this idea  · 
    An error occurred while saving the comment
    Russ commented  · 

    Related I think..
    If you set a status in the workflow column it also modifies the Item the workflow is running against, thus changing the date modified.
    AND worse still if you wish to state an approval workflow has completed, as the last action, you can't because it resets the approved state to pending!

  15. 31 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  3 - Nintex Workflow for Office 365 » Runtime  ·  Flag idea as inappropriate…  ·  Admin →
    Russ supported this idea  · 
  16. 95 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Russ supported this idea  · 
  17. 201 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Russ supported this idea  · 
  18. 359 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Russ commented  · 

    Why no comments from Nintex on this.. It's been over 2 years now... customers are desperate to have the features that already exist onPrem!

    An error occurred while saving the comment
    Russ commented  · 

    I'm beginning to wonder if this is a deliberate act by Nintex, with workflows under 5 actions being 'free' without inline functions it is virtually impossible to do anything useful... therefore you have to work around the issues with multiple actions...

    An error occurred while saving the comment
    Russ commented  · 

    If I'm reading the very uninformative help correctly, inline functions are only available in forms? Is that correct?
    If so, come on Nintex, you can't expect people to migrate from onPrem with these feature, to Online where the useful/critical bits are missing.

    Russ supported this idea  · 
  19. 334 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Russ commented  · 

    Couldn't agree more with all comments on the performance. So frustrating when coming from the OnPrem Nintex.

    Russ supported this idea  · 
  20. 449 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hi All,

    We’ve just released the ability to capture comments from via LazyApproval, apart from that you can also easily store and retrieve those comments (including ones made via Nintex Forms or directly via the task) into a new task action variable (Task comments).

    For those who are specifically interested in capturing from LazyApproval the way you do is by supplying the outcome separated by a comma and then the comments .e.g. ‘Rejected, Need more detail before can approve’.

    Check it out and let me know what you think…

    Cheers, Rick

    An error occurred while saving the comment
    Russ commented  · 

    We really need a fix on this to bring us back up to the functionality we had OnPremise.

    You've got to wonder whether this is a deliberate ploy to ensure your workflows don't get under the 'free' 5 action limit!!!?

    Russ supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base