đź‘‹ 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 have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
Nintex RPA allows to develop your own plugins which can be used in Advanced Commands.
Sadly the current implementation spawns a child process Leo.PluginActivator.exe which then handles the execution. Spawning this process and returning the result back is painfully slow (about 10-15 seconds, sometimes longer). Unusable in an attended scenario.
How about having a plugin directory and with start of the Assistant the libraries in that directory are loaded dynamically and can be used directly without spawning a clumsy child process?
This will speed up execution in attended and rpa the same way and even features which are currently not supported by Nintex RPA could be implemented.
Maybe add a plugin store on the Nintex Community where developers/customers can share their additions to Nintex RPA. (Thinking of Email-Plugins, Local Database Plugins, Encryption Plugins etc.)
