...
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
The projectdoc Toolbox defines the concept of a projectdoc Document. Such a document is a Confluence Page with properties and sections. A projectdoc Document can be identified either by its title and space or its name and doctype.
|
Section | |||||
---|---|---|---|---|---|
| |||||
In case authors actually need to change a name, this change cannot be by design an instant one. We are considering to include options to make the adjustment automatically in the future. Maybe by a dialog which will ask whether or not to change the names in referencing properties. This is similar to the action of deleting a page and asking whether or not the children should be removed, too. In the meantime this is a manual step. In case there is more than a couple of pages is involved, authors should consider to use the Web API to do the job.
|
...
Section | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||
Since we use the strategy to show names only if the document is in Released, Production, or Deprecated state, we now recognized how lax we handled the Iteration state of documents in our documentation. Here is an example on how we moved the iteration of all our role documents to Production.
|
Section | ||
---|---|---|
| ||
In case you need to change the name you need to wrap the name in a Name List Macro in the Confluence Storage Format. Since the name used in property values has not been changed when authors changed the name of the document, the old name can be used to select the documents in the Where Clause. For instance, if the name was a role name used in the Audience property, then the Where clause needs to select on the Audience Parameter of documents. The approach is identical to the use case we have shown for changing the Iteration property above. |
...