10-06-2010, 03:42 PM
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)
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)