@Vani1012  Do you see any errors in backend or console?and I believe you are part of dam-users group and permissions have been given to group

This doesn't work if we author this under welcome page i.e., demo1 page

@vikas3 If you are OK to use javascript use-api "use strict"; use(function () { var resourceResolver = resource.getResourceResolver(); var welcomeRes = resourceResolver.getResource('/content/first-demo/us/en/welcome'); var data = {}; data.page = pageManager.getContainingPage(welcomeRes)...

@edith_viddi you can have a look at the guide related to ADO-E134https://express.adobe.com/page/9dRc3LE9wFkWN/Both 116 and 134 should be of same difficulty level

Hi @edith_viddi  ADO-E116 is no longer valid and has been replaced with ADO-E134.Thanks, Krishna

@krishker  There is no format such that, it takes the name attribute of your custom property.For Eg:  you have a text field with ./sampleProperty Navigate to initial content of your template node and save that custom property with the value you want to come as part of page creation with this templa...

Hi @sravs , Can you try making the authenticator reference optional in your Service class. @Reference(policy = ReferencePolicy.DYNAMIC, cardinality = ReferenceCardinality.OPTIONAL) private volatile Authenticator authenticator; Thanks, Krishna

@krishker you can add properties to initial/jcr:content node if you want any properties that needs to come as part of page creation. Eg: /conf/we-retail/settings/wcm/templates/content-page/initial/jcr:content Hope this helps, Krishna

Hi @Ronnie09 you should be able to add any fields into basic tab in metadata schema however you cannot edit few fields like type, created date etc. Thanks, Krishna

Hi @chaitanya_harinath , I think granite UI does not allow to dynamically change the name attribute after it is included.