As of now, any component workflows created in a Office 365 is visible to all users within the tenant. This will create confusion in scenarios where in the component workflow is required for a specific site collection and not to be visible for others.

A visibility flag might help a long way to target component workflows for specific site collections rather than entire O365 tenant

We are trying to figure out how to remove headers from emails from the workflow in SharePoint online. I see you have a KB article:

https://support.nintex.com/SharePoint/Workflow/Disabling_Header_and_Footer_in_Notification_Message

But that appears to only be for SharePoint on-prem. How do we disable them in SharePoint online?

I opened case number 00246103 and they suggested I post here. They are still researching. I would call this a feature request.

Currently our Site workflows have been firing an hour early due to Daylight Saving Time ending for this year. This is apparently not a bug for some reason, and should be considered such.

Currently if the rich text has a table element, the table has not rendered as it is on the result of Nintex document generation action

Please add the workflow graphical view in Office365..this must be useful for the enduser...

Either an inline function or action allowing dates to be calculated minus weekends..
Given that Weekends vary from country to country and some tasks don't require this, it would be great if that within i the task action you could choose and calculate which days should be included.

It would be nice to have version control. Its a great feature that is missing from the on-perm world.

In NWF 2010+ through Workflow Settings we can show a button to start workflows on the item edit menu. Is this planned? This is a very useful feature for high priority manual workflows.

I added a comment to this idea: https://nintex.uservoice.com/forums/218291-3-nintex-workflow-for-office-365/suggestions/5740552-email-notifications-having-approve-reject-bu, but not sure if the comments are being monitored since it is marked as completed.

Based on my clients' feedback, the greatest need for button approval via email is from mobile devices. When I access the LazyApproval email from my iPhone, the actionable buttons are not there.

Side note: The actionable message buttons are available via my iPhone for Flow tasks.

A way to show the component workflow status of a component workflow in Nintex Workflow for Office 365

Allow tracking of Authorisation emails sent by Docusign

If Docusign revokes the authorisation token and it needs to be authorised again it would be good if this can be tracked from a workflow

as Nintex workflow id Getting Change all import and publish,there is no action to find current id of the workflow,

I have received some errors where I don't know what to do, because the error is not clear and I can't find anything in internet,
For example: EventAggregator. What is that? What does it mean? What should I do?

Add the ability in document generation action to generate anonymous or guest link and share the document outside of their organization

SharePoint online allows to Share a document or a folder by sending or posting an anonymous guest link.

We can leverage this to add the ability in document generation action where user can generate anonymous or guest link and share the document outside of their organization.

https://support.office.com/en-us/article/Share-sites-or-documents-with-people-outside-your-organization-80e49744-e30f-44db-8d51-16661b1d4232

Currently an out of office email causes LazyApproval within O365 to send a second email saying that the response was not valid. LazyApproval should know that it's an out of office email like the system does on-prem.

Currently, Nintex for O-365 workflows are not able to parse the Date and Time from the following publishing fields - Scheduling Start Date/End Date. Any workflow email that includes these fields shall display incorrect time (due to time-zone difference between the Nintex App and the Site-Collection). We would need this to be corrected, as all the site-collections will not be in the same time-zone where the Nintex Apps are hosted.

Allow the option to skip an action if an error occurs while performing it. For example, if a user-defined emailed address is undeliverable for sending a notification, then allow the workflow to continue.

The behaviour of the Start Workflow action is to suspend the originating workflow if an instance of the called workflow already exists for the list item.

Proposed is an enhancement to either:
1. allow the Start Workflow action to be configured such that the originating workflow is allowed to continue
or
2. introduce a 'Check Workflow' action that returns a value to indicate if if an instance of a workflow exists for a list item