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 ... 35 36 [37] 38 39
I can't seem to reproduce this - using the standard Master template and generating it with sub-reports the results allow comments in Word where ever the cursor is placed (except on the exterior of a table).
I would suggest you send through a copy of this to the support email for reveiw.

This can be done in a Virtual Document - using a Model Element with a Tagged Value: SearchName &  SearchValue - see the help on Virtual Documents or the Whitepaper on RTF reporting. Requires EA 7.1.

Automation Interface, Add-Ins and Tools / Re: Sequence diagram
« on: September 18, 2008, 03:23:19 pm »
If you have code that you are running under EA's Build, Test & Run then Sequence diagrams can be generated from this - see:
Is that what you are asking for?

I would suggest you have a look at the whitepaper on RTF report gerneation - see the section on Numbering.   The List numbering by default sets 1.0 rather than 1.1 - there is a note in this section:
[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.]
For the whitepaper see:

Automation Interface, Add-Ins and Tools / Re: importing requirements
« on: August 05, 2008, 10:31:25 am »
If the other product supports XMI import/export - then is the best process to use, otherwse the CSV import/export is the other option to look at.  There are detail steps on using this in the whitepaper on Requirements Management - see:
There is also an Add-in available for importing DOORS data.

Automation Interface, Add-Ins and Tools / Re: RTF report
« on: July 24, 2008, 11:48:42 am »
There is no direct filtering on the sub-element level of the RTF report generation. If you want to filter at this level it may be best to look into creating a query in the Advanced Search (ctrl-F).

The standard figure numbering is a text field: Figure: {Diagram.Figure}.  This is not directly referenced by other elements. However if you are using Element with Linked Documents -  there is the option to create hyperlinks to the diagrams in the Linked Document - by dragging a diagram from the Project Browser to the linked Document.  If the diagram and the Linked Document are generated in the report then the hyperlink will reference the diagram (Same can be done for elements & Packages).  See EA's help: "Hyperlink From Linked Document".

"Is there any other way to achieve this functionlity in the new RTF editor? "
Yes - the Sections:
Package::Model Document   &
Element::Model Document
Both support the output of RTF data from Linked Documents and Document Artifact Elements.

Automation Interface, Add-Ins and Tools / Re: Diagrams in RTF Reports
« on: June 30, 2008, 04:54:11 pm »
Hello Jason,

The RTF generator is set by default to scale diagrams to the page if larger than a page.  7.1 does support an option in the Diagram Propoerties under the Diagram Tab : RTF Document Options | Divide Diagrams into multiple pages.  You can set this for larger diagrams to ensure scaling does not minimise the diagram.  
In terms long diagrams and of parts of the diagram being off the bottom of a page - there has been a correction for this - but I am not sure which build - you might try the latest build.
Otherwise I would suggest you send through examples to the support email address - see below.

Automation Interface, Add-Ins and Tools / Re: Getting the linked item
« on: June 27, 2008, 03:40:18 pm »
In the VB code available from the download page on:
There are a couple routines dealing with this. See Repository.bas - DumpConnections, as well as, RequirementMain.bas - DumpHeirarchy.  These give two different routines of displaying Element- connector relations.

The RTF report generation largely works on Element Connector relations not Element-Connector-Element (Actor-association-Use Case), so it is best to report the set of Actors and the set of use Cases in one report.  If a different format is required for each, then the Vitual Document: Master Document - Sub-document can be used to set this up.
At present there is no filtering on connector types - we are looking at setting a similar filter to the element filter in the next major release.

Hello Ron,
GetElementByID() requires an ElementID - it won't work for a Diagram ID.  Sounds like you need to loop through the elements of the Diagram.DiagramObjects Collection.

Can you send through an example to SparxSupport to reproduce this(See support below) .

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.

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