Hiding Granite UI Resource Dynamically

Granite UI offers two ways of hiding the resource dynamically.
  • FilteringResourceWrapper (granite:hide)
  • RenderCondition (granite:rendercondition)
UseCase: To hide/filter a resource from being rendered based on some custom conditions.
Understanding the differences in terms of usage:

granite:hide
granite:rendercondition
Decision making logic/condition is defined using Expression Language(EL).
Decision making logic/condition is defined in a component ie. Separate rendercondition component will hold the logic.
Supported Variables/functions in EL (for Granite UI resource) are available here OOB rendercondition components are available here. 
Custom variable can also be registered using ExpressionCustomizer. One such variable is cqDesign for fetching the design properties as we would do with currrentDesign global object.
(OOB core components uses this variable in EL- ${cqDesign.customproperty})		 Custom rendercondition component can be created based on our requirement.
Usage: Property named "granite:hide" is to be created with value being EL on the resource to be filtered Node named "granite:rendercondition" or "rendercondition" is to be created under the resource to be filtered.
Properties for this node being "sling:resourceType" with the value as rendercondition component or custom component's path
Ex: Widely used in OOB core components to control dialog fields based on design/policy configuration of that component.
Condition can be controlled at property level itself making use of cqDesign custom variable. Hence EL is preferred in this case.		 Ex: In Page selection -> action bar -> Create -> Workflow option will be available/should be rendered for those who have access to /etc/workflow/models.
This condition has to be implemented making use of AccessControlManager API on specific path. Hence rendercondition is preferred for this use case.

Specific example on each of this is to be covered in a separate post for better clarity.

Reference: Adobe helpx links on Granite UI

Comments

  1. Astrum Granite | Kitchen Worktops and CountertopsSeptember 6, 2020 at 11:36 PM

    When planning for a new kitchen, it’s a smart move to choose your worktops and then build from there.
    Astrum Granite houses a broad selection of Kitchen Worktops, Quartz Countertops & Kitchen Countertops. We offer vast range of Granite Worktops, Quartz Countertops, Marble Kitchen Worktops

    The large selection of options can be daunting, so if you need any assistance or advice, our team have years of experience and the knowledge to steer you in the right direction, so don't be afraid to give us a call to get Online Quote.

    ReplyDelete

Post a Comment

Popular posts from this blog

Embedding Third party dependency/OSGi bundle in AEM application hosted in AEMasCS

Image
This post illustrate the ways of embedding third party dependency in AEM maven project. Steps are mentioned considering the project structure to be followed for AEMasCS while the same can be followed for classic versions too.  Before we begin, I would like to explain the scenario of including a dependency in our AEM maven project.  When we would like to make use of an API that is not already available in our project, we look for that in maven-central repository and specify the dependency in main pom.xml and desired module's pom.xml file. (Lets say, AWS S3 Java SDK V2 dependency) Upon updating the project in the IDE, we would see our class files (making use of those APIs) are compiled/build successfully without any errors.  Now, in the context of AEM/OSGi environment, when the same package and hence the bundle is deployed to AEM instance, dependencies that we added new might not be resolved/available in the OSGi as a bundle. Something like the below This indicates that the added dep
Read more

OSGI Factory Configuration implementation

OSGI Factory configuration is used to have many instances of an OSGI config (represented/identified via an identifier) for the single OSGI service/PID. Most often used OOB Factory configurations for example: Logger Factory/writer configuration (for log statements) Service user Mapper service Amendment (for using service resource resolver in projects) Few sample real time use case for the need of OSGI factory config: For multi tenant projects, if we have generic service used across tenants with properties/attributes specific to tenant. For single tenant, generic service targeting all locales with properties/attributes specific to locale. (where generic service -> holds logic in the lines of calling third party service for retrieving/updating information.) Implementation: ( In terms of OSGI R6 annotations ): Create Object Class Definition(OCD) defining desired properties for the OSGI service. - OSGIFactoryConfigOCD.java OSGI Service/Factory service to retrieve
Read more

Creation of Template Types for Editable templates

Image
In this post, we will create templates types which is the base for creating editable templates. Before getting to the subject directly, have added an introduction about templates in general. Template is the base for creating pages. Starting AEM 6.2, we have categorisation for templates - Static and Editable templates. Static templates :  This has been available for several versions of AEM/CQ Created using "Create Template" option with base page component as resourceType (which is responsible for rendering the page structure).  Template ( base page component as resourceType ) -> Page This cannot be edited as such. Since it just holds a reference to base page component, any changes to the page (other than authorable components), would need a change in base page component which is ultimately a work of developer. (calls for a code change) Allowed components are configured using Design mode (list being saved to etc/designs/projectfolder/templatename/jcr:content)
Read more