New Assets UI (Cloud Service Assets View) | Community
Skip to main content
Adobe Employee
September 29, 2023
Solved

New Assets UI (Cloud Service Assets View)

  • September 29, 2023
  • 4 replies
  • 1594 views

 Is there a documentation around the limitations of New assets UI (Cloud Service) compared to the old one. Any documentation or key pointers around this would help. Customer team is looking to move to the Asset View ( New UI ) and are looking for limitations in the New UI.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Himanshu_Phulara

Thanks everyone for responding.
Sharing my findings on this below, in case anyone else is interested: 

As per the current scenario, the New Assets UI ( Assets View) is not intended to replace the Admin View(Standard Touch UI Assets), as it supports only the below use cases. 

Use cases supported by Assets View.
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/assets-view/get-started-assets-view.html?lang=en#use-cases

For any admin related tasks we would still need to use the Admin view ( Standard Touch UI Assets ) and same goes with any use case not listed in the above documentation.

 

 

4 replies

Adilos-Cantuerk
Community Advisor
Community Advisor
October 2, 2023
kautuk_sahni
Community Manager
Community Manager
October 4, 2023

@himanshu_phulara I am unaware of this, Related resources that may be helpful:

Request you to create this in the Ideas tab, I'll share this with the Documentation team PM.

Kautuk Sahni
Adobe Employee
October 4, 2023

Some limitations are listed below:

New asset Ui search filter form is not customisable yet . Use default search filters only , can't add custom metadata filters.

-Default landing page is not configurable yet (may be in roadmap)

-configuration (Branding/text changes) of search page(text/ui) is not possible tet

- user permissions and groups need to be managed separately.It won't respect aem standard author ACL

-search is little different than regular aem search , GQL search , operator search not supported.

-metadata schema needs to be managed seperatly for new ui, can't be managed like standard author.

- does not support code deployment

 

Himanshu_PhularaAdobe EmployeeAuthorAccepted solution
Adobe Employee
October 4, 2023

Thanks everyone for responding.
Sharing my findings on this below, in case anyone else is interested: 

As per the current scenario, the New Assets UI ( Assets View) is not intended to replace the Admin View(Standard Touch UI Assets), as it supports only the below use cases. 

Use cases supported by Assets View.
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/assets-view/get-started-assets-view.html?lang=en#use-cases

For any admin related tasks we would still need to use the Admin view ( Standard Touch UI Assets ) and same goes with any use case not listed in the above documentation.