cancel
Showing results for 
Search instead for 
Did you mean: 

associations source cardinality preventing checkout of content

ragnaroek-hh
Champ in-the-making
Champ in-the-making
In 3.2 we created an association having a source cardinality of 0 or 1 as below:


         <associations>
            <association name="we:pdf">
               <title>FreigabeDokument</title>
               <source>
                  <mandatory>false</mandatory>
                  <many>false</many>
               </source>
               <target>
                  <class>we:doc</class>
                  <mandatory>false</mandatory>
                  <many>false</many>
               </target>
            </association>
         </associations>

by means of this we successfully enforced, that a target is not referenced no more than once.

After migration to 4.2c we encountered, that the explorer checkout function violates integrity. I guess, that this is caused by the new alfresco4.0 content model for working copies, because both the original and the working copy now have identical aspects and properties - opposed to former model.

[blockcode]
The association source multiplicity has been violated:
   Target Node: workspace://SpacesStore/a7a140d5-f82b-40af-a30f-691cd949028a
   Association: Association[ class=ClassDef[name={http://doc.model/dictionary/0.25}docID], name={http://doc.model/dictionary/0.25}pdf, target class={http://doc.model/dictionary/0.25}doc, source role=null, target role=null]
   Required source Multiplicity: 0..1
   Actual source Multiplicity: 2
[/blockcode]

Is there a new way how to express the cardinality 0..1? We do not want to use the workaround of the source increasing cardinality to 0..many. Any ideas apreciated
2 REPLIES 2

yogeshpj
Star Contributor
Star Contributor
Hi,

We are also getting the same problem.
Have you resolved the problem ?

Thanks,
Yogesh Prajapati

yogeshpj
Star Contributor
Star Contributor
I resolved the issue myself.

Actually when we are checking out the document,It clones the original document with name as "original-doc-(working copy)".

Now working copy will also have the association which we have defined as source and many both as false ( only 0 or 1 cardinality allowed).

At this situation,I got integrity violation as we are making 2 sources ( original document and working copy) for defined association.

Straight solution is change in model file.Make many attribute as true in source.
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.