The Nintex DocuSign Connector currently doesn’t include a way to base 64 encode a document to pass it to the DocuSign web services. The DocuSign web service requires it to be base 64 encoded. It would be great to have an activity that base 64 encodes a document.

Most of the times WF does not publish. It gives error as If the problem persists, contact your support team with the following information:
ButtonPanel - handleXamlBuildError : SyntaxError: Unexpected token < in JSON at position 0

Which is not informative.

In the previous version of Copy a List item it was possible to copy the item to another site in the collection without additional credentials.

At the moment it is not possible to set a workflow start variable to "required". This function is highly needed.

The Document Generation often times produces an error and suspends the workflow. It would be very useful if the action would optionally dump the error and detail regarding the failure to the history. Currently there is no way to understand why the error has occurred.

The Yammer Message action should allow for the uploading of images to either users or groups. This is supported by both the Facebook and Twitter action, but not Yammer.

HI,
i think there must be a column when the workflow will start except of this,
like choose any drop down trigger,or check box for any filed

Thanks

When updating multiple list items for example tasks it would be usefull to have a ignore errors checkbox to resume with the workflow if the update list item can't find the item. This would help because tasks disappear when 1 of 3 tasks is approved. But a parallel loop which updates the tasks with information still tries to find and update all 3 tasks but only 1 is still there. Workflow then crashes.

When using the Yammer Post action, it send the users posting an email to authorization to post and is a generic requests which is very confusing for end users and they may not have an idea why this is being sent or from what process.

Allow the addition of custom message, or customization of email.

I really wish we could pass through Email addresses so users are tagged in the post and sent a notification.

Also post on behalf of another user without those confusing authorization messages.

Good to have the possibility to choose (by parameter for example) whether list item should be permanently deleted or moved to recycle bin.

If using the action to send emails to an external email, I would like for there to be an option to error if the email being sent to is invalid. Otherwise, the workflow will continue as if the email was sent and no one will know that it wasn't sent.

Essentially the same request (except for Nintex Workflow for Office 365) as done by Jimbo Alba at:
http://nintex.uservoice.com/forums/229405-1-nintex-workflow-for-sharepoint/suggestions/6440022-populate-task-id-as-soon-as-the-task-is-created

All task actions can populate a task id variable but usually populate the variable only after the task is completed by the assigned user. I would like to recommend that this behavior be changed so that the task id variable is populated when the task item is created and assigned. This way I can query the task item even before it's task action is completed.

Allow a user profile lookup that's initiated using the logged in user's credentials or session (i.e. the initiator), or at least the workflow publisher's identity.

The "Office 365 Query User Profile" lookup currently requires you to enter a username and password.

More details:
SharePoint Designer 2013 has the ability to query without credentials using the "User Profiles:" action.

SD 2013 example:
Lookup for String
Data source: User Profiles
Field from source: First name
Return field as: As String
Field: Account Name
Value: Current Item: Modified By

IN SP2010 Nintex workflow there is an action Query LDAP which is used to query the DL (Domain Group) Users. But in SP Online am not getting the equivalent action for Querying the members of the particular Domain Group
If any one has faced this scenario please help me

Bhanu

API support is now available to be able to automate inviting an external person...

An additional "contains" test would be great to test in Run if statements for example if value is part of a multiple choice field.

If possible also "starts with", "is empty", "does not contain" would be very helpful additional operators.

In the "Office 365 update item permissions" action, we have availabity to configure user (email) or SharePoint group name (one or several) but it is not possible to register a security group which has been declare at the tenant level (when we configure this kind of group, the workflow is suspended and the result is "Failed to resolve user xxx" and issue is the same for a group name or email group name).

It will be interesting to implement this feature to avoid the creation of SharePoint group in the website and duplicate information between web and tenant.

In The Document Generation Action. When we click Edit Template the "Nintex Document Generation Tagger" not loading for Multfactor authenticated user.