Hide AEM Component Touch UI dialog editor field using AEM Render Condition | AEM Community Blog Seeding | Community
Skip to main content
kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
May 30, 2023

Hide AEM Component Touch UI dialog editor field using AEM Render Condition | AEM Community Blog Seeding

  • May 30, 2023
  • 1 reply
  • 515 views

BlogImage.jpg

Hide AEM Component Touch UI dialog editor field using AEM Render Condition by Debal Das

Abstract

Recently I got the opportunity to explore AEM render condition and being AEM developer I really enjoyed this feature.

I have explored AEM render condition with built-in rendercondition and Custom rendercondition both.

I will talk about both with built-in rendercondition and Custom rendercondition with one simple use case here.

Let’s consider I have one component named: Add Color in Your Title and it’s dialog editor fields

Read Full Blog

Hide AEM Component Touch UI dialog editor field using AEM Render Condition

Q&A

Please use this thread to ask the related questions.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    1 reply

    Rohan_Garg
    Community Advisor
    Rohan_GargCommunity Advisor
    Community Advisor
    July 5, 2023

    Is there any OTB render condition for the use case where a particular action say "Annotate" assets should be restricted to a particular user group?

    /libs/granite/ui/components/coral/foundation/renderconditions/privilege seems to be path based rather than group name.

    Or do we need to create a custom render condition for this?

    Terms & ConditionsAccessibility statement

    Loading footer...