topic Re: Multiple version creations while creating/updating in Alfresco Archive

Multiple version creations while creating/updating

satishvarmadand — Thu, 05 Mar 2009 19:45:55 GMT

Hi,How it is going o solve the problem for Update. When i try to update a file, i am using Content contentRef = contentService.write(node, Constants.PROP_CONTENT, dataToUpdate, contentFormat);But by calling this, it is creating a version. I want to disable version creation when i update a document

Re: Multiple version creations while creating/updating

satishvarmadand — Thu, 05 Mar 2009 21:09:21 GMT

Hi,
I found the solution and posting here. This moght be helpful if anyone is searching for this

Here is the way .
1) Search for "contentModel.xml" file . This will be under tomcat/webapps/alfresco/WEB-INF/classes/alfresco/model/contentModel.xml
2) Look for "<aspect name="cm:versionable">" inside that and make "<property name="cm:initialVersion">" & "<property name="cm:autoVersion">" as false.

By updating this, it wont add a version by default. Now you will get more control on when to add a version and you can do that by
VersionResult res = authoringService.createVersion(predicateVersion, ….versioncomments, false);

We can get the versionLabel & other version properties from this returned object.

-Satish

Re: Multiple version creations while creating/updating

cviaud — Tue, 21 Apr 2009 16:09:59 GMT

Thanks for this information. Anyway, I have one relating problem.

When I set <property name="cm:initialVersion">" & "<property name="cm:autoVersion">" as false, I've got an error on the first "check-in" I make.

Didin't you get this problem ?

Re: Multiple version creations while creating/updating

ra74 — Mon, 27 Apr 2009 13:07:33 GMT

Hi,
I found the solution and posting here. This moght be helpful if anyone is searching for this

Here is the way .
1) Search for "contentModel.xml" file . This will be under tomcat/webapps/alfresco/WEB-INF/classes/alfresco/model/contentModel.xml
2) Look for "<aspect name="cm:versionable">" inside that and make "<property name="cm:initialVersion">" & "<property name="cm:autoVersion">" as false.

By updating this, it wont add a version by default. Now you will get more control on when to add a version and you can do that by
VersionResult res = authoringService.createVersion(predicateVersion, ….versioncomments, false);

We can get the versionLabel & other version properties from this returned object.

-Satish

But I think there's a risk that it can change alfresco's default behavior for example type cm:mlContainer is versionable. And you have to remember to change the war during upgrade - that sort of customization should be done not in the war
I'm setting properties initialVersion and autoVersion directly in my code just before update

Re: Multiple version creations while creating/updating

jneeve — Tue, 29 Sep 2009 19:38:05 GMT

In case anyone finds this helpfull, this is what I did..

Assuming you have created a file already, use the authoring service to checkout the file. Then use the content service to update that working copy, and check it back in forcing a major version.

You''ll need to get a reference to the file you want to work with…In this example Im dealing with the bytes of a file Im reading in.



// Add the versionable aspect to the document.  This will allows the content to be versioned
makeVersionable(repositoryService, contentReference);

// Use authoring service to checkout file, update content, then check back in with major revision
AuthoringServiceSoapBindingStub authoringService = WebServiceFactory.getAuthoringService();

// Checkout the document to update, placing the working document in the same folder
Predicate itemsToCheckOut = new Predicate(new Reference[]{contentReference}, null, null);
CheckoutResult checkOutResult = authoringService.checkout(itemsToCheckOut, null);

// Get a reference to the working copy
Reference workingCopyReference = checkOutResult.getWorkingCopies()[0];

// Update the content of the working copy
ContentFormat contentFormat = new ContentFormat(MIME_TYPE, "UTF-8");
contentService.write(workingCopyReference, Constants.PROP_CONTENT, bytearray, contentFormat);

// Now check the working copy in with a description of the change made that will be recorded in the version history
Predicate predicate = new Predicate(new Reference[]{workingCopyReference}, null, null);

NamedValue[] revisionType = new NamedValue[]{Utils.createNamedValue("versionType", "MAJOR")};
authoringService.checkin(predicate, revisionType, false);
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍