@HuiDeShao Please elaborate on your query.

@KaibalyaJena_123 You can overlay OOTB Save & Close Button and add your custom button. On click event of this button, Pop us message can be configured. UI can be handled by Front end logic via JS.For reference on how to overlay:https://experienceleague.adobe.com/docs/experience-manager-65/developing...

@Himanshu_Jain Below page will give you acs version compatibility Metrics and in the same page, there is a section for AEMaaCS Feature Incompatibility, which should hopefully answer your queryhttps://adobe-consulting-services.github.io/acs-aem-commons/pages/compatibility.htmlhttps://adobe-consulting...

Hi @KaibalyaJena_123 Can you please add the screen, where you want to add the pop ups.

@AEMLearner-1989 Please follow below link to understand on how to use ui front module:https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/full-stack/clientlibs.html?lang=en 

@Abie I am assuming that you are not using Cloud version of AEM, where in Binary Processing is not recommended at AEM end. This should be deployed via Microservices. On Non-Cloud version, processing binaries is still possible.Coming back to your query, I see various plugins available to process TIFF...

@goyalkritika In my opinion create a service class and put in your navigationlogic methods into it. This service can be referenced in both your servlet and utility class.Adding a commonly used module in a Servlet, totally defeats the purpose of having services. 

@Adilos-Cantuerk Pretty much sure, that there is no such provision available OOTB. However, you can create a custom utility to deploy the above logic reading from similar CSV file as being uploaded for Bulk Metadata Import. But Bulk Metadata Import and Custom utility would work in separate threads.

@Abie Can you please explain how you are able to access layers for your PSD files. As far as I know, there is no OOTB way to achieve it. Is there any custom solution in play?

@mbrennan Assuming you have also cloned/copied the default metadata schema and converted into your own custom metadata schema. You would just have to rename the review status field property from dam:status to your own custom property and write a Workflow launcher that triggers Group1 Launch Approval...