...
| Excerpt | ||||
|---|---|---|---|---|
| ||||
Read this documentation page to learn how to use the requirement configuration macro and change the way your requirements are indexed. |
It is absolutely not mandatory to use a Configuration macro, but it will help you customize your requirement detail with property and dependency names.
Follow this tutorial to know how to add properties to requirements, and dependencies. And how to customize their names to simplify your requirement detail: https://youtu.be/891Q3OpCiLA?si=iaWgX2gN_TQj5L0Q |
To add a configuration macro, in the page edit mode, type |
...
 |
After adding a macro to the page, you can edit it simply by clicking on the macro: |
In tables
When you define requirements in table, by default, the requirement key should be in the first column, with a description in the second column, and properties in the following columns.
This table:
Gets indexed as:
Here is the default configuration for requirements in tables:
With the configuration macro, you can:
Rename properties.
Change the column type.
Here, I changed the column of "Author" in "Original Author".
My "Dependencies" column was indexed both as a dependency and as a property, so I added a 4th column to my configuration macro to uncheck the indexing as a property, and I set the configuration macro to apply to all the following tables in the document (This configuration is not global, you need to add the macro to every Confluence page with requirements).
After inserting the macro and publishing the edited Confluence page, my requirement is now indexed with the changed properties as:
You can quickly "unindex" the requirements in a page by adding a configuration macro at the top of the document and uncheck the requirements column. It can be useful when you have duplicated requirement definitions.
In paragraphs and headings
| Info |
|---|
New feature |
When you define requirements in paragraph or headings, by default, the description of the requirement is the following text.
For this page:
Here are my requirements:
With the configuration macro, you can:
Change the property name.
Treat the bold text as normal text.
Change the dependency name.
Ignore the numbering in headings.
After inserting the macro and publishing the document, here is my requirement again:
In headings
You can ignore the numbered headings by passing a regular expression specifying the numbering format.
My headings:
will get saved as:
Here are a few common ways to number headings and their regexes:
...
Numbering
...
Example
...
Regex
...
Decimal
...
1.2.
...
^(\d+\.)+\s*
...
ISO-2145
...
1.2
...
^(\d+\.?)+\s*
...
Lower-latin
...
a.b.
...
^([a-z]+\.?)+\s*
...
Upper-latin
...
A.B.
...
^([A-Z]+\.?)+\s*
...
Upper-roman
...
I.II.III.
...
 |
It is also possible to add a Configuration macro from the view mode, with the Transformation wizard, and then apply it in bulk to multiple pages. See documentation here: Transformation wizard: Transform your pages .
Possible configurations:
Table configuration: Let’s you exclude content from being indexed as a property or dependency; Change the name of the property displayed in the detail vs the confluence page.
Paragraph Configuration:If you write requirements in paragraphs instead of tables, this let’s you configure the name of the property, and the relationship to requirement links.
Document Configuration: This is the evolution of the paragraph configuration. We call this feature Linear Documents. It is best suited when requirements are written outside of tables, when you reuse public standards or your customer’s requirements. It let’s you create requirements from text headers, configure more properties and dependencies.
Parent requirement configuration: If you have defined one requirement in a table, and want to index all following requirements as children.
Limitations
If you want to apply two configurations to your table, you will need to add multiple macros before your table. For example, if you want to use the Table Configuration, and the parent requirement configuration you’ll have to put two macros.