This feature allows you to use defined metadata field values to make assets visible to the user. This is part of what many of us need to secure assets in the Author instance. What is equally important is the ability to restrict certain groups from editing specific metadata fields. Has anyone done th...

Hi @AmitVishwakarma, Thanks for this information. I wonder if there is some documentation that shows everything that is possible to configure for the metadata schema within the JSON file. I have found one link in the Experience League that sheds a very small amount of light on the subject:https://ex...

To use these configuration files as part of a metadata schema form's field configuration you will need to take a part of the full path to use in JSON Path field:ui.apps/src/main/content/jcr_root/apps/<your-project>/config/metadata-config.json I have highlighted above the section to use so that it is...

I finally figured out how to complete this task. The steps once understood are fairly straight forward, I just was not able to find information in the documentation as easily as I had hoped.In the end I used these steps:Place JSON Files in the Project:Typically, JSON files used for configuration are...

We are using OOTB AEM Experience Manager Cloud and want to keep things as close to OOTB as possible. To this end we are attempting to use the functions of the existing application rather than add ACS AEM Commons.As to the commit, push and build of the project with the JSON files added to the reposit...

I have written a Python script that converts metadata configuration captured in a MindMap file into JSON files that can be referenced in the JSON Path data entry box found in the Settings for a metadata field. The content of the JSON file has the format below:{    "jcr:primaryType": "nt:unstructured...