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
-
Save and Continue option
While it’s on my mind, one for the suggestion basket: Suggest adding an option to the Save dropdown menu that is in the vein of “Save and Continue” which would allow the user to save without having to go through the popup confirmation window and just return the user to the editing stage. Alternatively, it might work to allow one to set the behaviour of the Save button itself to that (presumably on a per-user or per-session basis).
:)Ben20 votesThanks for the feedback Ben. I am interested to know what the driver of the request is? Is it simply best practice saving every now and again, or is it due to the browser potentially crashing and losing your work? If it’s the latter, would some form of AutoSave assist?
-
Reorder UDA Parameters
When building and extending UDA's you often add new input/output parameters. Currently, the parameters appear in the order entered, I think. Would be great to have a way to reorder the parameters on the UDA configuration. Having the parameters in a seemingly random order can be confusing and has led to the wrong value be entered into a parameter.
22 votesThanks for the feedback.
-
flexi task: allow edit setting for escaltion,reminders and behavior per each assignee. today you can only edit the notification itself.
i've recently encountrd in this situation: i had a flexi task with two assignees, they had to agree on a specific outcome (approve). i couldn't add any more assignees to this task since i needed different behavior than "all must agree on a specific outcome". also, i didn't want the group members to recieve escaltion and reminders.
7 votesThanks for the feedback, we are reviewing this request for inclusion in a future release
-
Migration
Since a Nintex workflow can become quite complex with lots of information coming from multiple locations it would be great to be able to define all the pieces and parts that are needed for that workflow to run (a report of some sort). Further, once a designer/developer has created a workflow with all it's part and has unit tested the hell out of it, allow them to perform a save that pulls together all of the components into one Migration package / file / folder etc... so that when moving a workflow to a QA server it doesn't take manual…
26 votesThanks for the feedback Sunnie.
We’re reviewing this feature request
- Don't see your idea?