Would like to be able to retrieve information from the workflow task created in a previous step. Currently there doesn't seem to be a good method for doing this other than trying to use the "related Items" field for validation (which also fails). Would like to see the related workflow task associated as an integral part of the workflow variables.12 votes
Thanks for the feedback. Can you advise the kind of information you want to retrieve, what the specific scenario is etc, so we can better understand what you are trying to achieve?
Is it possible to replicate the user experience for configuring the action for assigning a task in on premise?
i.e. In On premise version, the different areas are split into a ribbon which makes it easy to identify what you are configuring. In the Office 365, it can sometimes be confusing as the configurations screen is in one page.2 votes
I noticed a strange translation for the english action, call http web service, this is translated to "bel http Web Service", translated to english "dial http web service" a better translation would be:"Roep HTTP Web Service Op"2 votes
Sharepoint is moving to a app-based world, what I think is cool, if your app needs a workflow you can use the visual studio to create this workflow, but it would be great create this workflow with nintex14 votes
Client needs to the ability to create a Nintex workflow as an app so they can specify access token.5 votes
Thanks for your feedback. This request is currently under review.
Is there/will there be a way to set it up so if a task is rejected, you can setup an action (i.e. email initiator) to let them know that the task had been rejected, and conversely if it is approved, have them alerted that it has been approved?1 vote
Thanks for your feedback. We are currently reviewing this with the development team.
Historically we haven’t included default rejection / approval notifications in the task actions, preferring to give the user the power to add a notification actions where necessary and to reduce the configuration burden in the task action. However we will look into the option.
If others think this is a useful feature, please vote up the request.
- Don't see your idea?