Workflow Designer

Many of us have learned the hard way that a condition is normally required when using the Update Items action since failure to do so results in the all items being updated. It would be so helpful and appreciated if there is a message warning that ...

Add the option to return a promise, and subsequently a response, from a component workflow. I like the ability to have a callback URL to pass data back. But often, component workflows run very very quickly. Why not allow us to return a promise / r...

Automation cloud obviously has both dictionaries and multidimensional collections - but collection operations don't by default support creating your own. This limits what you can do with component workflows. For instance, I've created a component ...

When I'm working on multiple workflows, it can be difficult to know which one you are currently editing. This is especially frustrating when you're editing DEV/UAT/LIVE versions of the same workflow. Having the title displayed above the Start Even...

We need the ability to format date to string with a user friendly output of MM/DD/YYYY (04/08/2022) and no time as well as MON DD, YYYY with not time (Apr 8, 2022)

Azure users that are synchronized via Microsoft's cross-tenant synchronization (are active users vs guest accounts) do not show up in NAC Users Management even though they are valid accounts. See Microsoft's article: https://learn.microsoft.com/en...

When we design a form, it's common to need to allow a user to update their submission - ESPECIALLY when the form is complex, or has a repeating section. Right now there doesn't seem to be a way to do this unless you use a sharepoint form. Unfortun...

When using the "Create New Item" workflow action to create a new line item on the relevant SharePoint List it would be helpful if it could create the item by the person who submitted the form for authenticated users (internal staff/users). This wo...

Switch condition does not have an other loop. Trying to migrate a Nintex Office 365 workflow to NWC but due to lack of this functionality, the migrated WF cannot be like for like.

The Assign Task to Multiple Users provides variables for Outcome, Task Responder, and a few others, but no date variables. You can use the "datenow" value in a date control to capture the approval/rejection date on the task form (see question here...