Anonymous

My feedback

  1. 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  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  2. 286 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →

    Hi All,

    This is currently a SharePoint limitation, however we have made sure that our lazy approval feature only allows people who are assigned a task to specify an outcome.

    As a workaround a user is able to query the task list to see who was assigned the task and who modified the task. We are looking at how make the task querying process easier. Thanks.

    Anonymous supported this idea  · 
  3. 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  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  4. 76 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  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    Strongly supported.

    Anonymous supported this idea  · 
  5. 20 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  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  6. 50 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  · 

    Yes, this would really be a very handy Feature, in particular during development / Debugging of a workflow.

    Anonymous supported this idea  · 
  7. 10 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  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  8. 10 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  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    As a matter of fact, this "idea" does not apply to the Update Field activity, but to each and every activity which has an "Advanced Lookup" functionality anywhere in its configuration window. It is really bothersome and error-prone that the workflow designer has to enter the desired Option as a free-text Attribute.

    An error occurred while saving the comment
    Anonymous commented  · 

    This is really puzzling me as well. This was working in On-Prem and I would also expect that I could use the Update Field activity to update a "Choice" column in a way that I am presented a drop down with all valid values.

    Anonymous supported this idea  · 
  9. 10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous shared this idea  · 
  10. 1 vote
    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 →
    Anonymous shared this idea  · 
  11. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous shared this idea  · 
  12. 26 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  ·  9 comments  ·  6 - Nintex Mobile/App Studio  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    The latest release of Office Lens included OCR capturing, for example for Business Cards. It would be great if I could use the result of the OCR from Office Lens to fill forms via Nintex Mobile.

  13. 16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Supported. As a matter of fact, I actually think it should be the default behavior to automatically terminate all running instances of (previous version of) the workflow as soon as a new instance of the same workflow is started. Example (from real-world customer project): There is an approval workflow which is still pending. In the meantime, the document itself (and the workflow) is changed. The user starts a new instance of the approval workflow for the revised Version of the document. In this case the pending approval workflow should be terminated automatically.

    Anonymous supported this idea  · 
  14. 96 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  · 

Feedback and Knowledge Base