AEMaaCS - Legacy User Interface - Classic Dialog

[Prashardan]

Hi Team

I am migrating from AEM on-prem to AEM cloud, when I run BPA on my author instance got below violations as critical. 

• Legacy Classic UI dialogs were detected. They must be modernized to work in AEM as a Cloud Service.

  /apps/accelerator/sitemap/components/depthPriority/dialog	A legacy Classic UI dialog was found at /apps/accelerator/sitemap/components/depthPriority/dialog. It is deprecated and should be modernized. It will not work in AEM as a Cloud Service.
  /apps/accelerator/sitemap/components/images/dialog	A legacy Classic UI dialog was found at /apps/accelerator/sitemap/components/images/dialog. It is deprecated and should be modernized. It will not work in AEM as a Cloud Service.
  /apps/accelerator/sitemap/components/lastModified/dialog	A legacy Classic UI dialog was found at /apps/accelerator/sitemap/components/lastModified/dialog. It is deprecated and should be modernized. It will not work in AEM as a Cloud Service.
  /apps/accelerator/sitemap/components/location/dialog	A legacy Classic UI dialog was found at /apps/accelerator/sitemap/components/location/dialog. It is deprecated and should be modernized. It will not work in AEM as a Cloud Service.
  /apps/accelerator/sitemap/components/news/dialog	A legacy Classic UI dialog was found at /apps/accelerator/sitemap/components/news/dialog. It is deprecated and should be modernized. It will not work in AEM as a Cloud Service.

  These components are related to sitemap and not used on any pages.
• Kindly advise what action is required to remove this critical violations

[Rohit_Utreja · Accepted solution]

@Prashardan 

You can convert these dialogs to touch UI dialogs. AEM modernisation tool can be utilised for the same.

Please find below a link for your reference.

https://experienceleague.adobe.com/docs/experience-manager-64/developing/devtools/modernization-tool...

[Jineet_Vora]

@Prashardan - If this sitemap components are not supposed to be migrated to AEMaaCS then it can be ignored from the report. If they are supposed to be migrated, then these needs to be mordernized using Touch UI dialog.

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/migration-journey/r...

[Prince_Shivhare]

Hi @Prashardan ,

AEM Cloud Support - As classic ui is not supported in AEM cloud and with reports as well we can understand that the components which are in classic should be converted to touch UI cq:dialog if you want to use it on any page.

Component deletion - As you are stating if these components are not used anywhere on the page then with the approval and discussion with the team you can think of deleting it. please make sure to check the references if there are any using the query builder console. However, if you want to use it in the AEM cloud, then you can use conversion tools and use it.

Cloud Reports - Critical AEM Cloud reports can not be ignored but as this is not related to security or something else then you can think of overriding it till the time you get the approach about what to do.

Thanks,

[Prashardan]

Thanks for your reply @Rohit_Utreja  @Prince_Shivhare @Jineet_Vora 

I have question related to the same. I have some acs-commons components which are using classic dialog.

Is it like if I want these acs-commons components on cloud I need to do modernize or do we have any other option on AEMaaCS.

Thanks in Advance.