Barry

My feedback

  1. 200 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  ·  10 comments  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    Barry supported this idea  · 
  2. 47 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  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    Barry supported this idea  · 
  3. 24 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  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    Barry supported this idea  · 
  4. 74 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  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    Barry supported this idea  · 
  5. 201 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  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    Barry supported this idea  · 
  6. 81 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Under Review  ·  6 comments  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    Barry supported this idea  · 
  7. 12 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  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Barry commented  · 

    A great example of this is selecting to sort tasks by 'Task Name'. This groups tasks by the first letter of their title, however, within their groups they remain ordered by, presumably, Created Date. Consider the scenario when many tasks have been generated to cover a days work. I'm directing a user to walk up an aisle and check stock in sequential bays e.g. Bay01, Bay 02, Bay 03...

    At present if they check their iPad for 'Check Stock' tasks under the C grouping they might see:

    Check Stock - Bay03
    Check Stock - Bay05
    Check Stock - Bay02
    Check Stock - Bay04
    Check Stock - Bay01

    What they expected to see was:

    Check Stock - Bay01
    Check Stock - Bay02
    Check Stock - Bay03
    Check Stock - Bay04
    Check Stock - Bay05

    Multiply this issue when there are 100 bays and you see the issue.

    While we have suggest using search to locate the task for the next bay, which may or may not exist, it's clunky and users don't like it. From the user point of view, the sort by 'Task Name' is broken.

    Barry supported this idea  · 
  8. 5 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
    Barry commented  · 

    I think I have a similar idea. Essentially, that the version number of the running workflow should be available as a common property such that it could be included in the details of things like tasks and email notifications e.g. in the footer of a notification.

    This would be really useful to in situations where workflows might run for a long time and a user might receive a task or notification that appears to contain a bug or old information for something which has been marked as fixed or updated. It would be good to be able to say easily that, for example, your notification was generated by a workflow which is still running under v6.0 and the issue you report was fixed in v7.0.

    I don't believe there is any webservice call we can make to get this info but happy to be corrected.

    Barry supported this idea  · 
  9. 92 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  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    Barry supported this idea  · 
  10. 12 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  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    Barry shared this idea  · 

Feedback and Knowledge Base