Messages

1

General Board / Virtual Document Sections Starting on New Page

« on: July 26, 2024, 12:06:57 am »

I have a virtual document with several sections (model document elements). Currently it takes each section and starts on a new page when generating the content. Is there a way for a section in the Virtual Document to continue on from the previous page or do they always have to start on a new page? Am I missing a setting somewhere?

2

General Board / Report Heading Levelling

« on: July 25, 2024, 05:41:22 pm »

Hi

I am having an issue getting the headers to structure correctly (heading levelling) in a virtual report using several report templates. I have put the desired output structure right at the bottom but essentially I am struggling with 2 main points:
- Each new section of the report needs to start at a heading 1 (they are currently starting at heading 2, even when set to h1)
- The child packages within a section should be one level down from the parent package, but currently they are all coming out on the same level (h2).

First Section Report Template:
Introduction (h1)
package >
   {Pkg.Name} (h2)
   diagram >
      {Diagram.DiagramImg}
      element >
      {Template - Legend Element Descriptions} (see fragment layout below)
      < element
   < diagram
   element >
      {Element.Name} (h3)
      {Element.Notes}
      child elements >
      < child elements
   < element
   child packages >
   < child packages
< package

Template - Legend Element Descriptions
package >
   element >
       {Element.Name} (h2)
      {Element.Notes}
   < element
< package

Second Section Report Template:
package >
   diagram >
      {Diagram.Name} Product Model (h1)
      {Diagram.Notes}
      {Diagram.DiagramImg}
   < diagram
< package

Package Structure:
Product Architecture (package)
   Product Structure (package)
      Product Elements (elements)
   Rule Types (package)
      Rule Elements (elements)

Report Output:
Introduction (h1)
   Product Architecture (h2)
      Status (h3)
   Product Structure (h2)
      Product (h3)
   Rule Types (h2)
      Product : Product Rule (h3)
   
(Second section in the virtual document)
   Product Model Diagram (h2)

Desired Report Output:
Introduction (h1)
   Product Architecture (h2)
      Status (h3)
      Product Structure (h3)
         Product (h4)
      Rule Types (h3)
         Product : Product Rule (h4)
Product Model Diagram (h1)

I have tried these but all are unsuccessful:

• Adjusting the Element Name heading levelling (changed to h1 or h4) but it makes no difference during report generation
• updating the {PKG.NAME} to h1
• Adding in another {PKG.NAME} in the child packages tags but setting it to h3
• Updating the "Adjust Heading Levels" in the Document options for the second section template to "Heading 1" and to "None"

3

General Board / Re: Limited Glossary Based on Report Content Only

« on: July 10, 2024, 11:37:46 pm »

How do you create/add an index to an EA generated document ? or do you mean add an index in Word after the document was generated?

4

General Board / Re: Fragment vs Template

« on: July 08, 2024, 09:25:58 pm »

Thank you, I appreciate, and will apply, your advice.

Do you have a clear way of distinguishing the different types I asked about in point 2, or are all templates in EA actually the same?

"2. In addition, is there a difference on which type of template I copy from the ones that ship with EA e.g. System templates, EA Documentation > Publication templates, Document Templates (found in the resources window).
Or do they all function the same way, but are just grouped according to which document type they were designed for (e.g. Standard, Virtual, Custom)."

5

General Board / Fragment vs Template

« on: July 04, 2024, 04:53:30 pm »

1. I am building out a series of reports (both Virtual and Custom) and it seems in most cases I can use a fragment or template interchangeably.

• Is that true or do they have specific use cases and should be treated as such?
• If so, when is it advised to use which?

I currently used fragments when I need to use a custom query to return specific information, but then I use templates for everything else, resulting in a "master document" with templates inside templates and fragments inside those.

2. In addition, is there a difference on which type of template I copy from the ones that ship with EA e.g. System templates, EA Documentation > Publication templates, Document Templates (found in the resources window).
Or do they all function the same way, but are just grouped according to which document type they were designed for (e.g. Standard, Virtual, Custom).

The reason I ask is that I would ideally want as few templates as possible with maximum reuse, so design 1 template that can be used in both a virtual and custom document. Is reuse in templates smart design or rather create very specific templates for the document type I need.

TIA

6

General Board / Document Generation - diagrams with fields together/set diagram size

« on: July 04, 2024, 04:40:59 pm »

This is a two part topic:
1. I need to generate a document where the diagram name, diagram image and diagram figure (label) appear together instead of spread over 2 pages. My diagram is long and so when I generate the report, it puts the diagram name as a heading on 1 page, then the diagram on a new page and then the diagram figure on the third page.

I have tried highlighting all three lines in the template and selecting: Keep together but it doesn't seem to lock them together.
I know I can resize the diagram after generation (or on the custom document) but then when you regenerate or update that section it resizes the diagram.

Any suggestions would be appreciated.

Template:
package >
diagram >
{Diagram.Name} Product Model
{Diagram.DiagramImg}
{Diagram.Figure}
< diagram
< package

2. As an hack-alternative - is there a way to set the diagram size in a document fragment/template, so that when you generate the document, the diagram will print at that size e.g. set the height to always be the same?

7

General Board / Re: Limited Glossary Based on Report Content Only

« on: June 28, 2024, 08:54:07 pm »

Fair enough. Could you limit what is generated from the glossary based on the glossary type field? i.e. could I include all "Type: Acronyms" but ignore all glossary items with "Type: System"?

8

General Board / Limited Glossary Based on Report Content Only

« on: June 24, 2024, 09:21:19 pm »

Hi, I know from the forum history that this question has been asked before, but apart from a third party tool, is there a way to limit the report generated glossary to list only the terms relevant (that appear in) in the report that is generated?
Thanks in advance