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.

Pickers should remember their last location and start from there

Avatar

Level 2

6/21/24

Request for Feature Enhancement (RFE) Summary: Pickers must remember their last location and start from there 
Use-case: Our editors create pages on specific topics and upload assets related to that topic. They very often upload the assets into the same folder to have everything in one place. Then they start to build a page and add the assets to the page. 
Current/Experienced Behavior:

For the first image asset:

 1. Drags in Image Component

2. Opens asset picker

3. Navigates all the way to the sub-sub-sub-sub folder

4. Selects asset

5. Confirm

6. Confirm

 

For the second image asset:

1. Drags in Image Component

2. Opens asset picker

3. Navigates all the way to the sub-sub-sub-sub folder

4. Selects asset

5. Confirm

6. Confirm

 

... repeat for each asset

Improved/Expected Behavior:

For the first image asset:

 

1. Drags in Image Component

2. Opens asset picker

3. Navigates all the way to the sub-sub-sub-sub folder

4. Selects asset

5. Confirm

6. Confirm

 

For the second image asset:

1. Drags in Image Component

2. Opens asset picker

4. Selects asset

5. Confirm

6. Confirm

 

... repeat for each asset

 

So, pickers should remember their last location and start from there, at least for the current session.

Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS
Customer-name/Organization name: VERLAG DES ÖGB GMBH
Screenshot (if applicable):  
Code package (if applicable):  
1 Comment

Avatar

Administrator

7/17/24

@martinkastler 

Thanks for proposing this idea.
This has been reported to the engineering under the internal reference SITES-23489. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira status.
Status changed to: Investigating