Keyword Dictionaries, Blueprints and Inline Creation

Release 1.4

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.

This is a standard property, as defined in Properties and RY Reports.

Specification

Types rely on features which are already available in Requirement Yogi:

Property	Value	Notes
`Type`	Any string	The type will be displayed in the requirement properties, When using the inline creation popup, the type will be suggested, If you already use the "Type" property in your documentation, then they will be visible in the inline creation popup. We think this is a minor inconvenience.
`_formatting`	#color; bold; italic; underlined;	All requirements with this formatting will be formatted accordingly. Elements must be in the specific order, followed by a semi-colon and an optional space. The first item is a color, in hex/css format, such as " #ff0000" for red. Note that this property is not searchable, since it contains "_".

Creating a new type

If you haven't defined any type yet, the form suggests to. It will use a blueprint to create the type.