Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

One click to expand the entire parent node in crxde

Avatar

8/25/23

Request for Feature Enhancement (RFE) Summary:

I propose adobe to include an option to expand the entire parent node along with its child nodes with a single click. Because, sometimes it feels annoying to click "+" on each node to see the final child node(leaf node) if it has a multiple child nodes.

 

Although the idea sounds simple, but it would be useful sometimes when people in a hurry to check something.

 

Use-case:  
Current/Experienced Behavior: For example - cq: dialog, we have to expand it node by node until we reach the child node.
Improved/Expected Behavior: My idea - When I right click on a node - a new option called "Expand Entire Node" should be implemented such that once I click on it, it would show/expand it till the last child node.
Environment Details (AEM version/service pack, any other specifics if applicable): I think this feature is not present in any version of AEM it seems.
Customer-name/Organization name: Adobe Experience Manager
Screenshot (if applicable): Santhosh_Talepalle_0-1692998113391.png

 

Code package (if applicable):  

 

Guys - What's your view on this idea???

4 Comments

Avatar

Community Advisor

8/25/23

@Santhosh_Talepalle  The only issue that i see with this idea is that it can become a very performance intensive operation in case of real life scenarios.

consider a tree structure like this /content/a/b/c.

Now lets say we want to invoke this operation at node a.

Now, worst case, if you go by Adobe's recommendation (bdw, i have seen real cases where we had 20k immediate child nodes under a single node), you can have a maximum of 1000 immediate nodes before which the JCR query performance really starts taking a hit. Lets assume we have 2 levels under any node from this tree to traverse.

child nodes of just under node c = 1000*1000. It is a geometric progression sequence and you can imagine what this number will look like at node a. I have not even accounted for the number of properties each of those nodes will have and what kind of values (in terms of size) each of those properties will have.

 

@kautuk_sahni , Perhaps Can we introduce an oak constraint that fails an operation that tries to create more than 1000 immediate children of a jcr node. Right now , this exists just as recommendation from adobe and is not strictly enforced. I have seen some bad implementations that led to creation of more than 20k immediate children and down the line , caused a great deal of performance issues like jcr queries failing, workflows getting stuck etc. Let me know if you want me to log this as a separate idea.

 

Avatar

8/25/23

@Harwinder-singh  - Thanks for addressing the issue that will be encountered with this idea. I haven't thought of in a broad scale about this since i wanted this feature mostly while checking the component specific needs. 

May be Adobe can do one thing that, it may limit the nodes count while expanding . For ex:- it can expand either 100 or 200 nodes. But again this would be an incomplete implementation for AEM. 

Avatar

Administrator

9/7/23

@Santhosh_Talepalle 

Thanks for proposing this idea
 
This has been reported to the engineering under the internal reference SITES-15878. 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.
//Adding note from @Harwinder-singh to the Jira.
Status changed to: New

Avatar

Administrator

9/8/23

@Santhosh_Talepalle, Sharing the reply from the PM team, There are no scheduled improvements or updates planned for the CRX/DE UI in the roadmap priority as of now. 

Status changed to: Declined