Hi @samsundar23!Personally, I am not aware of any general issue with AEMs SP16 that could cause NullPointerExceptions in scriptlets.In addition, the provided information is unfortunately not enough to provide specific advise on how to fix the issue.My recommendation is to perform a more detailed ana...

Hi @shubham_naik! To identify customisations and overlays of the AEM product, it's required to perform an analysis of your projects source code. Examples of things to look for:Does your project setup (package filters) cover any area that is usually reserved for product code, such as /libs? Does your...

Hi @lasher1668!The linked thread actually mentions two approaches to hide OOTB workflows:Workflow:WCM tag - this will apply globally and for all usersSetting ACLs for specific workflows and groupsYou are referring to the first approach which - from your request - does not fit to your requirement to ...

Hi @Vani1012!Could you please provide some details on where the wrong translation can be found?Is that within the AEM UI (product related)? Is it withing your custom application? Or part of translated content? For a product related issue, please open a support ticket with customer care (through Admi...

Hi @pkumarp1!The error looks like it's very likely to be caused by a wrong Java version being used to start the AEM process.The supported versions can be found on the Technical Requirements documentation [1,2] (AEM 6.4: Oracle Java SE 8 JDK - 64bit; various options for AEM 6.5). Please also check fo...

Hi @bhagchand!As mentioned by @Sady_Rifat and @ShaileshBassi already, there are dedicated Access Control Lists (ACLs) available for replication. Please refer to the documentation around User Administration [1] and check for the "Replicate" action. In general, ACLs can be managed through the authorin...

Good to hear that the issue has been resolved.   As I mentioned in my initial reply, domain related configurations are definitely one thing that might influence the behavior on multiple levels. A couple of potential areas where domains might influence request serving are: Dispatcher configuration, e...

Hi @Rohan_Garg!   My first recommendation would be to continue analysis to identify the component in the stack that is causing the issue. First, please double check on the log files to identify where the rewriting is happening. This could potentially be handled on Dispatcher side (e. g. through rewr...

Hi @Rohan_Garg! You're totally right: it's absolutely not an option to leave the dispatcher without any filtering. Please don't do that! And yes, Cloud Managers quality gates will check the filter setup against best practices and the security check lists to ensure that this does not happen.   The id...

Hi @Rohan_Garg! If the request is properly served from the publish instance but returning 404 when requested through dispatcher, this is most likely an issue with the filter rules configured on dispatcher.   This can be verified by e. g. removing all filters (setting to allow all) and double checkin...