Use case
Depending on the structure of your requirement pages, you may organize your requirements with a first parent requirement at the top, and following tables will actually refine that parent in tables below, with additional requirements.
Giving you a page structure looking like this:
Using this structure, you will want all following requirements to become automatic dependencies to the parent.
How does it work ?
Put the Configuration macro at the top of your page, or the table of your desired children requirements.
Go to the Parent Configuration, and choose the relationship name you desire.
We take the first requirement of the page as the parent, when there is only one requirement defined in the table (ex: a vertical table, or a paragraph), we’ll index it as a parent of all following requirements.
What your document looks like: | What we index: |
|---|---|
 |  |
 |