Skip to Main Content
Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!

If you are looking for the Nintex roadmap, you can find that on Nintex Community

If you have questions about Nintex Ideas, please contact

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact

Workspace Nintex RPA LE
Created by Guest
Created on Feb 14, 2022

Disallow Saving Botflows to RPA Central Once Contractual Max Hit

If 20 Botflows are contractually allowed to be saved to RPA Central, it would be extremely helpful if an error message appeared when trying to save Botflow number 21 that stated no more are allowed and disallow the user from saving to RPA Central. The user should still be able to save the Botflow locally, but not to RPA Central in this case.
Per conversations with support, there is no current mechanism in place to prevent contractual breach for the number of Botflows allowed. We have to manually delete added Botflows every 1-2 days in order to not breach our contract.
  • Attach files