1 - Nintex Workflow for SharePoint
This forum is open to any ideas and feedback for all of our on-premises Nintex Workflow products, including 2007, 2010 and 2013.
- The Nintex Workflow team
-
Workflow Inventory Add workflow and edit workflow direct links
I would love to see the link to Create a new workflow, and the direct link to edit the workflow added back to the Workflow Inventory (WorkflowGallery.asp) page.
The standard Nintex workflow version used to have both features, and they were removed in Enterprise version for some reason? It used to be really nice not only having all options on one page, but to be able to create or edit the workflow just 1-click away. Now you have to click on workflow name, then click on edit for example.
12 votes -
Recognition of changes made to item properties by other Nintex workflows
Often times, within a workflow, changes need to be made to item properties. If there were a way for Nintex to recognize changes made by Nintex (system), that could make conditional start options much easier for other workflows on the same list/library. In other words, a wf update to a field won't trigger a change that starts another workflow. Being able to add conditional starts that EXCLUDE changes made by Nintex, versus a human, would be very, very helpful.
9 votes -
Test Mode
Have a Test/Debug mode option in the Workflow Settings that you can check an uncheck. Then for each action, allow a check box to enable or disable test mode. If Test mode is checked in the workflow settings, then any action with its Test Mode checked would be enabled. However when you uncheck the Test Mode box in Workflow setting (meaning its going live) then each action with Test Mode still checked would become disabled. This would be a good time saver for actions like Log to History and Send Notification where you only want them in your workflow for…
102 votes -
Custom Text Color in Designer
It would be great if there was a way to modify the text color inside the designer independent of the site text color. This way when changing the master page, or default site look, we can make sure that text inside Nintex is always visible.
6 votes -
Improve 'Refresh Lists'
Clicking 'Refresh Lists' always involves removing filter and field criteria specified in the task.
I would like the criteria to be preserved if it is valid after Refresh Lists is clicked
4 votes -
Mark flexi task path as approval or denial
It would be nice to mark a flexi task path as "approval path" or "reject path". Normal approval action will be shown as red or green depending on denial or approval. Flexi action is always green as it doesn't know which is an approval or denial.
For better showing denials it would be nice to have that functionality.1 vote -
Move Task form properties view setting to the task level
Actually Task form properties view is a global setting defined at the farm level (in Global Settings in CA), could be very useful to set it at the task level, so each task, even in the same workflow, could have a different view
14 votes -
Flexi Task easily reorder task outcomes
When using Flexi Task, there is no easy way to move the order of Task Outcomes. So if you wanted to present Reject, Approve instead of Approve Reject, you would need to rename each one.
It would be nice to be able to drag/drop the outcomes in any order or have the branches dictate the order when you move branches left to right etc.
27 votes -
Give users with Design rights full capabilities for Site Workflows
For SITE workflows, a user with Design rights to the site has limited capabilities to work with those site workflows. This is because they cannot see the Nintex Workflow 2013 menu from the gear/setting drop-down menu. If I send them a link to the workflow, they can edit it and publish it, but they cannot Manage Workflow Inventory, View Workflow History or Schedule Site Workflows since they can't get to the menu. To see the menu, they require Full Control rights to the site. We lock down sites so that very few people get Full Control rights to a site,…
6 votes -
Colourblind-friendly visual markers for workflow statuses and Designer UI
Currently the Workflow Status page uses green/yellow/red to denote steps that were completed/in progress/errored, however the shades chosen for these are indistinguishable to some colour-blind people. This means that they cannot tell for instance whether a step is in progress or errored. Also, currently the only indication that a step is "disabled" is its image being shifted to greyscale which is also problematic for others including myself.
Some sort of visual indicator of the step's state beyond RGY and full-colour/greyscale would immensely help to support workflow developers and designers who are colour-blind.
3 votes -
A way to confirm the servers enlisted in the license file
Hello team,
Our customer complains about the file format of Nintex license file, because it's impossible to verify which machines are registered in the license file unless the file is actually loaded to the server to which its license is assigned. They need a feature or a tool to dump a list of servers enlisted in the license file. The feature would enable the user to check whether the license is sufficient or insufficient for customer's farm even before the farm is deployed.
1 vote -
Control Nintex features activation
I'm hoping we are not the only organization that wants to control who can create Nintex workflows while allowing site collection administrators and site owners the ability to manage other aspects of their sites.
We are aware we can manage permissions at the site collection level via the "Allow Workflow Designers" however that requires us to touch every site to alter this.
It would be nice to give organizations an option on controlling permissions either at the farm level or the site collection level. This will allow organizations that don't want users haphazardly creating workflows and then looking for the…
1 vote -
Update yellow pearl icon from 16bit to 32bit
This is very minor, but please update the yellow pearl graphic in Nintex Workflow to be 32 bit colors. It looks like something from 1995.
This is the yellow graphic you see when hovering or dragging actions over empty spots in the Designer.
Thanks!
1 vote -
Actions involving multiple fields - be able to change field order
For actions that involve adding fields (eg. Update Item, Create Item), I would like to be able to change the order of the fields once they are added. This would help when checking that all the correct fields are added and also help in troubleshooting.
6 votes -
Add keyboard recognition to drop down menus
When any drop down box appears, I would like to type a letter on my keyboard and have the cursor jump down the list to the first item that begins with that letter. For example, if I have a list with 50 fields on it, it would be good not to have to scroll down the list each time with my mouse (it reduces the amount of time I am swapping between mouse and keyboard). Thanks
4 votes -
Option to cycle (disable then re-enable) Nintex workflow across a farm
Several times over the last couple of years, after an update to the Sharepoint platform (2010) we've been left with Nintex WF running incredibly slowly on all the sites where it's in use.
The recommendation from Nintex support, which often seems to work, is to disable and then re-enable the Nintex Workflow features at the site level. This is simple enough but a pain to do across a lot of sites.
It woudl be very useful to have an option, or worst case even a powershell script for farm admins, that would look across all sites, store the current Nintex…
5 votes -
Workflow access to attachments
Workflow access to attachments on list items seems extremely limited. The list item property "Attachments" tells me whether at least one attachment is present (True/False) but nothing else.
I want the native ability in a workflow to see the attachments on a list items as a Collection so I can:
1) Count the number of attachments
2) Iterate through the attachments and for each one see:
a) File name
b) File type (extension)
c) File type (MIME)
d) Attachment URL
c) File size
etc.
3) Add (by prompting the user to upload a file) attachment
4) Add (by moving/copying a…123 votes -
Add a MOVE method to the Nintex Web Service
Being able to MOVE an item or document in SharePoint maintains the version history of that item as opposed to a COPY that creates a new item and doesn't maintain that history. Currently MOVE can only be done using Content and Structure or WEBDAV. Being able to automate this in Workflow would be very useful.
28 votes -
Global Flexi-Task Content Type Update
Would be great if you could globally update the Task Content Type that the Flexi-Task actions are using. This way if you need to use the InfoPath Content Type, or a custom Content Type throughout the environment, you don't have to update every single Flexi-Task action to use this new 'default' Content Type.
3 votes -
Workflow description in Workflow Inventory
When you hoover over a workflowname in de Workflow Inventory, the description of the workflow should be shown. This would help in using short workflow names AND finding them back very easy.
Thanks,
Peter29 votes
- Don't see your idea?