An error occurred while saving the commentOwen Runnals commented
I definitely agree that this would be great. I would even be happy with a check box in the Task/FlexiTask/Request Data actions that says "Use Item Form for Task" then we can just build out the single item form to collect all the data. We'd need forms to create the custom buttons based on what results were configured in the task. It would also help from a data growth perspective when we have many tasks in a very common workflow (task list grows incredibly large very fast).
476 votes21 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →Jon Hardy responded
The task ID is populated once the task is completed. Before this the task list items can be locked by the task engine for processing and a workflow accessing this task may fail. There has been therefore a strong reservation form our Engineering group to implement this capability even if technically feasible.If one wishes to delegate the task then the delegation should be used.
Should you have other use cases for accessing the task list before the task is completed then please let us know what they are. There may be an alternative way of meeting this need that will not introduce the possibility of workflow failure.
56 votes4 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →