Page Properties is not disabled or no Lock Icon (Cancel Inheritance) while Rollout in AEM 6.5

[tushaar_srivastava]

Hi Team,

I have created a custom rollout function, where if I rollout a specific page to some specific locale,

ideally the rolled out out pages should show lock icon in touch-Ui in page properties.

But for my page there is no lock icon (Cancel inheritance) in Page properties dialog.

and it is editable.

@kautuk_sahni   @arunpatidar   @BrianKasingli   @Vijayalakshmi_S  @vanegi 

[shelly-goel]

@tushaar_srivastava 

It would be something to do with the custom rollout function, please provide more details around how you've set up the custom rollout.

[Ravi_Pampana · Accepted solution]

Hi,

Did you add granite:data ==> "cq-msm-lockable" property to your custom properties? If not adding that might solve your issue. Below is the sample for reference. 

Ex:

<someText

    jcr:primaryType="nt:unstructured"

    sling:resourceType="granite/ui/components/coral/foundation/form/textfield"

    fieldLabel="Some Text"

    name="./someText"

<granite:data

        jcr:primaryType="nt:unstructured"

        cq-msm-lockable="./someText"/>

/>

[Vijayalakshmi_S]

Hi @tushaar_srivastava,

cq-msm-lockable property is responsible for that lock icon and if live relationship exist on specific site/page, it should come up fine.

Could you please let know the below details to debug further

• If the lock icon is not coming up for a specific property or for entire properties of Page component
• If for a specific property, is it custom or OOB page property.
• ResourceType of Page component (Eg. Is it OOB Page core component)

[tushaar_srivastava]

Hi @Vijayalakshmi_S 

• If the lock icon is not coming up for a specific property or for entire properties of Page component
• Lock Icons are not coming for entire properties of Page
• If for a specific property, is it custom or OOB page property.
• Mostly OOB Properties (Overlaying OOB page dialog and add some additional fields)
• In pageProperties dialog added proeprty, cq-msm-lockable  :: String :: nodeName

• ResourceType of Page component (Eg. Is it OOB Page core component)
• We have Basic Common component, and that is inheriting (sling:ResourceSuperType = foundation/components/page)
• The Current Template I am using here is basically inheriting commons Page
• i.e. CurrenPage Template (dialog inhering from)  > Page B component and it' page dialog (dialog inhering from)  > (Commons Page  (sling:ResourceSuperType = foundation/components/page)
• And in all the page dialogs we have some page properties dialog added separately with some additional fields in page dialog.

• Do we need to Add cq-msm-lockable  :: String :: nodeName in all nodes in page dialogs
• Or Do we need to go tith a node granite:data inside page dialogs

[Vijayalakshmi_S]

Not sure of the equivalent of lockable property for foundation/components/page resource which has fields in xtype still. Suggest to update to latest core v2 page component.