Our Nintex Automation Cloud tenant has a million workflows. Including a bunch of component workflows.
If this were C++, C# or Java, I’d have different namespaces (or packages), group my classes into different source directories, and define my class methods into different class files.
The only mechanism I could find for “reducing clutter” in NAC workflows is “tags” and “filters”.
Q1: Is there any better way to “reduce clutter” than to declare (ad hoc) “tags”, and manually “filter” on them?
Q2: Is there any way to separate different workflows to different “groups” (so everything doesn’t all display all together on the “All workflows” page)?
Q3: is there any way to define a “default filter” that’s active whenever a user logs on to the NAC tenant (so they don’t have to manually choose filters)?
Thank you in advance!
