Versions Compared

Old Version 2

changes.mady.by.user Adrien Ragot

Saved on

compared with

New Version 3

changes.mady.by.user Adrien Ragot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

...

Specifications of the feature

This part will explain how this feature works. It leverages the Properties 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:

PropertyValueNotes
TypeAny string
  • The type will be displayed in the requirement properties,
  • When using the inline creation popup, the type will be types are suggested,
  • If you There is the inconvenience that people who already use the "Type" property in your documentation, then they will be visible in the inline creation popupfor another purpose will populate the inline dialog unnecessarily. We think this is a minor inconvenience because the inline dialog isn't used often.
_formatting#color; bold; italic; underlined;
  • All requirements with this formatting property 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 CSS color , in hex/css format, such as " #ff0000" for red.
  • Note that this property is not searchable or visible in the details, 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 typeThe inline dialog suggests colors and creates the blueprint automatically.