...
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. |
Section | ||
---|---|---|
| ||
We have shown some use cases for the demand of changing values for a collection of projectdoc documents. It requires manual steps that need to be conducted very carefully. It is strongly recommended that you have a recent backup in case your calls corrupt pages in your Confluence instance. In the future we will probably provide tools to make this task easier. In the meanwhile authors have tools to at least allow these task to be run effectively. |
...