Anonymous

My feedback

  1. 182 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  · 
  2. 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  · 
  3. 674 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  ·  Lisa Tam responded

    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

    Anonymous supported this idea  · 
  4. 84 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  · 
  5. 32 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  · 
  6. 136 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  · 
  7. 241 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 comments  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  8. 252 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We are currently at the early stages of evaluating the whole topic of workflow documentation.

    Anonymous supported this idea  · 
  10. 68 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  · 
  11. 74 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  ·  2 - Nintex Forms for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Under Review  ·  Euan Gamble responded

    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

    Anonymous supported this idea  · 
  12. 67 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  ·  2 - Nintex Forms for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Under Review  ·  Euan Gamble responded

    As we are currently focused on Universal Forms, this is not on the short to medium term.

    Once we have shipped Universal Forms for SharePoint, we will revisit Classic Forms.

    Cheers,
    Euan

    Anonymous supported this idea  · 
  13. 154 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  ·  2 - Nintex Forms for SharePoint » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Open for voting  ·  Euan Gamble responded

    Thanks for your suggestion Francois.

    Nintex Forms is mainly focused on the List content type and all derivatives. The Survey content type is a little bit different due to the Rating Scale which we currently do not have.

    We may consider it in the future, but at the moment we are focused on Universal Forms release.

    I will update this idea if we change our position on this idea.

    Cheers,
    Euan

    Anonymous supported this idea  · 
  14. 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 →
    Under Review  ·  Euan Gamble responded

    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

    Anonymous supported this idea  · 
  15. 29 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  ·  Euan Gamble responded

    Thanks for your suggestion.

    I will update this idea if there are any updates to share.

    Cheers,
    Euan

    An error occurred while saving the comment
    Anonymous commented  · 

    I would like it to have 1 minute intervals instead of 5.

    Anonymous supported this idea  · 
  16. 245 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  · 

    agreed! we really need this so we can archive changes made to legal documents.

  17. 105 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  2 - Nintex Forms for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    It would be great if I could get my 4 attachments per item on my "employee info list" to display on a Nintex form in the form of an image! I need to display their PI, Photo,

    Anonymous supported this idea  · 

Feedback and Knowledge Base