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
-
Support Signed card payloads for Actionable Message
In some scenarios, an Actionable message is not working using Nintex Workflow.
Microsoft has suggested for Nintex to implementing signed cards which work in all cases and are fundamentally more secure since they do not rely on DNS records.At this stage signed cards are currently not supported
1 voteActionable Messages has been updated to use Adaptive Card with signed card payload.
-
Ability to add task outcome in UPPERCASE via task process action
Can we have the option to be able to add task outcomes either in UPPERCASE or LOWERCASE and not default to the first letter being in uppercase and the rest reverting to lowercase?
Consider the below steps:
Navigate to workflow designer
Add a "Task Process" action to the canvas
Double-click the Task Process action to configure it.
You will notice that under the Task outcomes section, there are two outcomes: Approve and Reject.
Rename the task outcome "Approve" to APPROVE.
Click away from the text box and you will notice that it has changed back to "Approve"
Same behaviour occurs…
7 votesThis change has been released. You can now set your task outcome as all upper case.
-
Permissions to Nintex Apps (Forms and/or Workflows)
Currently anyone with full control to a list or library can access the Nintex forms and workflows. We want our business users to have full access to lists and libraries, but do not want them modifying workflows as they are business critical. Governance around Full Control site owners is difficult to implement in our organization (10,000+ employees), we need only the development team to have access to Nintex in O365. In SharePoint 2013 on-premises, I would go to Site Settings -> Nintex -> Allowed Workflow Designers -> Remove permissions except for the development team. We need this same access control…
40 votesToday we released the new Nintex Admin and Governance features in Office 365.
With this release Nintex admins can now restrict users who can publish workflow (they can still save) plus the ability to create a tenant wide connections.
-
Capital letters in task outcome
It's not possible to add capital letters in the task outcome of nintex workflow o365 task actions.
7 votesThis update has been released.
-
Create team on Microsoft Teams action
Create team on Microsoft Teams action is demanded by Teams users for managing teams.
27 votesTeams actions for O365 have now been released.
-
Show or Hide Allowed Actions
In the current On-Prem I can Show/Hide actions for the users using a AD Group. This way we are able to control what the developer sees. Based on our maturity we show/hide actions. Such a feature is not available in O365 and this is very crucial for us to implement the governance in O365.
85 votesHappy to announce we’ve just released the action availability capability for Office 365.
-
Edit Action Description within Action configuration
When adding an action it would be excellent to be able to also edit the Title/Description. Often you can add a number of similar actions like Set Field etc so I find I often need to view the configuration then leave to edit action description.
3 votes -
Store task ID for Start a task process action
The "Start a task process" action does not allow the ability to store the task ID in a variable. It would be very handy to allow this, and in the event that multiple tasks are created for the process, store them in a collection.
36 votes -
161 votes
We have released the first phase of CC/BCC support for the the Initial task emails. For more details, visit our blog https://community.nintex.com/t5/Community-Blogs/Task-attachments-and-CC-BCC-Workflow-for-Office-365/ba-p/112529
For next phase, we will look to include CC/BCC for Reminder and Escalation emails.
-
Workflow Errors
There needs to be some notifcation to the designer or somoene if the workflow errors. When you have multiple workflows across multiple sites a notifcation is helpful in managing your workflows and any issues. This was available in on-prem why has it gone away?
641 votesI’m happy to say this feature has now been released, for more detail on how it works check out the blog – https://community.nintex.com/t5/Community-Blogs/Introducing-Workflow-failure-notifications-for-Office-365/ba-p/107432
-
MS Dynamics CRM 2016 Integration
We recently upgrade to Nintex Workflow Enterprise but were disappointed to find the CRM Actions are not yet compatible with MS Dynamics CRM 2016. We wanted to use this as part of a SharePoint Nintex Form and Workflow but are told this action is not available for CRM 2016. This needs to be release as soon as possible.
1 vote -
Allow images in Document Generation
The Document Generation actions should allow images to be dynamically added to the document.
On Premise has that so by right Document Generation for O365 should already have it.
3 votesOffice 365 was updated last week to have the same functionality as on-prem including support for images.
-
Ability to include attachments for Task Emails
Need to have the option to include attachments for email notifications that are sent from the task actions.
252 votesWe have released the first phase of task attachments. You can now add attachments to the Initial task emails. For more details, visit our community blog https://community.nintex.com/t5/Community-Blogs/Task-attachments-and-CC-BCC-Workflow-for-Office-365/ba-p/112529
In the next phase, we will add an option to include attachments for Reminder and Escalation emails.
-
Allow Person variable to not be an initiation variable
When creating a Person or Group variable, the creation of the var forces it to be on the initiation form. For workflows that only operate as Manual Start, I have to instruct users to ignore the prompt for the person value, and also add a description in the initiation options that says "Please Ignore, do not provide a value". This is confusing to users, is there a way we can remove the force display on the initiation screen?
55 votes -
multiple workflow variables in one set variable action
Why can't we set multiple variables in one set variable action item like in the list item update.
example: I want to generate document with the data in the current list item. For that purpose i have to create a workflow variables for each column in the list. so I have to create n number of workflow variables for n columns list. Also i have to create n set variable action in the workflow.
Also Can you please consider current list item values as well along with the workflow variable values in the document generation. Which is the ideal scenario…
1 voteHi Prasanth, You may of seen this already however the set workflow variable action now supports multiple variables in the one action, you can add up to 20 variables in a single action.
As for you requirement regarding document generation – the upgraded action which is due in a couple of months will support Item and Workflow properties meaning you don’t need to create variables for all your tags, they will all just appear in the tagger making it much easier..
-
document generation insert picture in word from current item attachment
for example you make an inspection report and want to insert the attached photo in the word template
9 votesWe now support insertion of images however if you want to get attachments you will need to get them via the lists.asxm web service to get the url of the image, once you have the url you can assign to a variable and use in the action config.
-
document generation output for send email with attachment
the generated document must have a item id output or any reference for use in send email with attachment
3 votesThe document generation action now supports outputting the document as a list attachment, you can then use the include list item attachment feature in send notification to automatically include the documents as attachments.
-
Implement SharePoint 2016 Redesigned Toolbox
The new version of Nintex for SharePoint 2016 looks really nice, can we please get that design skin applied to the Office 365 Version!!!
3 votesUpdated icons in the toolbox and designer ribbons have been updated with the same style as NW2016
-
Allow disable of action
I have actions in o365 that I would like to disable, but not delete. In on-prem, one could disable an action for debugging purposes. In o365, the only option is to delete it. If I have several nested actions, it becomes cumbersome to have to recreate the action. As of now, I have to go back and forth between exporting and importing versions. Not cool!
17 votes -
Edit Task URL property
A very common request from customer is the possibility to link an assigned task directly to the edit form, currently the URL property refers to the DispForm of the item, could it be useful to have also a property that link the default Edit form.
20 votesIn our last release we introduced a new setting for both Assign a Task and Start a Task Process called ‘Open task form in the selected mode’ allowing you to define how the task form will open, either Edit (default) or View Mode. One thing to note is that this behaviour only works from the link it the notification email and not when you open the task directly from the list.
- Don't see your idea?