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

How can we improve Nintex Workflow for Office 365?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Office 365 update item permissions: Azure IP restrictions

    We have conditional access restrictions in place for our O365 tenants which is preventing us to use some of the Nintex O365 workflow actions. In particular authentication for internal users is only allowed from an approved range of IP addresses. Any workflow action using the "Site and user administration" connection are failing to run as authentication is failing.
    Proposed workarounds from Nintex were to whitelist whole Azure IP restrictions or to use a service account that would have access to all of the sites. Both solutions are considered highly risky for our organization.
    Requesting solution from Nintex to build a…

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. API for creating/updating workflow schedules

    It would be great if the api for creating/updating site workflows would also allow us to create/update workflow schedules.

    https://help.nintex.com/en-US/sdks/sdko365/

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Central Place to terminate Suspended workflows either at list or site level

    Can we get a central place within nintex online to terminate or retry suspended workflows?
    Use case: we have a list, managed by users, that syncs specific info from one list to another. The source list had a choice column change and thus has started suspending wf's because users did not make sure destination choice column contained the same values. Now we have 200+ suspended workflows in the source list. Due to the nature of a suspended wf, we cannot just kick off a new on those items, even after the issue with the choice values are fixed between the…

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Store / Actions  ·  Flag idea as inappropriate…  ·  Admin →
  4. Lazy Approval - Ability to somehow know WHO APPROVED IT!

    The lazy approval is a nice thing to have, but how can I let users have this feature when there is no way of knowing WHO THE APPROVER WAS??? When the auditors look to see who approved access to a system, they do not want to see "Approved by SharePoint App"....they want to see an individual's name.

    84 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Term Store synonyms and Abbrebiations

    Term Store Synonym

    Please allow users to select synonyms and abbreviations for this term Store. VIP - I have a list of schools from which users should select. Users should not be required to always enter the legal school name in the default label. Our users are forced to use only the Default Label. Please fix this ASAP. This is crucial for an application we are about to take live in a few weeks.

    Thanks
    Carol

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Microsoft Edge Browser Support

    Microsoft no longer supports the use of IE11 for Office 365 applications but Nintex does not support Microsoft Edge. We have to browser jump between IE11 and Edge to get our work done.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Slow Environment

    Working in the O365 version is excruciating. Forms are bad enough, however workflows are extremely slow. Opening/closing/saving actions, saving/publishing any size workflow takes a ridiculous amount of time. We are migrating approx. 80 workflows. This will take a year at the speed this system works. And that's not counting all the new forms we are constantly building. Can the performance of the O365 environment please be improved.

    275 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Nintex Governance: Connection Manager & Workflow publishers

    Best practice around Connection manager would be: Create tenant level connections with appropriate set of users who will design workflows. To ensure local site admins don't create unnecessary connections we need a central setting to disable site level shared connections and personal connections.

    Workflow publishers: We need to add/remove each user to the list of allowed workflow publishers. There is no way to use AD groups. It'll be great if Nintex can enable AD groups in workflow publisher settings.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  9. Termination of Component Workflow

    Today if a main workflow invokes a component workflow and the component workflow is terminated for some reason, then the component workflow does not return any status back to the calling workflow and the parent workflow keeps waiting forever. This is the case if the setting on the "Invoke Component Workflow" action is set to wait for component workflow to complete and wait for the outcome

    There should be a way for the component workflow to return back the status in case it is terminated

    65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Sridhar,

    The issue we currently have is the workflow engine does not send us any kind of event to indicate that the component workflow (or any workflow) has suspended meaning we can’t send any notification back to the parent workflow. We are currently talking with Microsoft to see if they can provide us the info we need, will update you once we know more..

    Cheers, Rick

  10. Create site collection using modern template

    Currently the Office 365 Create Site Collection is not supporting the modern view template such as the communication/topic template.
    It will be great if this can be supported as well.

    ref:_00D90q6Cb._5002v2I76sv:ref

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Print / PDF of Workflow

    For documentation, we would love a button to print the workflow, with the option to show the configurations for each action or not.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    63 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    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..?

  13. Direct / more "intuitive" way to configure typical reminder settings for tasks

    I repeatedly see the requirement that a Task is assigned to a user and there should be an E-Mail reminder to the assignee every x days - starting y days after the Task has been assigned.

    Today (please correct me if I overlook something obvious here…) the in my eyes rather bothersome way of configuring this would be
    - create a separate Workflow variable V
    - Use a separate "Calculate Date" Action to add y days to today's date and store this value in V
    - in the Configuration Settings for the Task Action, use V as the "Due Date" …

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support for operators in *Wait for field change in current item* action

    *Wait for item update* action in Nintex on-prem enables developer to use different operator based on need. Please enable operators in Nintex online action *Wait for field change in current item action*

    e.g. Status != Submitted

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Store / Actions  ·  Flag idea as inappropriate…  ·  Admin →
  15. Enable Date formatting functions

    Date format is one of the common use-case in Nintex workflows. It'll be great if Nintex can build this feature.

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Store / Actions  ·  Flag idea as inappropriate…  ·  Admin →
  16. Unable to import same Workflow settings on "Set Workflow Variable" configured with "List Lookup" on a different site collection.

    Unable to import same Workflow settings on "Set Workflow Variable" configured with "List Lookup" on a different site collection. As compares if we use "Update List Item" Workflow action configured with "List Lookup" the settings are imported with no problem.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Store / Actions  ·  Flag idea as inappropriate…  ·  Admin →
  17. Provide examples

    I wish you would provide examples of how to use Nintex functions. I am a visual learner and need to see examples of how something works. Your site is totally useless to me. For example, I want to see how the Switch function is used in a workflow. Your site does a horrible job of explaining how to use it. Nothing on our version matches what is out there in the community either, it is all outdated. Very frustrating

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Store / Actions  ·  Flag idea as inappropriate…  ·  Admin →
  18. Export action set

    The ability to export action sets and import them into other workflows would be a great piece of functionality for us to have!

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Store / Actions  ·  Flag idea as inappropriate…  ·  Admin →
  19. Personal connections in Connection Manager

    From the governance perspective, personal connections should be disabled by default. Currently it must be manually disabled on each site/sub-site.

    Recommended path:
    1. Personal connections must be disabled by default
    2. Need basis site owners may decide to enable it
    3. This would encourage the use of *shared connections*

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Designer  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add ServiceNow connector

    It would be great to have a serviceNow connector added as an action which allow you to add, update, delete and retrieve Servicenow data. This is already available in NWC but not yet in Nintex O365 Workflow

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Store / Actions  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 23 24
  • Don't see your idea?

3 - Nintex Workflow for Office 365

Feedback and Knowledge Base