We have QA publish pages when we try to access them its going to AEM login page first. Its working fine on other env. what could be the reason

Hello @CarlosDa2 ,There are several probabilities for this issues 403 means its forbidden, so we have CSFR filter , CORS, Permission, Dispatcher rules, all this can leads to this issue 1. CSFR filter is blocking all the unauthorized POST req. so you need to whitelist your servlet in Adobe Granite CS...

Request for Feature Enhancement (RFE) Summary:To have the ability to undo the move or deleted assets/pages Use-case:Sometimes we want to revert the bulk moved or deleted assets or pages, but we don't have any recycle bin or undo changes optionCurrent/Experienced Behavior:No option to get back the de...

@harishred There is no straight way to do it, May be we can ask for this new feature @kautuk_sahni Temporary Solution for this -If you have time stamp then it will be a good start point. you need to check logs for this timeframe. THere is one sling job triggers for move operation com/adobe/cq/dam/as...

@pabloram23 Instead of relying on the asset name, the batch set assignment can be made dynamically based on the metadata property array values. This can be done using a custom workflow or a service that iterates through your assets and checks for the matching metadata property values.You need a cust...

Hello @elw23 , if the Asset name is the same then the part of it should not change, Please confirm on that. That is correct if you replace then it will treat it as a new asset only, its not the loophole but its the same behavior in any of our systems even in our windows system as well.If you already...

Hello @AliSyed1, this is the exact requirement we had, We need to overlay the required node. In our case its quickPublish button, so we need to overlay it first and we need to add the  granite:rendercondition ndoe here. And in it we need to add the required property which will specify the allowed or...

@PovEim There is one feature which checks the duplicate Asset Detection by checking SHA 1 checksum value.Its the popup that appears when user upload the same asset even if the filename is different.  Check this document https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/cont...

Sure, Let us know if it helps 

Hello @JakubIz, When we are migrating from JWT to OAuth for adobe events integration this involves updating our authentication method. Adobe Cloud services manage most of the integration automatically, you may need to update any service accounts/tokens/permissions related to your events providers to...