Documentation with EA

[Ronaldo Juliatto]

Hi

We intend to keep all documentation inside EA, but we are facing the problem that most of Edit fields, where we intend to fulfill the information, do not understand RTF, and so the generated documentation will lose a lot of formatting.
The second problem refers to the approval mechanics necessary for ISO. We can generate the final docs and approve it, but it is a paper and time-consuming process. We used tagged values for verification and approval, but the process seems to be something awkward yet.
Does anybody have faced these kinds of problems and find any solution that could be shared?

Any help would be greatly appreciated

Ronaldo Juliatto

[Tjerk]

Hi Ronaldo,

There is an option (View/Options/General) called Allow custom RTF tags in report, this option allows you to insert RTF in the notes. Be sure not to use RTF codes unintentionally then, otherwise your document might get corrupted easilly.

For the approval, you are able to use the field Status that is available for each element. Furthermore, you are able to select a package in the projectbrowser and set the status, phase, version and date for the package and (!) its underlying elements.

Greetings,
Tjerk