Those features were published in version 1.4 in March 2016.
Annotate keywords, error messages and part numbers
We're introducing the dictionary blueprint in Requirement Yogi. It starts with a template where people can enter any kind of key/description entry:
The user can assign a color to distinguish, for example, error messages from normal messages:
Importing documents from the customer
People often have to quickly import new requirements from the customer. Requirement Yogi makes it very efficient. On a page, select a candidate for a requirement key. In the inline pop-up, click "Define as a requirement" or press Alt + Shift + R:
The list of types appear:
After you click Create, the requirement will be added to the blueprint page. All references in the page (and optionally in the space) will be transformed to links.
To speed up the conversion, if all requirements on your page start with "ODIS", then they can all be transformed and added to the blueprint.
Specifications of the feature
This part will explain how this feature works. It leverages the Properties and RY Reports feature, so users could reach the same results without using the template. It defines the special properties named "Type" and "_formatting". Here are more details:
|#color; bold; italic; underlined;|
Creating a new type
The inline dialog suggests colors and creates the blueprint automatically.