Christian Heindel

My feedback

  1. 58 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christian Heindel supported this idea  · 
  2. 92 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christian Heindel supported this idea  · 
  3. 264 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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

    Christian Heindel shared this idea  · 
  4. 48 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christian Heindel supported this idea  · 
  5. 9 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  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    Christian Heindel shared this idea  · 
  6. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christian Heindel supported this idea  · 
  7. 83 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christian Heindel supported this idea  · 
  8. 22 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  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Alex responded

    Thanks for the feedback. We are currently looking at investments around governance for a future release where this would be a great fit.

    Christian Heindel supported this idea  · 
  9. 38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christian Heindel supported this idea  · 
  10. 8 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  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    Christian Heindel shared this idea  · 
  11. 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.

    Christian Heindel supported this idea  · 
  12. 476 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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.

    Christian Heindel supported this idea  · 
  13. 150 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  2 - Nintex Forms for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    Christian Heindel supported this idea  · 
  14. 72 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christian Heindel supported this idea  · 
  15. 128 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christian Heindel supported this idea  · 
  16. 32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    Christian Heindel supported this idea  · 
  17. 37 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  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    Christian Heindel supported this idea  · 
  18. 281 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    Christian Heindel supported this idea  · 
  19. 146 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Christian Heindel supported this idea  · 
  20. 302 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  ·  2 - Nintex Forms for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →

    Hi all,

    With the development of Universal Forms, we are looking at how the current form modes are supported in the existing product.

    At this time we are still planning to continue using functions to detect form modes. This is so we are able to support migrations but also give a lot of flexibility in the rules engine.

    We do not plan to bring different layouts to Universal Forms at this time. As we are introducing multipage to Universal Forms, we do need to figure out how a multipage form will be printed and is under consideration.

    I will update this feature when we release an Advance Preview of Universal Forms if our position changes based on feedback.

    Cheers,
    Euan

    An error occurred while saving the comment
    Christian Heindel commented  · 

    Also, customer that are "converting" from InfoPath are simply used to this functionality and missing it... ;-)

    An error occurred while saving the comment
    Christian Heindel commented  · 

    Hello Daniel.

    Some examples: The "New" and "Edit" forms sometimes differ when our customers want to enable fast and simple input in a first step and more information in a second editing step.

    While we can use rules and JavaScript to enable such behaviour, it makes using the form editor difficult and the form gets harder to overlook / understand. In the "View" mode, we often want to enable a more compact view, which results in the same problems.

    I think it is only very little additional work and that it is worth it, because you would get a better maintainability of the form.

    Christian Heindel shared this idea  · 
← Previous 1

Feedback and Knowledge Base