Page Comparison

...

It is also possible to add a Configuration macro from the view mode, with the Transformation wizard.

Table Configuration

If your requirements are in tables, it is absolutely not mandatory. The Requirement Yogi configuration macro is useful to change the way your requirements are indexed and override column titles, or choose to put the 3rd column as the description instead of the 2nd.

When you define requirements in table, by default, the requirement key will be in the first column, with a description in the second column, and properties and depencies dependencies in the following columns.

It also works for vertical tables: rows will be identified as columns. (Ex: 1st row in your vertical table will be mapped as the 1st column in the Configuration macro, 2nd row to the 2nd column, and so on.).

This table:	Gets indexed as:

...

Paragraph Configuration

When you define requirements in paragraph or headings, by default, the description of the requirement is the following text. Requirement keys in paragraphs:

...

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:

When requirements are in headings

You can ignore the numbered headings by passing a regular expression specifying the numbering format. My headings:
will get saved as:

...

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.

...