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

Pages: [1] 2 3
Suggestions and Requests / Copy and Link
« on: November 08, 2018, 12:49:18 am »
A variation on the copy/paste full-structure-for-duplication would be useful in that it would create a dependency between each original and copied element. If the dependency type could be user-specified that would great but I'd be happy with <<copy>> or <<trace>> as a default.

Regards, Mark

I've searched the help and forum for what seems like a piece of basic functionality but not found anything. I'm using EA build 1309.

I am putting a hyperlink to a file on a server location into the linked document part of a model element. That works fine in EA.

When I create an html report the linked document appears with the hyperlink in it but the link does not work because it is corrupted by the html report output location being prepended along with an 0x7B. So my hyperlink in the linked document is

W:\Published Data\Systems Engineering\Reference Data\SE Process\notice to adopt 15288.1.pdf

which works fine in EA.

The html report output location is


and the hyperlink that appears in the html output is (with the "wrong" additions highlighted in red)


Is this a bug or am I missing a trick?

Thank you, Mark

General Board / Re: Sysml Nested ports in EA V14
« on: May 30, 2018, 05:56:30 pm »
Problem still there in 1421.

General Board / Re: Sysml Nested ports in EA V14
« on: May 23, 2018, 01:49:31 am »
I can get the parent port's child ports to show up in Interaction Points. I can tick them but they do not then appear on the diagram and the Visible flag remains False too. All it took to make the parent port appear was to tick it when the owning block was selected. EA1420.

Anyone know why the classifier of the property is not in t_object classifier_guid?

Bugs and Issues / Re: SysML Item Flow with item property
« on: August 30, 2017, 10:06:13 pm »
Indeed. I have raised a bug report asking that Item Properties, as well as Classifiers, can be added via Advanced/Information Flows ...

Uml Process / Re: How to use IBD and properties
« on: August 15, 2017, 01:10:36 am »
Hi Helmut,

Sorry for the delayed reply. (Other forums notify of replies automatically and I forget that you have to ask for it on this one).

Thank you for your reply. That does indeed work.

Kind regards,


Hi Helmut,

I am still seeing my problem in 13.5. I have raised a bug report (#17076634). The Sparx response so far is:

"There are actually two "direction" tags with different values for each FlowProperty of the port. One belongs to itself and the another is inherited from the FlowProperty of Block1. You can see both using the docked Tagged Values window (Ctrl+Shift+6). You can delete the first tagged value in the Tagged Values window. We confirm that it is being created by mistake."

My issue is not with what is being shown for port direction on a diagram, that seems to be OK, it is that there are local copies of the FlowProperties for the port and they have their own "direction" tagged value, with default direction (inout), as well as the inherited tagged value for direction.

In my first post I missed a step 4:

4) Select port / Structural Elements / Show Owned/Inherited / Select all

Kind regards,


Bugs and Issues / Re: SysML Item Flow with item property
« on: August 14, 2017, 05:28:47 pm »
There is a relevant diagram in the SysML spec in Table 9.2. In the box for ItemFlow, two options for showing ItemFlow between eng and trns are shown. The left-hand side shows a "bare" item flow called Torque which is a classifier. The right-hand side shows torque: Torque which is an Item Flow with an Item Property, torque being the item property. EA seems to only support the Item Flow shown by a classifier (on the left hand side) and not the Item Flow with an Item Property (right-hand side).

There is some descriptive text in paragraph of the SysML spec.

Bugs and Issues / Re: SysML Item Flow with item property
« on: July 31, 2017, 07:37:48 pm »
This is still a problem in V13. I am trying to implement the Water Distiller example in Chapter 16 of the Practical Guide to SysML book (Iss 2 so SysML 1.3). This is a showstopper as you can't create an Item Flow item than can be allocated to from an object flow. I want to be able to map between logical model object flows and physical model items flows, e.g. a real-world value like temperature in the logical model is represented by a sensor voltage in the physical model.

In Build 1309 I am doing the following:

1) Creating an InterfaceBlock with FlowProperties;
2) Giving the FlowProperties directions (in or out);
3) Creating a Block with a port typed by InterfaceBlock;

The issue is that the port's FlowProperties' direction are set to inout (default) not the values specified in 2).

This is similar to,30594.msg222869.html#msg222869


Thank you KP. I fell into the trap of thinking the Preferences would be under the Configure ribbon along with Model options.

Just opened a diagram that has not been opened for a while. It seems throughout the model that the behavior is no longer showing on CallBehavior actions (those with a pitchfork).

I can't find an option or setting to control this. Has anyone else seen this and know what is going on? I am using EA 13.0.01309.


 |   actionname       |
 |   : CBname          |

now looks like (can't show pitchforks in bottom-right corner)

 |   actionname       |
 |                            |

Uml Process / Re: How to use IBD and properties
« on: May 04, 2017, 09:45:02 pm »

Connector Type on a ibd.
- Make a bdd with two blocks and a named association
- Make the associated ibd with the two parts derived from the two blocks of the bdd.
- Make a connector between parts
- Right Click on the connector, Advanced, Set Connector type
-- You can choose the name of the association of the bdd


I have been trying to do the above. However, when I right-click on a connector & select Advanced I do not see "Set Connector Type". Instead I see "Change Type ..." which just offers up UML connector types, not a means to navigate to an association type. I have carried out all the preceding steps. This is in EA13.

Am I missing something or has the UI changed in this respect?



Bugs and Issues / Re: EA13 crashing when saving diagrams
« on: April 28, 2017, 02:08:56 am »
On one project the Project Integrity repair seemed to delete all of the root package's baselines. The log of errors did not mention baseline and the _recovered_ package was empty.

Is that an expected behaviour? The help for Project Integrity doesn't mention baselines.

I baselined the root package on another project, ran Project Integrity repair and it didn't delete the baseline.

Pages: [1] 2 3