All ideas

We can check the usage of a variable in workflow actions, but we can not replace every that variable with a different variable. To do so, we have to replace each instance of variable use one at a time. Mass replacement of variables will save custo...

Allow users with administrator access to workflow tasks to delegate on behalf of other users. If a user is absence or terminated and has a pending task there should be a way to delegate the task to another user since the original user cannot.

In the instances page, the information being presented makes it difficult for customers to correlate with a particular record within a SharePoint list/library. During troubleshooting or analysis of tasks, they are unable to easily filter a specifi...

When a user completes the form and signs the document allow this signature to be used as an image variable within the workflow. Removing the need to store/generate an image file and then call that file into a workflow. This is important for data p...

It would be quite useful to sort the view of workflow variables either by datatype or alphabetical order. Currently, when you have more variables it gets hard to scroll through and find.

Here is the use case. I have an approval workflow and the requirement is the submitter should be able to see the final result of the approval in the form. E.g, approval status and name of the approver. For now, we can use form variables in the wor...

Would welcome support of Rich text multi-line text fields in Document Generation. At least allow us to have bold, italic and especially a link supported when generating a PDF from a Word template.

Missing the ability to auto complete tasks, as found in Nintex for Office 365 for instance. Would be great if this feature was added to NWC aswell.

Currently if a xtension responds with a code other than 2xx the call is considered to be a failure. However many APIs legitimately return a status-code other than 2xx. For example if you query a service and no results are found, many APIs return ...

Often times, we can have very rich and full Forms that trigger a workflow. Sometimes after a flow has been submitted it may have incorrect data (this is not something that can be validated correctly or handled with rules). Example we have an onboa...