topic child-assiociations behaviour in Alfresco Archive

child-assiociations behaviour

federico_tesei — Thu, 06 Dec 2007 11:47:14 GMT

Hi to all,By principle a child association should perform a cascade delete starting from root deletion node.Hence we have defined a custom content model [ ref attached files customModel e web-client-config-custom xml files ] that define a Tab content with two child-association;> a description &g

Re: child-assiociations behaviour

rivarola — Fri, 07 Dec 2007 16:18:31 GMT

Hello,

Is the child association between your Tab content and description/image a primary child association ?
In other words, do the 3 content already exist in the repository before you set the Tab as parent of the others ?

Re: child-assiociations behaviour

federico_tesei — Fri, 07 Dec 2007 18:41:29 GMT

Hello rivarola,
thanks for your reply.
The sequence through webclient is this:
> no content on the space
> add/create to/on the space a description
> add one or more image to the space
> add/create a tab on the finish click the modify Properties pane opens to select/add the associable stuff description and/or images previuosly added.
> I see the linked stuff on the property pane.

The view through info-doc.ftl or node browser instead shows that the Associations [all description and images ] are missing and when I try a Tab remove it just delete the Tab leaving description and image stuff in place.

thanks again

federico

Re: child-assiociations behaviour

rivarola — Mon, 10 Dec 2007 08:46:21 GMT

Hi Federico,

If the items already exist in the repository before creating the child association that links them, the child association is not primary. As a consequence removing the Tab won't remove its children. This behaviour is normal in Alfresco : only the first (structural) child association involves cascade delete.
The thing I don't understand is why your association does not appear in the Node Browser.

Re: child-assiociations behaviour

federico_tesei — Mon, 17 Dec 2007 15:58:08 GMT

Hi rivarola,
back from flu sickness I'm going on investigating why the child associations do not are enforced when I create a Tab Content.
Anyway another key question for us is if a primary child association move 'cascading fashion' as does delete. I mean
if in space Src there are content A and his children a1 a2 a3 tied as child association when I move A to space Dst a1, a2, a3 are moved as well as child association children or not?

thanks

federico

Re: child-assiociations behaviour

viralshah — Thu, 18 Mar 2010 12:04:10 GMT

If the items already exist in the repository before creating the child association that links them, the child association is not primary. As a consequence removing the Tab won't remove its children. This behaviour is normal in Alfresco : only the first (structural) child association involves cascade delete.

In that case how does one create a primary child association from Alfresco Explorer ? Because the explorer gives option only to seach & select content which is existing on the repository. Really confused on this one.