Bulk edit not supported warning after select all | Community
Skip to main content
New Participant
January 16, 2023
Declined

Bulk edit not supported warning after select all

  • January 16, 2023
  • 2 replies
  • 485 views
Request for Feature Enhancement (RFE) Summary: Related Case #E-000797571
Use-case: We noticed recently the new warning message added to AEM bulk edit scenario, where user attempt to “Select all” and edit these sub-pages in separate tabs. The warning message says that “Bulk action not supported, The selected action Edit(e) will only have effect X selected items currently loaded…”. As we understand, the justification for that warning message is to let user know that not all sub pages might have been lazy-loaded, and that’s fine. That also explains why the massage doesn’t need to appear when pages have been selected manually. The point is that the mentioned logic might be confusing when there are only few sub-pages to be selected by “select all”. In that case lazy logic is not the case and user can be sure that “select all” picks all the sub pages we have on the screen. Please consider extending that logic, because our customers feels uncomfortable with new behavior and confusing warning. (More detail you can find in thread for Case #E-000797571)
Current/Experienced Behavior: Warning message for few pages selected by "select all"
Improved/Expected Behavior: For the scenario when only few sub pages exist, warning message is not necessary, even if pages were selected by "select all" 
Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager (6.5.15.0)
Customer-name/Organization name: Wundenmanthompson's customer
Screenshot (if applicable):  
Code package (if applicable):  

2 replies

kautuk_sahni
Employee
January 30, 2023

@pt6 , Requet is more closely aligned to Classic UI. Classic UI is deprecated, i.e no more feature enhancement support for it. 

Kautuk Sahni
kautuk_sahni
Employee
January 25, 2023

@pt6 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-11208. 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.

Kautuk Sahni