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

Pages: [1] 2 3 ... 40
Bugs and Issues / Re: Behaviour of action pins
« on: March 23, 2018, 07:24:21 pm »
Hi Uffe,
I use activity parameters and action pins quiet often and the situation is even worse.

In addition to what you have written, I often use unnamed but classified parameters and how those are shown as pins varies from version to version (currently I have to add a space character to the pin name to get “:classifier” shown correctly) , what however is some kind of indication that Sparx at least try to improve something.

Hi Simon,
it seem I have more privileges than you!

Just create two state machines let’s say “Main” and “Sub”.
Insert a state in Main (e.g. State1).
Use context menu “New Child Diagram”/”Select Composite Diagram” on State1 to select the diagram under Sub.
And "voila”!

This works as long as you have not assigned a classier to State1, and from my opinion this should work if a classifier is assigned before as well (just because I belief this is a navigation feature).

Oh my god! Regard it as a feature!

If you regard it as a bug, you have lots of bugs in this direction since years.
If you would fix them, my navigation facilitations for users would be gone.

From my perspective, an element having a component diagram, and double clicking on element to open any diagram are two distinct things.

Just realized that this problem has gone in V 14 Beta.

To your question regarding special properties:
You do not need special properties, standard packages are enough

The security functionality you refer to, is what you need (at least from my perspective)

After having assigned a state machine via Instance Classifier to a state, it is not anymore possible to select a Composite Diagram to this state.
Remark: Same problem exist for actions later made to callBehavior
Seen in Build 1310 and others


General Board / EA V14 Beta; What about SysML1.4?
« on: March 13, 2018, 12:59:33 am »
Today I had a first look on EA V14 Beta.
I realized that SysML1.4 is missed. Will SysML1.4 not be supported anymore?

Bugs and Issues / Link to Element Features not working on properties
« on: February 28, 2018, 12:31:18 am »
When using “Link to Element Feature” in field “Feature Type” you can select value “properties”. However in the Feature list below not properties are listed even if the element has properties. So it is not possible to link properties at all.


General Board / Re: Virtual Documents and RTF Templates
« on: February 16, 2018, 08:22:16 am »
Ok! Now I found my problem. I assigned template fragments rather than templates to the model reports and those seem to be ignored and the system "Model Report" template is used as default instead.

General Board / Virtual Documents and RTF Templates
« on: February 16, 2018, 04:25:42 am »
Can anyone enlighten me, how I can use RTF templates for virtual documents. Up to now I did only use virtual documents for html.

I have a rtf-template that works fine on packages.

Now I created a <<report package>> having one <<model document>>.
My first try was to add a tag RTFTemplate to my <<report package>> manually and setting the value to point to my working template.

As a result I got a cover page as expected but all the content was rendered with the system “Model Report” template. I fiddled around with both RTFTemplate tags (<<report package>>, <<report package>>), but whatever I do I get my stuff only rendered with chatty “Model Report”!?! :'(

One possible way could be:

-Select the 6th package
-Right click to open context menu
-Select Documentation/Generate Report Options and click “Exclude Package from Generated Reports”

General Board / Re: Share links on elements and diagrams
« on: January 30, 2018, 01:35:53 am »
What do you mean with "the other documents, sources and so on". Are those things in your EA repository or is it something outside?

Hi RWHurra,
there are so many ways how you can characterize the level of your requirements.

E.g. you can just put each level to a own package, or you can use a stereotype, or you can use a tagged value, or you can use a <derive> relationship, or you can use a….
There is no best approach, you need to now some approaches and you have to decide what fits best to your needs.

Thinking about requirement instances typically is not a good idea.
To get a requirements library to be used in other projects can also published this lib in several ways (without having a best approach). E.g. you can do that by XMI export/import, by a version control system, or by the EA-asset service (all in fact are based on xmi).

General Board / Re: Another question about SQL queries of diagrams
« on: January 29, 2018, 08:19:39 pm »
This issue is continued here:,39168.0.html
So I try to close this one!

Thank you Simon,
t_diagram' as CLASSTABLE makes all work.

I suggest that you also consider that magic thing in the user manual.

Pages: [1] 2 3 ... 40