|
|
|
|
The following issue has been re-assigned. |
|
Assignee: Dragos Mihalache
Assigner: Julien Anguenot
Date: 23/04/07 16:29
Comment:
Versioning rules issue. We just discussed this with Dragos.
Basically when a document is valid, when doing a modification this won't be possible to modify the document without :
- going back to Project life cycle state.
- incrementing the version (major or minor)
|
|
This is a proposition of improvment that I think is quite major for the usage of Nuxeo.
Context:
1- I've create a new document based on a file
2- I've Approved this document during a "Approbation Review".
=> document state is passed from "In Projet" to "valid"
3- I've published this document in the "Section" part.
4- I've modified the document (the description and upload of a new file)
=> It's status is still "Valid".
I think that in a enterprise context (due to Quality constraints), this is critical! Indeed the document has been MODIFIED and cannot still be considered as VALID.
The document status shall be automatically be changed to "In Project".
Impact :
As the document has been modified, it must be reviewed once again. In that aim, the "Approbation Review" shall once again propose the state "Set Valid"
Note : I'm open to any discussion ;-)
|
|
|
|
![]() |
|
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
