AnsweredAssumed Answered

Space with Version Action + AutoVersioning - CMIS Sync NO but Add File in Explorer YES?

Question asked by lloy0076 on Apr 14, 2014
Latest reply on Apr 15, 2014 by lloy0076
alfresco-community-4.2.f-installer-linux-x64.bin on Centos 6.5 with the easy install option.

According to http://wiki.alfresco.com/wiki/Actions_and_Rules#Versionable when I use a rule action to add versionable, AutoVersion should be turned on. However, it seems to depend on how the file gets into the share.

Here is what I do:

1. Setup a rule for content that does not have the versionable aspect and give it the versionable aspect if it is created or entered the space.
2. Setup another rule for content that does have the versionable aspect and set it to checkin when it is updated.

PATH 1: Upload file by adding content using the Explorer web-application (http://foobar:8080/alfresco -i.e. the JSF app and not the one which is called share).

1. Upload a file, any file.
2. Examine the dialogs - notice that Auto Versioning tick box is present AND turned on.
3. Edit the file in any way.

It doesn't matter if you save it using WebDav, via CMIS Sync, CIFS or edit it in place.

It's happy.

PATH 2: Upload file by using CMIS sync from http://cmissync.com.

1. Upload a file, any file but using CMIS sync.
2. Go to the Alfresco Share app and notice that the file IS versioned.
3. But sadly, notice that for some reason auto-versioning property is off.

Also, notice that the "set property" action is BROKEN so you can't set any properties at all (but that is not this bug).

Now when you re-save/update files by CMIS sync, they get overwritten and you potentially lose data. And there's only ONE version (1.0).

Other salient information:

Here is my versionable aspect:

<blockcode>
      <aspect name="cm:versionable">
         <title>Versionable</title>
         <properties>
            <property name="cm:versionLabel">
               <title>Version Label</title>
               <type>d:text</type>
               <protected>true</protected>
            </property>
            <property name="cm:versionType">
               <title>Version Type</title>
               <type>d:text</type>
               <protected>true</protected>
            </property>
            <property name="cm:initialVersion">
               <title>Initial Version</title>
               <type>d:boolean</type>
               <default>true</default>
            </property>
            <property name="cm:autoVersion">
               <title>Auto Version</title>
               <type>d:boolean</type>
               <default>true</default>
            </property>
            <property name="cm:autoVersionOnUpdateProps">
               <title>Auto Version - on update properties only</title>
               <type>d:boolean</type>
               <default>true</default>
            </property>
          </properties>
      </aspect>
</blockcode>

It looks right to me!

But when applied by the site rule, the aspect - versionable is applied but not the property.

Is this a bug?

The attached file is what I see when I use CMIS sync to put the file in the repository. Notice how the Auto Version property says 'No' (i.e. false) but there is one version there; I believe it does have the versionable aspect.

Outcomes