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.4 votes
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.2 votes
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.1 vote
Good to have the possibility to choose (by parameter for example) whether list item should be permanently deleted or moved to recycle bin.22 votes
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.4 votes
Essentially the same request (except for Nintex Workflow for Office 365) as done by Jimbo Alba at:
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.15 votesRoanna Gunaratnam responded
Hi all! Jason, In your scenario could you give me more details on what you are trying to do with the task ID, before the task is completed? Thanks.
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.
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 By34 votes
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
API support is now available to be able to automate inviting an external person...8 votes
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.78 votes
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.3 votes
In The Document Generation Action. When we click Edit Template the "Nintex Document Generation Tagger" not loading for Multfactor authenticated user.1 vote
Hi, thanks for adding the ability to email external email addresses! I thought this would work for internal distribution groups as well, but that seems to not be the case. It would be fabulous if we could do this (we have a forwarding account set up for it now, but it's a pain).16 votes
Currently there exists an action to assign an office 365 license to a user. However, there is no action to remove a license from a user. I'd like to be able to do this via workflow. This would be useful for off-boarding users, as well as writing workflows to transfer licenses from one user to another when needed.21 votes
This will just go through each item in the list once you pick the list you are targeting not having to set up any collections or such.1 vote
Bring back the From text box in the notification action1 vote
either fix the issue when creating documents based on Word Content Types, or allow Nintex Workflows to run as SP2010 Workflows, rather than
either fix the issue when creating documents based on Word Content Types, or allow Nintex Workflows to run as SP2010 Workflows, rather than SP2013 Workflows. SP Designer affords us, at least, the option to run as SP 2010 workflow when creating the workflow.6 votes
- Allow a user to paste in credentials and test to ensure the credentials are correct without having to save and publish the workflow.
- Have a query that pulls in the Salesforce objects available based on the permissions from #1.
- Display the objects' fields based on the object type selected
Perhaps create a unique designer area for managing Salesforce data. Most users who may need to interact with a Salesforce connector may not know how to grab the correct fields and thus not want to build a workflow using the action.10 votes
Would be good if we could still set this in O365 so that calculations between dates won't include weekends/bank holidays (the days we set in the managed holidays)55 votes
- Don't see your idea?