3 - Nintex Workflow for Office 365

Welcome to the feedback forum for Nintex Workflow for Office 365

Please use this forum to submit ideas or feedback on the product.

The Nintex Workflow for Office 365 team

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. In O365 Add Workflow Graphical View(View Flow) in RunTime

    Please add the workflow graphical view in Office365..this must be useful for the enduser...

    756 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  ·  49 comments  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  2. Version Control

    It would be nice to have version control. Its a great feature that is missing from the on-perm world.

    469 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  ·  14 comments  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  3. 'Run Now'

    As Nintex Workflow for 0365 is heavily dependant upon the 'Call HTTP Web Service' action, creating and testing them is particulary time consuming with the feedback cycle, being build workflow, publish, run and then view the history log.

    The 'Run Now' provided within the on-premises solution allows users to call the web service there and then to test the input and output.

    135 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  ·  1 comment  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  4. Calculate Work Days inline

    Either an inline function or action allowing dates to be calculated minus weekends..
    Given that Weekends vary from country to country and some tasks don't require this, it would be great if that within i the task action you could choose and calculate which days should be included.

    127 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  5. 91 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  6. Start Workflow in Item Edit menu

    In NWF 2010+ through Workflow Settings we can show a button to start workflows on the item edit menu. Is this planned? This is a very useful feature for high priority manual workflows.

    88 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
    Open for voting  ·  Jon Hardy responded

    SharePoint online is still not allowing Apps to integrate into this menu. Suggest you configure the start options to start on item creation and start on item update when developing and testing. Then creating or editing the item will kick the workflow off for you.

  7. Component Workflow - Visibility

    As of now, any component workflows created in a Office 365 is visible to all users within the tenant. This will create confusion in scenarios where in the component workflow is required for a specific site collection and not to be visible for others.

    A visibility flag might help a long way to target component workflows for specific site collections rather than entire O365 tenant

    70 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the great suggestion guys, I’ve added this backlog and will keep you updated on a time frame on when we can deliver this feature update. Would love to hear any other thoughts/suggestions on how we can make component workflows even better..?

  8. Create Custom Workflow Actions

    I would really like to be able to create our own custom workflow actions that we could use within our site collection this would make the product much more flexible.

    52 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  9. Runtime Performance Issues

    I am in the middle of developing a workflow, and when the workflow hits an "O365" action, it freezes for several minutes. HUGE performance issue!!

    31 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  10. Daylight Saving Time Support

    Currently our Site workflows have been firing an hour early due to Daylight Saving Time ending for this year. This is apparently not a bug for some reason, and should be considered such.

    31 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  11. Document generation ability to generate table element from rich text fields

    Currently if the rich text has a table element, the table has not rendered as it is on the result of Nintex document generation action

    31 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  12. The Publishing Date fields are displaying the time from an incorrect time zone

    Currently, Nintex for O-365 workflows are not able to parse the Date and Time from the following publishing fields - Scheduling Start Date/End Date. Any workflow email that includes these fields shall display incorrect time (due to time-zone difference between the Nintex App and the Site-Collection). We would need this to be corrected, as all the site-collections will not be in the same time-zone where the Nintex Apps are hosted.

    26 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow reordering variables on the workflow start form.

    Currently, workflow variables are displayed in the order they are created, which is inflexible.

    23 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  14. Approve/Reject buttons from email on mobile devices

    I added a comment to this idea: https://nintex.uservoice.com/forums/218291-3-nintex-workflow-for-office-365/suggestions/5740552-email-notifications-having-approve-reject-bu, but not sure if the comments are being monitored since it is marked as completed.

    Based on my clients' feedback, the greatest need for button approval via email is from mobile devices. When I access the LazyApproval email from my iPhone, the actionable buttons are not there.

    Side note: The actionable message buttons are available via my iPhone for Flow tasks.

    17 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  15. Enhance Start Workflow action to handle running instances

    The behaviour of the Start Workflow action is to suspend the originating workflow if an instance of the called workflow already exists for the list item.

    Proposed is an enhancement to either:
    1. allow the Start Workflow action to be configured such that the originating workflow is allowed to continue
    or
    2. introduce a 'Check Workflow' action that returns a value to indicate if if an instance of a workflow exists for a list item

    16 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  16. 14 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  17. Office 365 upload file error handling

    WHen you use Office 365 upload file, if the site does not exist the workflow gets suspended. Testing for the site and library existence is not trivil. Please add some error handling to this action so that it returns No if the site does not exist, or Nintex does not have access, rather than suspending the workflow.

    15 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  18. Skip action on error

    Allow the option to skip an action if an error occurs while performing it. For example, if a user-defined emailed address is undeliverable for sending a notification, then allow the workflow to continue.

    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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  19. Enable fully transparant Do-Until (polling) functionality in all Nintex call web service actions

    Since we sometimes can not rely fully on the Microsoft REST service endpoints (for example for SharePoint Online) especially when looping those calls in a workflow, it would be very nice if Nintex Workflow added some automatic polling (Do-Until) to retry web services calls if they fail with some sort of 500 error. The same functionality I was aiming for will be introduced into Azure Logic Apps as can be viewed here: https://www.youtube.com/watch?v=J7PyjKkkNu0. This should enhance the stability of our Workflow solutions

    9 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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
  20. LazyApproval Out Of Office Support

    Currently an out of office email causes LazyApproval within O365 to send a second email saying that the response was not valid. LazyApproval should know that it's an out of office email like the system does on-prem.

    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  ·  Runtime  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

3 - Nintex Workflow for Office 365

Categories

Feedback and Knowledge Base