Item9081: Force new revision on each state transition

Whenever a state transition happens, we need to force a new revision. otherwise state history can be lost due to reprev.

-- CrawfordCurrie - 31 May 2010

It would be nice if we could define a specific state transition that would force a new revision. This could apply in whenever eg an approval from the general manager is necessary for publishing, but there are also some intermediate stages that are just clerical approvals, that need not update the revision since they add nothing to the context. Setting this to "waiting for feedback".

-- StefanosKouzof - 09 Jun 2010

Well, it might be nice, but I have to put my ISO9000 hat on and say it's not acceptable. If you define a workflow, then it's important that all steps in that workflow are recorded for posterity. IMHO there is no point in having an approval step if you don't record who or what executed the approval. Of course the force new revision only applies when the same person executes two state transitions within the {ReplaceRevisionIfEditedWithin} time.

If anything, wouldn't it be more sensible to be able to set a "you don't need to force a new revision on this transition" flag in the transition table?

Either way, this task is closed, and good workflow practice dictates that if you intend to implement this feature you should open a new task

-- CrawfordCurrie - 10 Jun 2010

Commenting is disabled while not logged in