nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Is possible to start the document version at 0.1?

smi2000

Hello,

I am using Alfresco community 4.0 and I am very interested in continuing to apply it to my document management.
But I have a problem: the default version of a document is 1.0, and this is not right for me.

Is possible to start the document version at 0.1?

thanks.

Find more posts tagged with

Comments

mrogers

Yes - that's what the version service on V4.0 does for minor versions.

smi2000

Hello mrogers,

I am working with share alfresco, and when I upload a document, your default version is always 1.0
How can I change this? I need the default start in 0.1

thanks in advance!

bchevallereau

Hello,

Which version of Alfresco do you use ?

There is an extension that allows users to specify the version (and the example is done with 0.1) : http://blogs.alfresco.com/wp/pmonks/2009/11/03/version-baselining/

But, the version is a simple meta-data "cm:versionLabel", so it should be possible to specify the version label during upload.

Ben

thirukathirvel

Hi,
Yes it is possible.
Do checkout your node and it creates the WorkingCopy node.Then checkin the workingCopy node with majorVersion Flag as false.Somethinf like this,
                upload.save();
      var workingCopyNode = upload.checkout();
      workingCopyNode.checkin("",false);

Thanks,
Thiru

twallace

I've been wrestling this issue for over 2 weeks and finally found a simple solution in Share.

Create a Folder Rule with the following:

Remove Versionable Aspect
Add Versionable Aspect
Change cm:versionLabel to 0.1
Check Out (no destination folder required)
Check In (as minor version)

This creates a locked document with a *hidden* version label. Manually upload a new version (same document is fine) and set it to a minor version. Document is then available with 0.1 as version label and with 0.1 as the last Version in the version history.

I implemented this on a folder as a Space Template, so that non-technical users don't need to do anything except create a new folder from the template. The document is then locked for editing by them and ready for the first 0.1 version to go in.