Introduction to eaDocX Profiles

When you create a document using eaDocX, all the formatting options you have chosen are saved inside your Word document as a set of Profiles *.

Element Profiles

Each type of element, and even each stereotype of each type of element, has it’s own ‘profile’, which says how it will be printed:
Each Profile contains:

• How each type and stereotype of EA element should be formatted: table or inline,
• Which fields and tagged values are printed, and in which order
• Any table column titles,
• Any conditional formatting rules you have created
• Any data about elements related to this one
• ..and a few more data items

The Profiles are used in all the different sections in your document, so a <<Functional>>Requirement in one part of the document will be printed in exactly the same way everywhere else in the document. This is deliberate, because we think it makes the document more consistent, and so easier to read.

However if you really want to, there is a way to make the same element type print in different ways in the same document.

Variations on Element Profiles

Element Reports can have ther own private formatting, so if the elements are printed as part of an element report, they may look different.

Relationship tables allow you to print a table of related elements, and that table has it’s own private formatting.

Document Profiles

The profiles inside the document can be saved and shared between documents so that all your documents print in a similar style – see Sharing Document Profiles.

* for the technically minded, Profiles are stored in a ‘Custom Properties’ field in the Word document, so they don’t get accidentally damaged as you edit the mains document, but they still get saved with the document, and copied when the document get copied. They are stored in an XML format, along with all the local document settings.

See also import and export profiles