Messages

1

General Board / Re: Display custom tag values on RTF Report

« on: July 20, 2013, 04:18:01 am »

One additional thing that I noticed is that my older objects (where the Tagged Values window shows all the tagged values in a single list) still work ok. It is the newer objects (with tagged values grouped by stereotype) that don't work.  

2

General Board / Re: Display custom tag values on RTF Report

« on: July 20, 2013, 03:28:02 am »

This problem was fixed but seems to be broken as of version 10. Does anyone know of a solution?

3

General Board / Re: Display custom tag values on RTF Report

« on: October 19, 2010, 03:52:20 am »

Thanks for the reminder Graham. I received a response from Sparx support but forgot to update the forum.

They advised me that they have referred the problem to their development team and they're hoping to include a fix in the forthcoming release of build 864.

4

General Board / Display custom tag values on RTF Report

« on: September 01, 2010, 09:41:31 pm »

Does anyone know how to include custom tagged values in an RTF report (i.e. tagged values that were created in an MDG technology using the Tagged Value Connector)?

When I populate my tagged value, the Tagged Values tab displays the name of the linked element. However, when try to display this on a report using ValueOf, the linked element's GUID is displayed in the report instead of the name of the linked element.

Thanks,

Fred

5

General Board / Re: RTF Reporting Questions

« on: September 22, 2011, 10:48:52 pm »

You could do this by creating the report through scripting using the DocumentGenerator class. It is a bit of work but I create most of my reports that way because it is the only way to get the level of control that I need.

To get the elements on a diagram, use the DiagramObjects collection. This will give you the ElementIDs, which can be used to access the elements. This would also make it possible to report based on element type or other criteria.

6

General Board / Re: Landscape RTF reports  from DocumentGenerator

« on: August 31, 2011, 10:14:28 pm »

Thanks Skiwi,

Even when I follow your instructions below, I cannot produce landscape documents from a script using the DocumentElement method of the DocumentGenerator class.

Have you been able to do this?

When I submitted a support request to Sparx, here was there answer:

We have confirmed that this is an issue, the Document Generator treats all documents as being Portrait.


Fred

7

General Board / Re: Landscape RTF reports  from DocumentGenerator

« on: August 25, 2011, 09:44:47 pm »

I have received confirmation from Sparx that this is an issue. No estimate on when it will be resolved.

8

General Board / Landscape RTF reports  from DocumentGenerator

« on: August 25, 2011, 04:40:22 am »

Does anyone know how to specify landscape layout when creating RTF reports with scripts using the DocumentGenerator class?

All my reports come out in portrait mode even when the RTF template used specify landscape. There does not appear to be any methods of the DocumentGenerator class to change the mode.

9

General Board / Re: Keywords

« on: August 30, 2011, 09:50:41 pm »

Thanks Luis!

The "tag" attribute did the trick. I had been looking for a property called "keywords".  

Fred

10

General Board / Keywords

« on: August 27, 2011, 04:36:32 am »

Does anyone know how to access element keywords from scripts?

11

General Board / Re: RTF Template and child elements

« on: August 12, 2011, 09:36:21 pm »

If you remove the content from the child element section, the child elements will be documented just like their parents.

See this help topic:

http://www.sparxsystems.com/enterprise_architect_user_guide/9.0/reporting/rtftemplateeditorchildsect.html

12

General Board / Help with writing Transformations

« on: August 15, 2011, 11:33:24 pm »

I am struggling a bit with writing Transformation templates. In general, I am wondering if there are any better or more detailed descriptions and examples of how to write them than is found in the help?

Here is my specific question. I am trying to transform a Conceptual Data Model to a Logical Data Model. As part of the transformation, I want to change the stereotype for all attributes to “Attribute - Logical Data Model” except for attributes that currently have stereotypes of “Primary Key”, which should remain the same.

My code is below. The result I am getting is that all attributes are changed to “Attribute - Conceptual Data Model” (i.e. only the “else” code runs). Does anyone know what I am doing wrong?

Thanks,

Fred

Code: [Select]

Attribute
{
      %TRANSFORM_REFERENCE()%
      %TRANSFORM_CURRENT("stereotype")%
      %if attStereotype == "Primary Key"%      
            stereotype="Primary Key"
      %else%
            stereotype="Attribute - Logical Data Model"
      %endif%
}


13

General Board / Re: Different view of a business process?

« on: August 09, 2011, 03:48:28 am »

You could use the Diagram Filters feature to implement option 2.

14

General Board / Re: Linked Elements in Activity Partition

« on: August 03, 2011, 10:11:07 pm »

I don't see any of the containment relationships (in EA 9.0.908) between an Activity Partition and its contained elements appearing in either the Project Browser or Traceability windows.  Is there an option somewhere to turn this on?

I don't think it is an option. If you move the contained elements around within the partition, do you see the partition border change from a solid line to dashed? When this happens, it indicates that the "owned by" relationship has been established. I haven't tried all element types but this seems to work for the typical ones such as Activity.

15

General Board / Re: Linked Elements in Activity Partition

« on: August 02, 2011, 10:41:13 pm »

I also find that this is a problem.

You can establish an "owned by" relationship by moving the element within the partition until the partion border appears dashed. However, that relationship is not visible everywhere. It is visible in the Project Browser and Traceability windows but not in the Relationships window or the Related Elements (LInks) tab of the element properties window.

One final caution about using this method is that elements can only have one owner (makes sense). If you re-use an element on multiple diagrams, it will only have an "owned by" relationship to the last partion that it was linked to.