John Troup

My feedback

  1. 22 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 →
    John Troup commented  · 

    BUMP!

    John Troup supported this idea  · 
  2. 4 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 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    John Troup shared this idea  · 
  3. 54 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  2 - Nintex Forms for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your suggestion Cassy. With Universal Forms, you will be able to set the value of any control. I just tested setting the People Picker control in a test environment.

    Would the person be hardcoded in the rule? Or would you expect a UserProfileLookup runtime function output to populate the field? Let me know in the comments below.

    Cheers,
    Euan

    John Troup supported this idea  · 
  4. 314 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  2 - Nintex Forms for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →

    Hi all,

    Drag and drop has been included into Universal Forms in our current build. We have no plans to bring this current functionality to Classic Forms.

    Once we have shipped Universal Forms for SharePoint, we will close this feature request.

    Cheers,
    Euan

    John Troup supported this idea  · 
  5. 303 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    John Troup supported this idea  · 
  6. 38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    John Troup supported this idea  · 
  7. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  2 - Nintex Forms for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    John Troup supported this idea  · 
  8. 473 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.

    John Troup supported this idea  · 
  9. 158 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 →
    John Troup supported this idea  · 
  10. 20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  1 - Nintex Workflow for SharePoint » Web Parts  ·  Flag idea as inappropriate…  ·  Admin →
    John Troup commented  · 

    Bump

    John Troup supported this idea  · 
  11. 13 votes
    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 →
    John Troup supported this idea  · 
  12. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    John Troup commented  · 

    We created an audit log field and had the workflow update that field with each action taken.

  13. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    John Troup supported this idea  · 
  14. 28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  2 - Nintex Forms for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your suggestion Ryan. I can tell you that the new Responsive Designer will look very different to classic when Universal Forms will be released as its a new engine.

    Once we release Universal Forms for SharePoint, we will revisit our strategy around Classic Forms.

    Cheers,
    Euan

    John Troup supported this idea  · 
  15. 161 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  4 - Nintex Forms for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    John Troup supported this idea  · 
  16. 35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your suggestion Brent. As we will need to rebuild the Managed Metadata control for Universal Forms for Office 365, I have added this feedback into the backlog.

    When we begin development on this feature, I will update this feature with any updates I have.

    Cheers,
    Euan

    John Troup supported this idea  · 
  17. 383 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  4 - Nintex Forms for Office 365 » Other  ·  Flag idea as inappropriate…  ·  Admin →

    This feature is still in the backlog. We are focused on Universal Forms for Office 365 at the moment.

    Once we ship Universal Forms for Office 365 and SharePoint, we will review our offering of Live Forms.

    I will update this feature once we ship Universal Forms.

    Cheers,
    Euan

    John Troup supported this idea  · 
  18. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  4 - Nintex Forms for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    John Troup supported this idea  · 
  19. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    John Troup supported this idea  · 
  20. 91 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  4 - Nintex Forms for Office 365  ·  Flag idea as inappropriate…  ·  Admin →

    We have discussed the idea of converting from Classic to Responsive but due to the big change in structure, we are not sure it would give a great experience.

    As an example, a form of 1000px in a 10×10 grid would be a 100 column grid. Converting this from Classic to a Responsive 4 column grid would not look great. The best we could do is just list every control stacked under each other. If you think this would still be useful, please leave a comment below.

    John Troup commented  · 

    Need this big time. Can't use responsive forms otherwise.

    John Troup supported this idea  · 
← Previous 1

Feedback and Knowledge Base