If I understand correctly, the audit features are for a node (and presumibly for the document contained in the node) but this does not covers the case when a document is moved to another node (as is done when using a simple workflow for approve/reject actions).
There are cases (very often) when a document is accessed and modified by different actors (as is the case in a collaborative environment). In those cases it is very useful to know the past history of a document (e.g. who created it, who read, who approved/rejected it, …) and it would be very useful to map this loose workflow with a simple workflow (and add/delete new transitions by adding new folders/new rules). The only missing part is the "history".
Even there are cases in which an advanced workflow cannot be used to map such collaborative workflow. That´s why it would be very useful to have an "history/trace" aspect that collects all this activity information and can be added to individual documents. Thsi would allow to map collaborative workflows that cannot be mapped using an advanced workflow.
Any comments?
