Hi @AmitSi18 ,
In Granite RenderCondition (used in AEM dialogs to conditionally show/hide fields), the underlying implementation uses Sling Models, meaning you have access to all Sling injectable objects that apply in the context of a dialog rendering request.
Complete list of OOTB objects that you can inject into a Granite RenderCondition class using Sling Models:
1. SlingHttpServletRequest (@Self)
- Current HTTP request object.
- Use it to access request parameters, headers, attributes, etc.
2. Resource (@Self)
- The resource node for the dialog field.
- You can read properties directly from this node.
3. ValueMap (@Via("resource") @ValueMapValue)
- Used to get dialog-specific properties like any custom configurations defined in the dialog node.
4. ResourceResolver (@Inject)
- Allows you to access the repository, traverse resources, etc.
5. RequestPathInfo (@Inject)
- Helps you extract selectors, suffix, extension, etc. from the URL.
6. Page (@ScriptVariable)
- The current page in context.
- Helpful to check path, template, or hierarchy-based conditions.
7. PageManager (@ScriptVariable)
- Used to work with pages — get parent, children, etc.
8. WCMMode (@ScriptVariable)
- Tells you the current authoring mode (EDIT, PREVIEW, etc.).
- Useful when you want to show/hide a field only in authoring mode.
9. ComponentContext (@ScriptVariable)
- Gives context about the component being rendered.
10. SlingBindings (@Inject)
- Contains all the request bindings like currentNode, resource, pageManager, etc.
- You can access the whole context via bindings.
11. Authorizable (@Inject)
- Represents the current user.
- Use it if you want to show/hide fields based on user roles or groups.
12. Session (@Inject)
- The JCR session associated with the request.
- Usually not required for simple conditions, but available if needed.
Example: Custom RenderCondition Java Class
@Model(adaptables = SlingHttpServletRequest.class)
public class MyRenderCondition implements RenderCondition {
@Self
private SlingHttpServletRequest request;
@Self
private Resource resource;
@Inject
private RequestPathInfo requestPathInfo;
@ScriptVariable
private Page currentPage;
@ScriptVariable
private WCMMode wcmMode;
private RenderCondition condition;
@PostConstruct
protected void init() {
boolean show = currentPage.getPath().startsWith("/content/mysite") &&
wcmMode == WCMMode.EDIT &&
requestPathInfo.getSelectorString() != null;
condition = new SimpleRenderCondition(show);
}
@Override
public boolean check() {
return condition.check();
}
}
If you want to debug or log all available objects, you can use:
Bindings bindings = (Bindings) request.getAttribute(SlingBindings.class.getName());
bindings.keySet().forEach(k -> log.info("Binding key: {}", k));
This helps you discover any other available context variables dynamically during request.
Regards,
Amit
