Template Availability -  AEM offers multiple properties to control the templates allowed under Sites. However, combining them can lead to very complex rules that are difficult to track and manage. Therefore, Adobe recommends that you start simple, by defining: only the cq:allowedTemplates property ...

First this looks to me as a weird requirement. Never heard of similar requirement in past. However, even if you need to do it then I am assuming you are only talking about custom workflows.  2 ways I can think of: 1. In workflow process/model, you can define and add a condition to not execute this w...

Are you sure that your bundle has been built correctly? You should validate the MANIFEST.MF file contains a proper SymbolicName header. You can also refer below link to define the symbolic name of OSGI bundle. http://wiki.osgi.org/wiki/Bundle-SymbolicName   Also, you should check for - in pom.xml's ...

Couple of things you should do: 1. Check with some other experience fragment whether you are getting same issue or not. 2. Always, refer logs for any issues and if you don't find any relevant information in logs then enable the debug logs and then analyze.  I will hope, one of these step will help y...

It is always better to first refer to logs for any issues. And if you don't find relevant information then I would suggest you to enable the debug logs and then analyze the logs during the operation. I am sure this will definitely give you clue what is incorrect. Also, while asking any question, it ...

I think you should refer this - https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/notifications.htmlthere are ways by which you can change the setting and email notifications can be sent.Also, using webhooks on Adobe I/O you can integra...

As far as I remember, it is not available OOTB. You can certainly do the customization for the same in the template.

I would suggest first you should look at the logs and try to find what is causing the issue. Any exception or error may be due to configuration issue, special character issue etc. Logs will give you direction to find the root cause. If you dont see anything on logs then try to enable it on Debug mod...

I think NodeType you mentioned is dam:AssetContent which means its not metadata. Generally this node contains only few fields like name, parentPath, processed etc. You may be need to enable the launcher on your custom Metadata - In that case few configurations needs to be modified:NodeType - nt:unst...

@sriram_1 please confirm whether it solves the issue or not?