Anonymous

My feedback

  1. 18 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  ·  5 - Nintex Workflow Cloud » Workflow Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  2. 55 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  5 - Nintex Workflow Cloud » Form Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 22 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  ·  4 - Nintex Forms for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    There is actually a workaround for this in the short term that I have used recently.
    On your list(s) have essentially a search string column, which combines two fields eg "Truck Ford", which I use a workflow to ensure that field is always correct if the fields change.

    In your form then use a variable to combine the two form control values into the same format and filter by that variables on the search string column, returning anything with "Truck Ford" in that column.

    Not the best solution but it worked in my scenario until we can filter by multiple fields.

  4. 3 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 →
    Anonymous shared this idea  · 
  5. 127 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
    Anonymous commented  · 

    Is this in the schedule to be done yet? It would be a great addition.
    Either this or conditionally hiding pages would solve many use cases.

    Anonymous supported this idea  · 
  6. 20 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 →
    Anonymous supported this idea  · 
  7. 25 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
    Anonymous commented  · 

    Using the tags to create a folder landing page based on those tags would be a great addition to this eg when the workflow page loads you just see tag 1, tag 2, tag 3 etc as folders

  8. 15 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 » Form Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  9. 71 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  ·  4 - Nintex Forms for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  10. 49 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  5 - Nintex Workflow Cloud » Form Designer  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your suggestion, Michael. We are considering this feature.

    As a work around, you can export and import the whole workflow, then remove the actions on the imported workflow (not the original).

    Cheers,
    Euan

    An error occurred while saving the comment
    Anonymous commented  · 

    Have the option to export start/task forms from nwc. If you use cloud to capture form submissions and then SharePoint to display/progress this submission you have to remake the form between platforms.

    Anonymous supported this idea  · 
  11. 364 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  Jon Hardy responded

    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” ?

    Anonymous supported this idea  · 
  14. 286 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →

    Hi All,

    This is currently a SharePoint limitation, however we have made sure that our lazy approval feature only allows people who are assigned a task to specify an outcome.

    As a workaround a user is able to query the task list to see who was assigned the task and who modified the task. We are looking at how make the task querying process easier. Thanks.

    Anonymous supported this idea  · 
  15. 762 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous supported this idea  · 
  16. 11 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 » Form Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  17. 219 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 » Form Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  18. 410 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  Jon Hardy responded

    Without going into the technical detail; the previous value made available in conditional start is actually the current value just before any updates are made to the item. When the item is updated, we lose the ability to get the value prior to the update.

    To restate the workaround as indicated in the idea; create an additional column in the list or library and update this with the current value of the column of interest. Then when the actual column is updated, the previous value is still available in the additional column. Of course one need not make this additional column visible in the view or Form so the users are not confused.

    Anonymous supported this idea  · 
  19. 698 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous supported this idea  · 
  20. 138 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  ·  4 - Nintex Forms for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base