Workflow Designer

Give the option to assign a task without emailing the assignee(s). With the addition of my nintex, some users are already asking for the option to just monitor their tasks in there on a daily basis rather than receive emails for each task. If mult...

At present, we can only escalate tasks to a single assignee. Customers who utilize this feature tend to escalate tasks to more than one assignee or to a group. We need the ability to escalate tasks to a collection of emails, a text of semi-colon s...

There are cases where even if an action fails, the process should continue. We want to be able to manage the failure within the process and handle it proactively instead of reactively (only after it has failed). There are different examples and sc...

In the Assign a Task action the option to choose "Minute(s)" is not present when setting (subsequent) reminders. However, this option is available in the escalation settings. This lack of availability can be inconvenient for testing purposes.

We have no ability to undo or redo what we have just done. The only way to make this happen is constantly saving our work for everything we do, this is not practical when building a workflow for the first time. Why did this feature not roll over t...

Hi there, it would be great to be able to cater for business days only (exclude weekends), when configuring NWC task assignment reminders and escalations. Currently when specifying days as part of reminders and escalations there seems to be no eas...

There needs to be an option to add lazy approval actionable message to emails generated from tasks. One of the biggest drawbacks that is keeping me from switching from O365 to Cloud, is that option. With current cloud lazy approval, user has to re...

Hi Nintex Support Team, Scenario is while after start event the execution goes to a Task event with a notification to take the action right. So in between we want to engage the user on the same page and then redirect to the Task form.

Currently we have an issue testing a workflow where it gives us "Semantic Errors" when we try test the workflow. When we try to publish the workflow we get the following "Some fields contain references to invalid variables; we recommend removing t...

We require a simple unique identifier for each workflow instance to use in a subsequent "Set Instance Name" action, and other communications as a short way of referring to a particular instance. At the moment the workflow sends data to a sharepoin...