Setting business hours for initial emails and reminders.Looking for the Same configuration in Assign a task process Action in O365.

Setting a modified start condition in the workflow Settings does not trigger the workflow to start when the document library item is modified (a document set). The modified start condition compares the values of two fields on the document library item and should start the workflow if they are not equal. The two fields being compared are People fields with multiple selctions possible.

I can't do simple math operations on currency columns because they get treated like unparsable strings.

"$100" * 1.43 = Exception casting "$100" to type double.

Please provide a way to not have "$" as part of the value................

Need a way to test user credentials and connections. Workflow keeps indicating bad username format or password or something and I can't make sense of if it is the connection or the parameter to the query.

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.

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

Right now I can't find any way to see the history of a component workflow called from another workflow. If possible it'd be great to have component workflows log to the caller's history.

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/DisablingHeaderandFooterinNotificationMessage

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 if the rich text has a table element, the table has not rendered as it is on the result of Nintex document generation action

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.

Currently available on premises.

I would really like to be able to create our own custom workflow actions that we could use within our site collection this would make the product much more flexible.

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

Send Document to Repository Action does not work. I have tried moving the document in the same site with no luck. I just get this error "Unable to find document to repository." what does this mean and why am I getting it. - Content Organizer is turned on.

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.

As Nintex Workflow for 0365 is heavily dependant upon the 'Call HTTP Web Service' action, creating and testing them is particulary time consuming with the feedback cycle, being build workflow, publish, run and then view the history log.

The 'Run Now' provided within the on-premises solution allows users to call the web service there and then to test the input and output.

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

Currently, workflow variables are displayed in the order they are created, which is inflexible.