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
-
Use a reference for Site Language and Template within "Create site in o365" action
Currently the Site Language and template need to be defined when configuring the action.
Please add an option to define this by a reference/variable, so that this can be configured depending on the workflow logic.
4 votes -
Create Groups within "Office 365 Create Site in o365" action
When creating a site using the "Office 365 Create Site in o365" action, and creating unique permissions, there is no option to create and the groups i.e owners, members, visitors etc
10 votes -
Change Log
It would be great if there was some built in change log functionality built in. Either as something I could view from the workflow designer or even if it just wrote changes to a file in the SharePoint site the workflow is built in.
I keep an excel change log for each workflow but a more detailed change log that had each change made to every control would be helpful when troubleshooting a workflow I have not looked at in some time.
4 votes -
"Approve/Reject" in Common Reference
It would be better if Nintex for Office 365 will also have the "Common Reference" feature like the "Approve" and "Reject" link for fast and easy approval. It's also work on both PC and Mobile version.
8 votes -
Save / Publish Timestamp in Designer
Look - I'm not the smartest, and I also tend to fluctuate between saving like it's going out of style, and saving so rarely that you'd think I was allergic.
I just want a time stamp in the top right hand corner that says Last Publish: (date time) -- Last Saved: (date time)
Surely that's a quick win?
9 votes -
Details upon hovering over actions
In On-Prem, we can hover over actions to get a brief bit of information about what's going on in that action - ie what variable is being set.
Please bring this into O365. With the bit of lag that happens in opening actions, this could save a substantial amount of time overall.
2 votes -
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 connections20 votes -
Help Needed Dynamics CRM Create Record Lookup
I am new to nintex need help.
I am using the Dynamics CRM Create Record action but it seems to be failing when setting the regarding field.
Can any provide details on how to set a regarding or lookup field in the CRM Create Record action field.
Thanks
1 vote -
Layout of Workflow Designer
There is a lot of white Space in Workflow Designer that causes a fair amount of scrolling on the web browser. My suggestion is to reduce the size of, or flatten, the action boxes. Also, crunch them together more. Maybe allow connections of actions that fall off the bottom of the screen to wrap to the top of the screen next to those actions that don't.
6 votes -
Allow States in State Machines to be Collapsed and Expanded
It would be really nice to be able to minimize and expand each state as we're working through large workflows, to increase visibility & use it as a sort of checklist as we work through.
3 votes -
Can Nintex also connect to outlook for doing a complex mailbox management ?
we need a workflow solution end to end for doing a complex mail box management with a group mailbox we use on daily basis.
Also workflow should also enable work allocation basis the criteria in the email body/subject/sender etc.1 vote -
Ability to programmatically import workflows with Connection Manager actions
Connection Manager is now available in a few workflow actions viz. viz. "Start Workflow" or "Office 365 update item permissions".
These actions though are not automatically configured, when exported and imported to another subsite (sharing the connection manager). This is a real problem, as now you can't programmatically import an exported workflow. Imported workflows need to be manually configured, by selecting the Connection Manager. All other properties are automatically configured, except Connection Manager.
9 votes -
Complete import of Document Generation Configuration
Currently when doing export / import of a workflow containing document generation actions, the doc gen actions drop elements of their configuration when imported to the target list...namely the source library for templates and output library for generated documents. This occurs even though libraries with the same title exist in the target site.
It is an impediment to releasing changes and makes the process more prone to human error.
Please retain the config when matching libraries exist.
1 vote -
Item Update in a List
Why did you get rid of the drop down box from updating an item in a list if the item in the list is multiple choice? I need to update a status from blank to "Pending Approval" but I already defined what the options were in the list. It should pull this through (and use to). Please fix it.
Thanks,
Seth1 vote -
State Machine - States not readable in canvas
When working with a state machine that have several states, the titles for the state path are not readable. I have tried zooming but the text for the state still isn't readable.
It would be nice if more text for the state could be displayed. Otherwise, a hover effect to display the state text would work.
7 votes -
Why can't we have a feature similar to Content control title in update word document? Doc generation does not support table,checkbox etc
My application with dynamic html structure containing checkbox and table structure was working fine while render to Control Content title but now, even though Rich text field support html conversion, It does not render my table, styling and the controls like checkbox,radio button
4 votes -
Deleting Component Workflow is not a true delete
Current deleting a component workflow is not a true delete as you can't reuse the name of the deleted workflow. Please fix this.
6 votesNicholas, This should not be the case, once you delete a component workflow you should be able to reuse the name for a different workflow. If you continue to experience this then please log a support call so identify the issue.
-
Notification options - Multipe approvers
Please allow (as already delivered for NW for SharePoint) the configuration of configuring the notification Options for individual approvers. More particularly, I want to be able to enable the notification E-Mail for certain approvers within one Action while disabling the notification for other approvers.
9 votes -
Workflows - permissions step tedious
Setting unique permissions is now one permission per action in the workflow (means you need many more steps if you set multiple permissions). On-premise you can set multiple permissions in a single step.
4 votes -
Workflow - task permissions wrong
Tasks are a free for all now, no longer are they permission restricted so they can only be actioned by the person they are assigned to (on-prem says ‘Sorry you are not authorised to action this task’ if it is not assigned to you), in the cloud anyone with ‘Contribute’ over the tasks list can action any task. Again forum workaround suggests a custom workflow that sets unique permissions manually.
7 votes
- Don't see your idea?