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
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.



Reporting on Tagged Values is dependant on where the Tagged Value is – i.e. it could be in: Package/Element/Element.Attribute etc.

For each Section in the RTF report editor (Package/Element/Element::Attributes etc. )
There are two options for reporting Tagged Values:
1)  Using the Section (i.e. Element::Tagged Values)
2)  Using “Valueof” – (in the Element field list – for Element::Tagged Values)
The “ValueOf”  is last entry.  This requires the tagged Value to be named.  

Option 2 would probably be the easiest to use if you require the data be in a simple form and placed early in the report.

The Automation Interface suports the generation of RTF reports using:
 - RunReport (String, String, String)

For the details on this command see:

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