Arne

My feedback

  1. 365 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    Arne supported this idea  · 
  2. 25 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  ·  5 - Nintex Workflow Cloud » Connectors  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Arne,

    Apologies in the delay in responding to you, and thanks again for submitting your requests!

    This scenario makes sense – I’ll add this into our backlog for review and prioritisation. I will endeavour to keep this ticket updated with any progress.

    Regards,
    Kate

    Arne shared this idea  · 
  3. 314 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Planned  ·  Euan Gamble responded

    This feature has been included into Universal Forms for SharePoint and Office 365.

    Once we have shipped Universal Forms for SharePoint, I will update this feature.

    Arne supported this idea  · 
  4. 145 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 Vadim. As we are currently building Universal Forms for Office 365, SharePoint and Nintex Workflow Cloud, we are considering how we move forward with Live Forms with all the Nintex Infrastructure.

    We currently support Google reCaptcha in Nintex Forms for Nintex Workflow Cloud which may suit your needs as the platform supports anonymous forms and pushing data to different systems.

    Cheers,
    Euan

    Arne supported this idea  · 
  5. 152 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Arne supported this idea  · 
  6. 8 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  ·  3 comments  ·  5 - Nintex Workflow Cloud » Runtime  ·  Flag idea as inappropriate…  ·  Admin →
    Arne supported this idea  · 
  7. 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.

    Arne supported this idea  · 
  8. 698 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Arne 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.

    Arne supported this idea  · 
  10. 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.

    Arne supported this idea  · 
  11. 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

    Arne supported this idea  · 

Feedback and Knowledge Base