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 ... 33 34 [35] 36 37 ... 40
IN the RTF report template add the: Package | Diagram | Element - Section - but leave this blank to replicate the: Package | Element section. You can Set your Tagged Values using the Element field ValueOf() or using the TaggedValues Section.

In general this type of thing can be done by using taged Values of the same name in the different Groups you are reporting - e.g. if they are different packages - but reported through the same template - set up the TV's in the packages - set as the same name, but with alternate values - then use these for your different titles using: Package.ValueOf(TVname).

Automation Interface, Add-Ins and Tools / Re: Scripting for dummies
« on: January 06, 2010, 11:54:48 am »
If you are wanting to get Documentation from scripting you can use the RunReport () command to generate RTF docuemtnts or if you want create specific output to say Word there has been some VB 6 code for Document generation availble on:
this could be converted to VBScript and run using the scripting.

In the RTF editor: File | Document Options | Document Options Tab:
 - Connector Direction: (set the direction)
 - Exclude Connector Type:
 (Exclude all but the UseCase connector)

I hope this clarifies things.

Marcel, I assume you are stating that the Use Cases are contained in the package to be reoprted - the Actors are in an external package - Is that correct?
If so, use the Connectors.source.Element & Connectors.Target.Element to report the related Actors - the filter in the template Document Options can be set by connector to filter to a specific type and direction, but not the destination element type.  (i.e. set up filtering to source->Target & UseCase connector Type).
PLease feel free to  put in a Feature Request to have an Actors section (same as External Requirements section).

Automation Interface, Add-Ins and Tools / Re: RTF: Restart Page Numbering
« on: November 05, 2009, 11:44:12 am »
It does reuire a new section - but set to re-start the page numbering. In the Template Editor - see:
Edit | Edit Sections &
Insert | Insert Break | Section

Do the same with the: Element::Diagram - section - tick it, but leave it blank to replicate: Package::Diagram.

If you are using Builds post 834 - you simply need to set the template to include the Section - Diagram::Elements - leave this blank to replicate - Package::Element.
Then so long as: F8 | Include All Diagram Elements in Report -  is checked this will render the diagram Elements.

Send an email to or see the support link 'Report a Bug' at the bottom of this page.

In answer to your questions:
1. Instead of setting the top document as a Master Document - leave the Master document - Tagged Value: RTFtemplate - option blank. In the first Model Document use the Package section (no child packages) and set the Package name on your header page (plus any Tagged Values - like author, company etc..
Alternately a recent build includes the option to set fields for "Project Constants" this can be set for the title etc.
2. I assume you are refering to a table "Revision history" - best to keep a Linked Document (with these tables) on the Root package and report this along with the title.
3. Could you send through to suport an example of this.
4. Again Linked Documents on Packages can be used for this - rather than a Document Artifact.
If you do take to Geert and Midnights suggestions - there is VB 6 Automation code to write to MS Word SDK available as a starter - see:

Basic Flow and Alternate flow are both: Secnario.type, so they are listed from the same field Element:: Scenario.Type. Hence the can only be listed in one table.

There is code written in VB 6  available from:

From the downloadable code see the subs:
- DumpDiagram
- PasteDiagram
This is for generating documents in Word these can be saved as RTF.

Regarding reply#7 - The filtering is set permanently for each individual Template in the RTF editor: File | Document Options.  It is best to use this especialy for each Model Document.

Reply #8: It is necessary to use both the connector::target::element and the connector::Source::Element fields - what you are reporting are only the targets  - these can differ depending on how they were originaly set.

Reagrding your first point;  this option does work - I am not sure what you have done to get this.

Second Point: The Connector source and target both need to be displayed. It is best o use a table for this.

Pages: 1 ... 33 34 [35] 36 37 ... 40