Date: Fri, 29 Mar 2024 01:55:18 +0100 (CET) Message-ID: <1546287530.17589.1711673718053@09e9d69a2016> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17588_1086919674.1711673718052" ------=_Part_17588_1086919674.1711673718052 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Lifecycle phases define phases that are bound to a lifecycle.
Use lifecycle phases to organize items running through lifecycles.
The document type lifecycle-phase provides the following proper= ties:
Please note that only information about specific properties is provided = here. Common document property used by all document types are documented by= Document Propert= ies.
The reference to the lif= ecycle this phase belongs to.
Since 4.6
Since version 4.6 a parent document that is a lifecycle is automatically= listed.
Describe the type of the lifecycle phases.
List all items associated with this lifecycle phase.
List the subordinate types that are attached to this document.
These are internal notes that are usually not exported and only visible = to team members with write access.
But this is not a safe place to store sensible informat= ion. It is just a convenience for the reader to not be bothered with notes = stored here for the authors for later use. The security level is about supp= ressing the representation by a CSS style. Therefore consider this as a con= venience for the reader, not as a security tool.
The text of notes sections is also indexed.
For a document the references section contains pointers to resources tha= t prove the statements of the document.
Often these proofs are not easily distinguishable from further informati= on. In this case you may want to skip the reference section in favour for t= he resource list.
For further information please refer to References and Resources.
The resources section provides references to further information to the = topic of the document.
This may be information on the internet provided by the resource or info= rmation in the team's information systems. Anything the reader of the resou= rce might want to know, may be listed here.
For further information please refer to References and Resources.