đź‘‹ 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
Disorganized:Poor organizational structure results in all rules being piled together. Sometimes, to implement a single business logic, the logic must be scattered across multiple rules. For example, when processing listing data, or when using if-else statements (when a confirmation is used with an if-else statement, selecting the negative option triggers the else branch—an unexpected outcome. This forces the if-else logic to be split into a separate rule).
Black Box:Even with good descriptions, it is difficult to fully understand what the rules are actually doing. It requires repeatedly opening and closing each rule to view their content, making modification and maintenance challenging. (Imagine having a dense web of numerous rules. Moreover, as the number of rules increases, system responsiveness slows down).
Non-Replicable Rules:During development, similar business logic is inevitable, and the common practice is to copy and then adjust existing rules. However, K2 surprisingly does not support this! Imagine having many similar scenarios, each requiring the setup of dozens of similar rules again from scratch!
Any updates on this? It has been 2 years now, and no talks of implementing this has yet to be found @nintex
Agree with others, this feature is very mandatory and can save development time
Necessary feature, the availability of this feature enhance the productivity and save a lot of time.
Really, really need this.