Stefanie Sloper

My feedback

  1. 264 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    This feature is now available from the latest versions outline below

    Nintex Workflow for SharePoint 2013 v3.5.2.0
    Nintex for SharePoint 2016 v4.5.2.0
    Nintex for SharePoint 2019 v5.1.2.0

    Stefanie Sloper supported this idea  · 
  2. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stefanie Sloper supported this idea  · 
  3. 16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3 - Nintex Workflow for Office 365 » Runtime  ·  Flag idea as inappropriate…  ·  Admin →
    Stefanie Sloper supported this idea  · 
  4. 476 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jon Hardy responded

    The task ID is populated once the task is completed. Before this the task list items can be locked by the task engine for processing and a workflow accessing this task may fail. There has been therefore a strong reservation form our Engineering group to implement this capability even if technically feasible.

    If one wishes to delegate the task then the delegation should be used.

    Should you have other use cases for accessing the task list before the task is completed then please let us know what they are. There may be an alternative way of meeting this need that will not introduce the possibility of workflow failure.

    Stefanie Sloper supported this idea  · 
  5. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    Stefanie Sloper shared this idea  · 
  6. 600 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hey all,
    There looks to be 2 requests here
    - Update Inline function to allow calculate date difference, factoring in only business days / hours
    - Update Calculate date action to factor in only business days / hours
    Can you please share which of the two you require and your use cases
    Thanks
    Lisa

    Stefanie Sloper supported this idea  · 
  7. 60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Stefanie Sloper commented  · 

    Just had to implement a nasty polling loop to workaround this. Please add :-)

    Stefanie Sloper supported this idea  · 
  8. 446 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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
    Stefanie Sloper commented  · 

    This is the top item on UserVoice. Nintex are you listening? :)

    An error occurred while saving the comment
    Stefanie Sloper commented  · 

    This is essential e.g. for LazyApproval, we don't get the comments!

    Stefanie Sloper supported this idea  · 
  9. 377 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Stefanie Sloper supported this idea  · 
  10. 641 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    41 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Stefanie Sloper supported this idea  · 
  11. 428 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stefanie Sloper supported this idea  · 
  12. 78 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stefanie Sloper supported this idea  · 
  13. 24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    Stefanie Sloper supported this idea  · 
  14. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Stefanie Sloper supported this idea  · 
  15. 209 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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” ?

    Stefanie Sloper supported this idea  · 
  16. 680 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stefanie Sloper supported this idea  · 
  17. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Stefanie Sloper commented  · 

    We also need to use caps in task outcomes. it seems like more effort to have changed these to lower case, is there a reason behind this?

    Stefanie Sloper supported this idea  · 
  18. 27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Stefanie Sloper shared this idea  · 
  19. 15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Stefanie Sloper shared this idea  · 
  20. 162 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Stefanie Sloper shared this idea  · 
← Previous 1

Feedback and Knowledge Base