The Action ID can be passed to another workflow using the Store and Retrieve Data actions. Even when the task is not yet completed. In this case I want to know the associated task item and be able to query it. So a 'Query Task' action would be useful here where I can specify which content type and fields I want to get. I could have just pass the Task ID to the other workflow but the task id is only available when the task is already Completed.

The current Execute SQL is synchronous. For a stored procedure call that could potentially be timely, this makes the workflow stop and wait.

Looking for a way to do this asynchronously.

Add an option to allow the user to toggle the error handling for actions to either recognise non delivery of an email as an error or not.

Sometime input is required from users (i.e. Flexi Task) but you don't want them to actually go to the site to see the other list items. So when a flexi task has been assigned and approved or declined it always opens the relevant site on which the list is.

Will it be possible to specify a URL or close the browser after approval has happened?

Can we use Nintex workflow to add item to SharePoint 2013 list when there is a new item in SharePoint 2010 list? (or cross farm)
and only few columns in SP2010 list will be add to SharePoint 2013 list.

lots of cases, we might need to copy some columns from a list to another one list(or cross site/farm).

There are currently no actions that can be used to delete SharePoint lists. You can delete list items, and sites. But why not make it possible to delete Lists?

I have a list related to an element in a list in another site collection. How can i access to this element without a List CAML Query. any ideas please thinks

Ability to import more file types and populate Sharepoint lists and even Libraries. It would be nice to be able to pick up an Excel spreadhseet (xls, xlsx or CSV) and interogate / use the data and then populate a Sharepoint list. A further extension would be to upload a big chunck of documents and supply a spreadsheet with the necessary metadata for the documents.

I cannot work with Users from other Subdomains.
Example:
I want set a User from a nother Subdomain to a AD Group in my Subdomain.

Root Domain= Nintex
Subdomain= De.Nintex
Subdomain= Us.Nintex
Subdomain= En.Nintex

It would be great if we can able to manage the document library version, like if the approval reject, then roll back to previous version of the document.

Workflow colum updates on an user modified document event (system action do update to metadata columns) needs actually an wait action to avoid locked files/workflow errors. A better handling would be nice.

Display unavailable workflow actions in the Workflow Designer. When designing site workflows in the Workflow Designer, workflow actions that are only available for lists are not displayed. It would be helpful to see those workflow actions otherwise you wouldn’t know they exist unless you were designing a list workflow. The unavailable workflow action could be greyed out with an indicator that it's not available for site workflows but is for list workflows.

We have scenarios where PA's to managers have access to the managers' mailboxes, however they cannot reply to approval tasks using lazy approval because of the "sent on behalf of" headers. We also have shared mailboxes for groups that have the same issue. Allowing lazy approval to work on "sent on behalf of" would make life a lot easier.

Add functions to design the request data form in lazy approval, placement of the colums in the email form.

• An action that does nothing other than have the ability for the developer to put development notes against it, acting as a label or a placeholder. eg. I might want to add a real action to replace this label at a later stage but currently I'm just putting an action there as a placeholder...

• Ability to move an Action by dragging it pass the current viewable screen while scrolling.
• Have a 'cut & paste' function available with the Action.

With all of the List and Library Actions, whether it be Query List or Create List Item, you have to select the list you are interacting with. What if you are creating that list earlier in the workflow, meaning it doesn't exist yet. I.E. - [Year]_Archive

This would eliminate the need to use "UpdateListItems" method, since it can be very tedious building out the XML for the Method.