| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
When to use it?
When creating a new requirement document,
When you want to ensure that requirement keys are unique.
Alternatives
You can insert individual keys by typing /req on a page and selecting the Requirement Yogi macro. See the tutorial.
Using the key generation
On the transformation wizard page, complete the default steps as usual, select a saved transformation or press skip to access the transformation summary.
Like with the Keys transformation or the Links transformation, you can select the tables where you want to apply the key generation.
| Panel | ||
|---|---|---|
| ||
Your tables are labeled with a number to facilitate table selection |
Configuring the key generation
You can use variables to reuse the key generation in other documents.
Available variables :
{space.key}
{page.id}
{page.title.capitals} will use the page title. Exemple: Business Requirements → BR
{parent.page.title.capitals} will use the parent page title.
You can also type the first requirement name in a table and let the plugin generate a key pattern from that.
| Panel | ||
|---|---|---|
| ||
We verify every key to ensure their unicity |
Changing the plugin configuration
At the summary step before transforming the page, simply click on the rule you want to modify to edit it.
On this step, you can modify every configuration you previously applied, or remove it.
You can add several rules of the same type.
Exemple: Generate keys starting with "BR-" in tables 1 to 3, and keys starting with "FN-" in table 5
