If a document is upgraded with a new version and has been copied as reference, the reference document will also be upgraded.
|
Practical use of functionality?
When you copy a document as reference and then you upgrade the main document to a new version, the reference document will also be upgraded. |
|
|
What is the impact of not doing this?
Currently when you copy a document as a reference and then update the main document, if you want the reference document to have the latest version, you must delete the reference document and copy the new version as a reference in all the spaces where you copied it previously. |
Hi @Guest ,
I have a few thoughts and questions. :-)
Should the reference point to:
The latest document? (And access be lost to previous version when it is revised?)
All versions in the stack?
Does the document need to be "approved" via a review process before the reference to it is updated?
We might consider:
The reference being able to be updated manually to reference the latest version.
The original document pushing out its latest version to update all references to it.
This could be a manual process that workflow could automate once a document was approved.
Best regards, Paul Houghton...