Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

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):  
3 Comments

Avatar

Employee Advisor

23-06-2021

Hi @mikeetiuPH 

 

Thanks for proposing the idea. This request has been raised to the product team via the internal request CQ-4326979. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

Status changed to: Investigating