Customizing release status

[landersohn]

I would like to customize the way letoDMS treats the release of documents. In particular I'd like to have
a) three different kinds of release: "unreleased" "prototype release" and "production release"
b) use letter instead of numbers for the versions. Ideally I'd want "x1, X2, X3,..." for "prototype release" status and letters "A,B,C,..." (except X) for "production release" status.

Question, is it possible to customize letoDMS relatively simply in this manner?

[matteo lucarelli]

The version number is an automated field increased by the db.
This is a mandatory requirement for a DMS: the version number cannot be a user field!

Another solution would be a custom extension to the version number (a free string the user can add to the auto-increasing version number).
Should fit?

About the different kinds of release status: who should modify the release status? Actually this status is automatic (modified by the system where there are no pending review/approval).
Could it use a way similar to the "obsolete" status? (manually imposed after the automatic assign)

[landersohn]

Matteo,
A custom extension to the version number would work, although it would be nice it was semi-automated.
In regards to the release status: I am thinking of a different group of approvers for the different release states, and I am haing engineering documentation in mind: in "prototype release" it would be just engineers, for production release the approvers would be broader and for example include manufacturing people. This is appplicable to for example medical devices where control needs to be present throughout development and design but with increasing levels of control the further the development moves along.

The extension to the version would make it easy to see what level of release a document has at a glance.

Maybe one can tie a group of approvers to the extension string: if say GROUP "Prototype" approves a document, the extension string gets automatically set to "proto" and if a a GROUP "Production" approves a document that string gets set to "production". A scheme like this would work just fine

The version number is an automated field increased by the db.
This is a mandatory requirement for a DMS: the version number cannot be a user field!

Another solution would be a custom extension to the version number (a free string the user can add to the auto-increasing version number).
Should fit?

About the different kinds of release status: who should modify the release status? Actually this status is automatic (modified by the system where there are no pending review/approval).
Could it use a way similar to the "obsolete" status? (manually imposed after the automatic assign)