Whant diffrent text for objects depending of report type

[steen.jensen]

We have an Application catalog based on Archimate_Component in a structure based on bussiness capability.
The Notes field have an short description of the systems capability.
Severel Tags of diffrent information
But, where should we but in an longer and more description text for each app/system?
- as linked dokument?
- a Tag field?
- other solutions?

The purpose is to generate an it-landscape document for every time we are in an procurment phase

[Geert Bellekens]

Using the linked document actually a pretty good option.

Linked Documents: If you use the same stylesheet as your templates, you can even have it seamlessly integrated in your generated document (using the same headers styles)
You can create an linked document template to make sure all of your full descriptions have somewhat the same structure.
Added bonus is that you can add images and tables and stuff in these linked documents.

Tags: Downside of using tags is that they only support plain text, and writing a few paragraphs or pages into the tiny memo box is not going to make anyone happy.

Other solutions: For a couple of clients we divided the notes into different sections using html tags. That could something like

Code: [Select]

<definition>The short definition</description>
<description>A longer text</description>
<securityConcerns>something about security</securityConcerns>
We then used a script fragment to parse the notes and fill the different sections in the generated document.

That worked pretty well.

Geert