Comment

Custom Tag predicates cannot be permanently configured to only pull specific namespaces

Avatar

Level 4

09-06-2021

Request for Feature Enhancement (RFE) Summary: Custom Tag predicates cannot be permanently configured to only pull specific namespaces
Use-case: We want to have multiple tag fields not just one
Current/Experienced Behavior:

AEM has an out-of-the-box tag field. There are certain instances wherein stakeholders would like custom tag fields configured for certain tag groups. E.g. A tag field for “Content Type”, “Target Country(ies), “Campaign”. In the schema editor, there is no out-of-the-box way to limit what namespace is going to be displayed on a certain tag predicate. With that, even if there are multiple tag fields created, all of them will display the same set of tags or tag groups

Improved/Expected Behavior: Have the ability to point tags fields to a specific namespace
Environment Details (AEM version/service pack, any other specifics if applicable): AEMAaCS
Customer-name/Organization name:  
Screenshot (if applicable):  
Code package (if applicable):