You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
My question concerns the basics of document handling.
Until the document isn't signed (approved) by the CEO it is actually a DRAFT.
Being FINALLY signed by CEO it comes into effect from this moment or from the date specified in its text.
From this very moment none symbol in this document cannot be changed. View for example https://openknowledge.worldbank.org/bitstream/handle/10986/24985/9781464808524.pdf.
Otherwise it will be the NEXT VERSION of the document that should also be signed by CEO and should be once again registered with its specific date and number.
That means that FINALLY APPROVED document should be FINALLY FROZEN TECHNICALLY and nobody should be able to correct its text and cridentials (CEO, date, register number, storage link) or delete it. Even CEO, even accidentially.
I have not found in Confluence the mechanism of FREEZING FINAL DOCUMENTS. Manual downloading a document as a pdf file and uploading it back as an attachment doesn't guarantee that no corrections are made on this way or that it could not be deleted.
All its pages are actually only drafts: even if CEO signs a document via 'Comala workflows' and if 'APPROVED' label displays , this document is not protected from further changes or deleting.
Is there any solution?