PNP Publication Workflow
Three components exist to the documentation workflow, these include:
Scroll Documents
Create a scroll document for all spaces to roll up into the URL.
Create Variants as necessary. At a minimum, set a publish variant.
These variants are applied as labels to the Confluence space.
Variants indicate where and when a page is published. The variant publish is used when a page is to go live. The URL extension is set to publish.
Scroll Viewport
For spaces that are edited by other departments in bits and pieces, set a Version. The URL extension to the version is ok.
For spaces that are edited and approved in one step (legal, Info Sec, Technology) there is no need to set a version. Use the working version when publishing and set the version URL extension to ok.
When generating the URL, ensure the correct Version and Variant with the correct URL extension publish and ok are chosen for the public URL.
BEST PRACTICE: Save a new version with each publish to the URL. major and minor versions are used.
Document Sharing and Delivery
Once a PDF or URL is stored on Community, the document is operational and serves its function. This stage defines how documents are shared and edited, whether by an individual or a group of people.
Depending on the securities set for a particular Community sharing link, these documents may be distributed internally (inside the business) or shared with third-party stakeholders such as subcontractors and clients.
Compliance with Other Policies and SOPs
The review, approval, and exercise of authority under this Policy must comply with all applicable Thrive policies and procedures, including, without limitation:
Commercial Documentation
Refer to the following for guidance on:
Contact Knowledge Management if your questions are not answered by this documentation.