Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Dermot

Pages: 1 ... 36 37 [38] 39
In terms of clarifying the numbering:

User defined numbering can be set up using the menu items under Edit | List and Overrides.

With RTF reporting there is a general need to set the List Numbering format for the different levels of indentation in a generated document.
For example:
1. Package level 1
    1.1 Package level 2 (child package)
      1.1.1 Element Level 1 Element (child element)

To do this a numbering “List” must be set up and a set of “List Overrides” defined for this “List”. The List overrides also need to have the initial setting on the formatting altered to 1.1.1.  These Numbering Lists can then be applied using Paragraph Numbering to the Headings set for Packages and Elements.

The steps to do this are as follows:

To create a specific list numbering, perform the following steps.
1)      Select Edit | List Overrides | Create List item.
•      Define the name of a new listing in the List Name field i.e MyList.
•      Select OK.

2)      Create the List Override using: Edit | List Overrides | Create List Override.
•      Select the List to Override just created (MyList).
•      Press OK.
3)      To set the Style of each level you need to set the List Level Properties for each level using Edit | List and Overrides | Edit List Level.
To set the first level numbering (used in the Package Section):
1)      From the List Override drop-down, select the List Item just created (i.e. MyList).
2)      Set the level numbering :
a.      List Level:             1
b.      Number Text:      ~1~.
3)      Select OK to save changes.

To set the second level numbering (MyList):
1)      In List Level  - Set this to: 2 (maybe for nested Packages or Elements)
2)      Set the Start At:  change from 0 to 1 (change from 1.0 to 1.1 formatting)
3)      Select OK to save changes.

Do this for level 3, Level 4  etc. to cover adjusted headings.

Note: As the heading fonts are incremented for nested packages, if a 1.1.1 starter is required rather than 1.0.0, then the: List Levels properties | Start At - needs to be set for or all list levels.

To use the new numbering created:
1.      In the Content window select the text to be numbered
package >
 Package: {Pkg.Name}
element >

2.      Set the font heading level

The newly created numbering should then be accessible under Paragraph | List Numbering.
•      Select the new numbering (i.e. List MyList, Override# 001)
•      Set your level to 1.
•      Select OK to set your numbering

3.      Select the Element section:
element >
 Element {Element.Name}.
child elements >
< child elements
< element

4.      Set the Heading style (i.e. Heading 2) :
5.      Set the numbering to MyList - Level 2 - using:
                  Paragraph | List Numbering.
                Select OK

Let me know if this covers what you are asking.
I will get this added to the help file.

Hello Paul,
I would suggest  you send in a copy of the RTF template and the output generated to the sparxsupport email.  I would reccomend you generate it from the EAExample.eap model - so that it can be re-produced on our end.

Hello Paul,

I would suggest you have a look at the whitepaper on RTF report generation - see the section on "Numbering" - see: "user definable numbering".  The paper is available from:

Regarding the second point - I am not sure I understand what you are referring to with next level formating?

Regarding adding a "Custom Value" - You can add a one-off Tagged Value or set up a Profile to include this tagged Value with newly created tables.  The Tagged Value can be reported in the RTF using Element::ValueOF or Element::Attribute ::ValueOf - depending on where you have defined the Tagged Values.  I suggest you look at the Requirements whitepaper for an overveiw of setting up the Profiles for Tagged Values:

This as a starter:
See this section in the EA Help file.

The Automation Interface - Project Interface - does support generation of RTF documents using:
RunReport (String, String, String) see EA's help.
However I do not know of any means to Automate any editing of the RTF template in the RTF editor.

Hello Clifford,
I would suggest you send this through as a email to support, along with an export of the templates used and the resulting output generated.

I understand ClearCase does offer SCC compliance.  We have had other users using ClearCase but set to work in SCC mode.  How that is set you would nned to check with the ClearCase documentation.

I see this is not DXL code - what version of DOORS are you using?
If the code is not on the DOORS side - are you seting this up as an EA-addin?  If so the Repository is already set if you are using the standard ADD-In code i.e. see EA_GetMenuItems(EA.Repository Repository, ...)

Automation Interface, Add-Ins and Tools / Re: Create a RTF from API
« on: May 02, 2008, 03:16:31 pm »
One point to note with the Automation RunReport() - it allows for both the legacy RTF report generator templates, as well as the new report templates.  If you do have templates of the same Name in both the legacy and the new, then you can run into a problem of one being generated when it not what is expected.  So check both the new and  the legacy report template names and ensure there is no mix up.

I would suggest you create a simple template of unique name and re-test your call to RunReport().

Hello TLC,

In the RTF editor you need to set the List Levels to start the numbering as you want it.  See the "Numbering" section  in  the whitepaper on RTF report generation:

The root Node package name will be rendered using the package Section:

If you are primarily reporting on sub-packages from below the Root node then it would be best to create a Virtual document and either set the Master Document or a Sub-document to just report the Root name using the above (i.e. drag across the Root package to the model document class).  
In the Editor - Unset the Section: Child Package - then it will only parse the first entry.

I hope this is of help.

Hello TLC,

When you say 'Project Name', what are you refering to - The root-node of the packages, the repository name or ...?

Hello TLC,

Unfortuantely I cannot send an XMI copy of a template-package across the forum, however below is list of the steps to create a Virtual-template-Package:

Creating a Master Document:
The Master Document defines the general template for the Table of Contents and Headers and Footers etc.
1)      Open the Tagged Values view  (Ctrl-Shift+6)
2)      Create a Master Document Package using either:
      Under a Package Create a new diagram of type: Model document
      From the toolbar select: Documentation
      On an existing Diagram:
      From the Toolbar select: Toolbar | More tools | Extended | Documentation
3)      Drag a Master Document Package onto the diagram. This will prompt for a package name and will create a Package and a Diagram.

4)      Open the created Diagram (the Toolbar will now display Documentation).
5)      From the Toolbar Documentation - drag on a Model Document Element. Give the Element an appropriate name (e.g. the sub-document section name: “Requirements”).
6)      Select the Element:
      In the Tagged Values window; under RTFTemplate;  set the Template using the drop-down.
      Set the packages to report or  a filter:
•      Drag the packages to be reported onto the Element
•      Set a filter in the Tagged Values window by creating a Tagged Value of type SearchName, then  select an existing Search in SearchName.  
•      If the Search requires a filter value, create a Tagged Value of type SearchValue and set the Filter Value in this Tagged Value.

Repeat steps 5- 6 for each new sub-document required.

I hope this is of help.


The latest version of EA – 7.1 available for download, supports creating Virtual documents that contain multiple model templates.

You can combine several Model Documents under a Master Document package element.
Each Model Document element provides a separate template; for example, an Actor Section for the Actors and a Use Case template for a section on Use Cases. The Master Document links any number of Model Documents into a single generated document, and provides headers and footers and a central table of contents.


Pages: 1 ... 36 37 [38] 39