Customize Assets Console | Community
Skip to main content
M
mmouraam
New Member
August 4, 2022
Solved

Customize Assets Console

  • August 4, 2022
  • 1 reply
  • 1048 views

I'm working on a demand that needs a column to be added in the assets console of AEM as a Cloud Service.

This column needs to present the data of a specific field of the content fragments in folder. (jcr:content/data/master/my_field)

 

I got it by doing an overlay of availablecolumns and reorder.jsp in my local SDK.

- /apps/dam/gui/content/commons/availablecolumns

- /apps/dam/gui/coral/components/admin/contentrenderer/row/common/reorder.jsp

 

but working with jsp is no longer recommended and maybe not even supported.

 

There is another way to achieve this goal?

Maybe using clientlibs or PageInfoProviders. And how? Someone has an example?

 

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 lukasz-m

Hi @mmouraam,

The approach you have described is correct and is aligned with Adobe recommendations. Overlay and/or PageInfoProvider is the way to go:

In terms of jsp usage, you are right it is not recommended. However this rule is not valid in case of overlay of existing functionalities. In that case it is correct to use jsp in that scenario, assuming original functionality that you are overlaying is using jsp - it will not be possible to implement proper overlay other ways. There are lot of OOTB functionalities written that is using jsp, I do not think support of jsp will be discontinued soon.

Regarding PageInfoProvider examples, here are some:

1 reply

lukasz-m
Community Advisor
lukasz-mCommunity AdvisorAccepted solution
Community Advisor
August 7, 2022

Hi @mmouraam,

The approach you have described is correct and is aligned with Adobe recommendations. Overlay and/or PageInfoProvider is the way to go:

In terms of jsp usage, you are right it is not recommended. However this rule is not valid in case of overlay of existing functionalities. In that case it is correct to use jsp in that scenario, assuming original functionality that you are overlaying is using jsp - it will not be possible to implement proper overlay other ways. There are lot of OOTB functionalities written that is using jsp, I do not think support of jsp will be discontinued soon.

Regarding PageInfoProvider examples, here are some:

    Terms & ConditionsAccessibility statement

    Loading footer...