cancel
Showing results for 
Search instead for 
Did you mean: 

Inheritance between aspects

anujs86
Champ in-the-making
Champ in-the-making
Hi,

I have content type A with mandatory aspect as ABC having some properties 1,2,3
Now, I have created another content type B of parent A with mandatory aspect DEF having properties 4,5.

I am able to use properties 1,2,3 in content type B but I want only 2.
In my web-client-config-custom.xml, I have defined  like this

<config evaluator="aspect-name" condition="ABC">
<property-sheet>      
   <show-property name="1" read-only="false" />
        <show-property name="2" read-only="false" />
        <show-property name="3" read-only="false" />
</property-sheet>
</config>

<config evaluator="aspect-name" condition="DEF">
<property-sheet>      
   <show-property name="2" read-only="false" />
        <show-property name="4" read-only="false" />
        <show-property name="5" read-only="false" />
</property-sheet>
</config>

Now when I try to add content of type B, I see all properties 1,2,3,4,5
Also In view details I see all properties.

Is there any way where I can see only properties 2,4,5 for content type B??
4 REPLIES 4

mitpatoliya
Star Collaborator
Star Collaborator
Hi Anju,

If you simply remove the config for the aspect ABC it will not show the properties related to ABC.
As whatever the aspects you attache to any content type will show the properties from the config of those aspects.
Other option is remove ABC as mandatory aspect from typeA

anujs86
Champ in-the-making
Champ in-the-making
Hi Anuj,

If you simply remove the config for the aspect ABC it will not show the properties related to ABC.
As whatever the aspects you attache to any content type will show the properties from the config of those aspects.
Other option is remove ABC as mandatory aspect from typeA

Thanks for the reply Mit,

The problem is, If I remove config of aspect ABC, it won't show up in view details of document type 'A'.

mitpatoliya
Star Collaborator
Star Collaborator
Yes, that is there but this is the limitation of alfresco.
It could not give the property level access or permission or configuration.

anujs86
Champ in-the-making
Champ in-the-making
This I have sorted out by modifying content model.
Thanks Mit.