Let's say a document has been validated. You can put anything you want when you modify it and it stays valid after that ? It should go back to the "project" state whe modified, and if the version number is incremented the older one should be marked as obsolete. Btw a Jira issue is already opened here : http://jira.nuxeo.org/browse/NXP-1040
-- Cédric On 10/18/07, JMP <[EMAIL PROTECTED]> wrote: > > Hello! > > I think it's normal. It's a correct behavior. When you start an > approbation workflow it's your choice to decide wich end state you want > (Valid or Obsolete). Once you accomplish the workflow and your document is > in Valid State, we consider that you can't modify it because it's valid! > It's the "path of validation" or the "validation way". It's a simple "use > case" lifecycle practice (an example of lifecycle process implementation). > > BG. > Jean Marie > > > 2007/10/17, Quentin Lamerand <[EMAIL PROTECTED]>: > > > > Hello Nuxeo folks ! How are you ? > > We were looking at the lifecycle example in the sample project and tried > > to use the approbation review on a document with this lifecycle. It works > > great for the first transition but once we are in the second state, the > > approbation review isn't anymore in the available workflows list. Is it a > > correct behavior ? Maybe we have to write a custom workflow too ? > > Best regards, > > Quentin > >
_______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
