All ideas

Would like the ability to save minor changes as a .x version instead of a full version. For example, just updating a singular target that may have been failing could be saved as a minor change warranting a v1.1 versus adding in a new loop through ...

Currently when building/running scripts in Nintex Bot, the display scale needs to be set to 100% for it to look and run correctly. In some cases this option is locked by group policy, preventing us from using the application. It would also be a ni...

A lot of institutions schedule processes around non-calendar schedules such as "Second Tuesday of the month" or "The 5th of the month, or the first Monday after". Currently scheduling these types of bots means having to do manual date calculations...

Currently when scheduling a Botflow in RPAC, it is not possible to prevent a Botflow from running on a non-working day or a holiday. Proposing a feature to upload a list of days we want RPAC to exclude when running scheduled jobs. This feature wou...

Proposing a feature that would show task/action differences between versions of the same Botflow. This would increase visibility into version functionality when having to regress to a previous version. It would also be beneficial when auditing bot...

Please consider allowing users to create a new version of a currently published botflow. Currently to save a new version, you have to unpublish the botflow first. This feature would allow maintaining separate "development" and "production" version...

I have a botflow that runs every 5 mins, so you can imagen when viewing the instance page its a lot of scrolling, and if I need to search for another botflow that is running lets say 1x a day I have to scroll to search it. I think it would be best...

Current Application In the Query List action, you can only provide up to 2 query conditions, and 1 specific field. Requested Enhancement Allow for an "infinite" number of conditions. Model off of the If Statement. Allow user to specify a Group wit...

When Targeting Excel, specifically Sheets, a 'Sheet Exists' action would be nice. Current workaround is setting an error task, attempting to select a sheet that may or may not exist, then adding logic to determine if that error task was hit.

We would like to see a new variable type, secret or hidden, similar to Postman. This variable would be useful inside LE. A use case we have is internal REST calls. For OAuth 2.0 the Body requires a client secret and/or API Key. Currently there is ...