It would be great to have a From field that supports dynamic references. Most business requirements want emails sent from a specific account, which is not supported in NW in O365!699 votes
To support this requirement we’ve just release the following features
- Specify a customizable sender display name for both email and task actions, we understand one of the main requests was to be able to supply a custom from email address however due to many of the limitations in the cloud we are currently unable to deliver this request and so hopefully being able to add a From display name will get you one step closer..
- Add a customizable Reply To email address for the email action so you can control the email address when people hit reply.
Hope you enjoy these features and be great to hear any feedback once you try them out.
There needs to be some notifcation to the designer or somoene if the workflow errors. When you have multiple workflows across multiple sites a notifcation is helpful in managing your workflows and any issues. This was available in on-prem why has it gone away?641 votes
I’m happy to say this feature has now been released, for more detail on how it works check out the blog – https://community.nintex.com/t5/Community-Blogs/Introducing-Workflow-failure-notifications-for-Office-365/ba-p/107432
We’ve just released the ability to capture comments from via LazyApproval, apart from that you can also easily store and retrieve those comments (including ones made via Nintex Forms or directly via the task) into a new task action variable (Task comments).
For those who are specifically interested in capturing from LazyApproval the way you do is by supplying the outcome separated by a comma and then the comments .e.g. ‘Rejected, Need more detail before can approve’.
Check it out and let me know what you think…
At this time the "Office 365 update item permissions" supports default permission levels only. It would be nice to be able to select or just type in the name of a custom permission level to be assigned to the workflow item that has been added to the site/sitecollection permission levels.377 votes
Happy to say this feature has now been released..
The ability create copies of current list items (workflow context) should be included.367 votes
Copy an Item action has been released and is now available for use. You can find this action in the Integration category of the toolbox.
When designing a workflow for O365 a lot of Nintex Store actions like 'Create Site' require an account and password explicitly. As I am -designing- the workflow I do not want to know the actual Workflow Account password executing these actions, that's for the admins to know. The only way to enter these passwords is by using plain text either directly or by means of a Text variable. So I would propose a new 'Secure String' or 'Password' variable so at least I can call someone to type in the password without me knowing it. Of course it would be best that these actions don't require an extra direct password or just send a mail to the user indicated asking him to login and trust the execution of the workflow.
When designing a workflow for O365 a lot of Nintex Store actions like 'Create Site' require an account and password explicitly. As I am -designing- the workflow I do not want to know the actual Workflow Account password executing these actions, that's for the admins to know. The only way to enter these passwords is by using plain text either directly or by means of a Text variable. So I would propose a new 'Secure String' or 'Password' variable so at least I can call someone to type in the password without me knowing it. Of course it would be…339 votes
I often find nearly Site Workflows I create need to be scheduled as they are for batch processing, polling lists, sending 'Near due' notifications and other related tasks.
At the moment, my understanding is that you have to loop indefinitely and a delay for action to mimic a schedule. I.e. complete some actions every 2 hours.
It's just a bit hacky and a tough sell to customers.314 votes
In Workflow 2010/2013 on premise when setting automatic start for create/modify as well as Yes and No we also have Conditional. We can then use a condition builder to specify eg. column values including what they used to be and what they are now. Can we have this in Workflow O365.
I know that this has already been asked for but it looks like the requirement wasn't clear303 votes
Client would like the ability to create reusable workflows to use on similar lists.253 votes
I am pleased to announce this capability has rolled out this week as a Component Workflow. Learn more at https://www.nintex.com/blog/whats-new-component-workflows/
Need to have the option to include attachments for email notifications that are sent from the task actions.252 votes
We have released the first phase of task attachments. You can now add attachments to the Initial task emails. For more details, visit our community blog https://community.nintex.com/t5/Community-Blogs/Task-attachments-and-CC-BCC-Workflow-for-Office-365/ba-p/112529
In the next phase, we will add an option to include attachments for Reminder and Escalation emails.
The absence of the Assign Flexi Task with configurable outcomes is a huge miss for me.194 votes
This feature was completed a while ago.
I recently try the Nintex Mobile App with our O365 SharePoint site. It's working well and i was surprised by the design on different devices and OS.
It could be nice to improve this app with the ability to manage his tasks from his mobile and not just be able to fill a new form.180 votes
The absence of action sets is a major development need!170 votes
Action Sets and Collapsible actions are released. Here is a blog that gives a good succinct description.
We have released the first phase of CC/BCC support for the the Initial task emails. For more details, visit our blog https://community.nintex.com/t5/Community-Blogs/Task-attachments-and-CC-BCC-Workflow-for-Office-365/ba-p/112529
For next phase, we will look to include CC/BCC for Reminder and Escalation emails.
If you build workflows in one tenancy, then publish to a different one, you cannot overwrite an already existing workflow. This means the import can only work the first time. If you import a new .nwp (with changes you made in a development tenancy, for example) you cannot import this to production as it does not allow publishing - it gives the error that a workflow with that name already exists, and does not support overwriting like NW 2013 on prem. Renders import/export quite useless if you need to properly test and move workflows around tenancies. Only way to do it is to fully delete the existing workflow before importing again - but this means you lose all running instances and all workflow history - not good!
If you build workflows in one tenancy, then publish to a different one, you cannot overwrite an already existing workflow. This means the import can only work the first time. If you import a new .nwp (with changes you made in a development tenancy, for example) you cannot import this to production as it does not allow publishing - it gives the error that a workflow with that name already exists, and does not support overwriting like NW 2013 on prem. Renders import/export quite useless if you need to properly test and move workflows around tenancies. Only way to do…147 votes
I am very pleased to say that we have just released this capability. It does come with a warning however, it is now possible to overwrite a production workflow with the wrong design on import. Unless you have exported the design (before saving or publishing the incorrectly imported workflow) your production workflow will be irrecoverably lost. We have included warnings, a tick box and help link to inform users of this possibility as well as a blog post on an approach to use to recover the workflow (or prior stored versions if they have been saved). Blog post “Best practices for workflow version control” in our community site – http://bit.ly/2noCDkl.
We're having to rely pretty heavily on web service calls to supplement the currently available action set. It would save an inordinate amount of time if we could leverage UDAs to interact with these in a more structured fashion.
Barring that, since Action Sets are going to be implemented in an upcoming release will these support the snippet feature? Injecting a pre-build snippet would give us the same time savings but doesn't result in such a clean workflow.132 votes
Reusable workflows has been delivered via the Component workflow features that was recently released. For further detail about how this feature works please see the blog written by Chris Ellis – https://www.nintex.com/blog/whats-new-component-workflows/
The ability to send emails to recipients outside of the O365 instance.131 votes
This has been released into service and is ready to use
It would be nice if the email notifications sent with a "Request Approval" activity and "Assign Flexi Task" activity, could have "Approve" and "Reject" buttons instead of hyperlinks.126 votes
This capability is now available on O365, please refer the our blog: https://community.nintex.com/blogs/NintexProductBlog/2017/10/04/actionable-messages-in-nintex-workflow-for-office-365.
Since we have leveraged Microsoft’s actionable messages to build this feature therefore it will initially be available to users of Outlook online and Outlook 2016 Version 17.10 (Build 8201.1000), however Microsoft do plan to roll this feature out on Outlook for Mac and Outlook for mobile next year.
I would like to see the disable feature per Workflow Action available in the designer.106 votes
Implement the Nintex Lazy Approval capability within Nintex Workflow for Office 36590 votes
Happy to say that LazyApproval for Office 365 is now released.
- Don't see your idea?