I did have a chance to review Connor’s suggestions and they were helpful in furthering my understanding, so I appreciated that. I was picturing scenarios where you might wish to tag cards for two different scenarios:
Inside of the FLO itself: This could enable tagging just the cards that interact with a specific external system, for example. That way if you were to show cards with just that tag the rest would be hidden from view (hiding functions and non-related action cards). Another aspect of this might allow you to condense the view so that you could quickly make mapping assignments to related cards that don’t sit next to each other on a large/complex FLO.
Outside of the FLO: This angle maybe would have more to do with searching, like being able to use a common tag across FLOs, and as your total number of FLOs grow you can scale maintenance by being able to quickly search and find FLOs that contain cards with common tags.
Anyway, just some thoughts. I wasn’t really looking for a current solution or workaround, just trying to contribute to the conversation as I get involved with the Azuqua community. I did find Connor’s notes about grouping functions/actions inside of a conditional card helpful, although one limitation in my mind is that you can’t collapse it in the view once you are done working on/configuring that grouping of cards.
I appreciate you reaching out. Again, I’m new to the community and the product in general so take my thoughts with a grain of salt.