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
-
DocuSign Single Sign-On Integration
DocuSign actions should include support for Single Sign-On between DocuSign and Office 365. Currently, to authenticate a DocuSign user that utilizes Single Sign-On they must be added to an exceptions list, and it is unrealistic to add all users to the exceptions list as this defeats the purpose of using Single Sign-On.
81 votes -
Update Item Permissions For External User
Currently the Update Item Permissions action does not support modifying permissions on external users (reason here:https://community.nintex.com/thread/12513). It would be great if this action could be updated to support external users, or if another action could be developed specifically to interaction with externals users who have been added to the SharePoint site.
57 votes -
Office 365 XML Decode function
In Nintex on-prem there is a function to decode XML values, so that special characters are no longer encoded, but shown as correct (eg. é, è, à,...).
In Office 365 this is not available, but you have to convert each value via a replace action (for each known special character). Is it possible to have an action which can decode the XML an easier way?13 votes -
docusign download all documents in the envelope
Allow the DocuSign Action "download document" to download all of the documents associated with the envelope. The difference would be to append Combined to the REST call that is already being sent. It would be and easy fix.
https://docs.docusign.com/esign/restapi/Envelopes/EnvelopeDocuments/get/Example: GET /restapi/v2/accounts/1703061/envelopes/44efc9e6-915e-4b1d-9b54-801410d6922d/documents/combined
6 votes -
Global task delegation
We moved from SP2010 to SPO and we need global task delegation back. When one of our employees goes on vacation, they need the option to delegate ALL nintex tasks to another user for a set date range. This "upgrade" to SPO and Nintex Online has been a nightmare for end users. Missing way too many important features.
49 votes -
Start Parameters for Start Workflow action
Would be great to have the ability to pass the Start Workflow action values as start parameters.
54 votes -
Set Workflow Variable for Lookup List in another site
Set workflow variable to able to set variable from the list lookup in another site.
9 votes -
Multi-factor authentication support for live actions.
Currently, none of the Nintex live actions support any multi-factor authentication. More and more clients are switching to this level of security and the lack of this support greatly inhibits our feature offerings. None of the live action advantages are available and clients can't switch to multi-factor authentication without breaking workflows that utilize these features.
57 votesWith the work on a “Connection manager” MFA will be supported for those live actions that support OAuth authentication. Unfortunately not all actions do, and so there are exceptions. When connection manager is released the help will detail which will.
For the balance, the comment by Mike Oryszak below is an option for these actions.
-
Update Date/Time Column To Blank
The Update Item or Office 365 Update Item action should be able to set a Date/Time column back to a blank value, which is currently not possible.
28 votes -
Really need a replacement for PadLeft.
If InLine functions are not being replaced in 0365 (which I really hope they are), how about more actions to help with common functions like padding out variable for use in Document title etc..
20 votes -
Workflow Actions for Site Collection Administration
Would be great to have more workflow actions for site collection administration. Thinking about actions like "Set site collection administrator" or "Set sharing capabilities"
4 votes -
Favorite Actions
Create a tab that lists favorite actions. This would allow to easily access actions that you use a lot (like log history), instead of having to scroll through all those tabs.
7 votesThank you for your suggestion. In the mean time try typing in one of the words of the action name in the search it will appear in the toolbox e.g. log for log to history. This will also avoid the need to scroll through tabs.
-
Task email to send to Mailbox
It would be very handy to include the ability to send a Task email to a mailbox. I understand that a task needs to be assigned to users, but the ability to send the task email to an email address and not to assignee's would cut down on email clutter when a task is assigned to a group of users but only needs to be completed by one user.
20 votes -
Office 365 groups actions
Create an action that automates the provisioning of Office 365 groups.
16 votes -
Need cross site workflow/actions
I think it's extremely important that Nintex Workflows can perform cross site actions such as updating items in another site using the standard actions. Nintex Workflow, being the leading SharePoint workflow add-on, really should provide this no-braining functionality. Thank you.
10 votes -
Document content as Base64
Hello,
Is there any chance to prepare something like [FileData] from on-prem version?
I would like to use document content as Base64 in Nintex Workflow for O365 but without success right now.Thank you
35 votes -
17 votes
-
Copy File to Fileshare
Should be able to copy a SharePoint file to a network fileshare location.
16 votes -
Target only the current item when using Office 365 Update Item Permissions
It would be great to add simply "current Item" to the "Items to update" scope for the Office 365 Update Item Permissions online workflow action.
This would greatly simplify the action and make it clear that the item permissions being affected are only the item permissions that correspond to the item the workflow is currently running against.
8 votes -
Ability to store binary data in variables and pass them in Web Request action
Currently when trying to put binary data (ex. retrieved using SharePoint API binary data of the file from library) in a text variable or to use directly in "Web Request" action some information is lost (I suppose Nintex is not supporting null bits [0x00] and replaces them with spaces [0x20] or cuts them off). Because of that, when trying to create a new file in a different library or when trying to call Nintex O365 REST API to create a workflow, the results are incorrect - the created file is corrupted and API returns errors.
It would be really nice…
29 votes
- Don't see your idea?