Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

When to use it?

When your document already has requirement keys defined as text, and you want to convert them to requirement yogi macros.

Example:

  • When importing a document from Word.
  • When migrating from Requirement Yogi Server


Using the requirements transformation

It is the first default step when trying to transform a requirement document. The wizard will take you through every table in your document and ask you which one contain requirements.

After selecting tables containing requirements, you will be taken to an other screen allowing you to refine your text selection.

For instance:

  • Only allowing requirements containing letters, numbers, or hyphens, but no dot or underscore. (Note: Requirements containing only letters would also be detected and transformed)

  • Only allowing requirements starting with "BR-" with a regular expression.

Keeping your requirements selection rules more generic will allow you to reuse the transformation on other pages


On the next screen, you will see a recapitulation of the requirements you selected, allowing you to manually exclude one if necessary.

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: Having a Requirement transformation rule targeting tables 1 to 3, and another targeting table 5

  • No labels