Thanks Suraj for your inputs. I have created a component and calling that from template.html. Now, getting the current resource and fetching the child nodes.

Hi All, Thanks for your inputs. Yes, as everyone told I was unable to unlock page by superuser (eventhough If i give all the permission). So, using admin session I achieved. Thank Again

Since I have used workflow, Using workflow session I'm able to lock and unlock the page. (page.lock() && page.unlock()). Thanks all for your valuable inputs.

Hi Arun, I'm using workflow package. Inside the worlfow package I have my page url's. So, in the workflow model, I will get the workflow package URL as a payload path. This link https://helpx.adobe.com/experience-manager/kb/workflow-lock-unlock-not-working-aem63.html is to lock and unlock the payloa...

Hi Gaurav - can you share the above 2 links again. it's redirected to https://community.adobe.com/ even if signed in..

Thanks Varun for your help. I have used workflow package and achieve it. Initially, I was about to go with Launcher. But, customer wants to trigger the workflow for bulk request. For Instance, if content author worked in 25 pages, then he wants to trigger the workflow once and that should be take ca...

Hi All, Thank you very much for your inputs. The has been fixed and it was due to the permission issue which I given for service user.Regards,Vijay

Hi Arun,The state of the bundle is in active and the service is also in active. That's why I could able to see the logs which I put in that service.If the issue with archtype or dependencies then it should not work in local as well right? but for me it is working in local. Issue is only wth the dev ...

Hi Arun Patidar​,I have changed the code as you suggested (using repository session). But still I'm facing the same issue. The updated code is working fine in my local instance but not in dev. Also I' having some existing projects in dev environment where I'm using the same logic (get all locale bas...

Hi Puzanovs,Thanks for your input and the issue has been fixed now.The way of calling the service (I18nTenantRuntimeExtension) should be something different in AEM 6.4.Below are the fix:Removed felix annotations and placed OSGI annotations.Added org.apache.sling.scripting.sightly.compiler.java depen...