Customize Menu Options for AEM Cloud not visible in Assets Essentials Console | Community
Skip to main content
Rohan_Garg
Community Advisor
Rohan_GargCommunity Advisor
Community Advisor
May 15, 2024
Investigating

Customize Menu Options for AEM Cloud not visible in Assets Essentials Console

  • May 15, 2024
  • 2 replies
  • 565 views
Request for Feature Enhancement (RFE) Summary: Custom Metadata Schemas and fields developed in AEMaaCS should be visible in Assets Essential console as well.
Use-case:

Currently we are not able to see any of the custom buttons or menu along with the metadata schemas designed in AEM in the Assets Essential console.
Current/Experienced Behavior: Any custom metadata schema and fields developed in AEM Assets Cloud console are not visible in the Assets Essential console.
Improved/Expected Behavior: Any custom metadata schema and fields developed in AEM Assets Cloud console should be visible in the Assets Essential console.
Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS
Customer-name/Organization name: Credera (Formerly TA Digital)
Screenshot (if applicable): N.A
Code package (if applicable): N.A


Original Query Link - AEM Assets Essentials (Experience Manager Assets) vs Experience Manager - Custom UI Handling

    2 replies

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    May 22, 2024

    @rohan_garg 

    Thanks for proposing this idea
    This has been reported to the engineering under the internal reference ASSETS-39115. 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.
    Kautuk Sahni
    E
    Adobe Employee
    ehahn061Adobe Employee
    Adobe Employee
    May 23, 2024

    @rohan_garg There are two different topics in the request: (1) ability to display custom menu buttons, and (2) ability to display custom property types used in the metadata form

     

    for #2 related to metadata properties: Currently the Admin needs to go and configure the metadata form in the Assets View. Each property should map to the same node as in Touch UI. Some customers are leveraging the Assets View as a lighter weight experience and are configuring the metadata form to include a subset of the properties used in Touch. 

     

    If there are missing property types, could you please elaborate? If you built out custom form fields in Touch where there was a new UI element or overlay, please let me know as these may be something we look to productize in the future. 

    Terms & ConditionsAccessibility statement

    Loading footer...