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 - Helmut Ortmann

Pages: 1 ... 44 45 [46] 47 48 ... 62
676
Bugs and Issues / Re: No menu entry for Schema Generation
« on: August 15, 2013, 08:01:14 pm »
Hello,

check View, Workspaces and Commands. Make sure that all commands are enabled.

Helmut

677
Bugs and Issues / Re: [BPMN] Selecting all (Control) flows on a mode
« on: August 12, 2013, 10:39:32 pm »
Hi Jef,

you can't select all connectors.

You may write an addin or script to do the job.

Helmut

678
Bugs and Issues / No return message(acknowledgement) to a bug report
« on: August 13, 2013, 05:37:16 am »
Hello,

I issued a bug report on Sunday and today. I got no acknowledgement. In the past I got an acknowledgement.

SPARX may improve their message by returning the content of the bug report. I don't want to copy each detail on my hard disk.

Helmut

679
Bugs and Issues / Field length of return Fragment Scripts is limited
« on: August 08, 2013, 05:42:14 am »
Hello,

I used a fragment script to output *.h files in the rtf/pdf documentation.
If the *.h file is to large (around 300 lines) I get the error message 'invalid field content' or so.

I assume that the length of the returned value is restricted by count of characters or lines.

The workaround is: Make more than one fragment template to split the output in parts below of 200 lines.

Thanks,

Helmut

680
Bugs and Issues / Re: Ran out of memory during rtf as PDF generating
« on: August 07, 2013, 07:58:54 pm »
Hello Geert,

thanks. The workaround works. The drawback is that in the *.pdf file the bookmarks are missing.

Helmut


681
Bugs and Issues / Ran out of memory during rtf as PDF generating
« on: August 07, 2013, 05:54:13 pm »
Hello,

if I generate large RTF documents as *.PDF the following happens:
  • Pop Up: Ran out of memory
  • Parts of the document are missing
  • In short no useful PDF document

The exact behavior differs from PC to PC.

It's easy to reproduce:
Try to document the whole EA example model as PDF. One PC runs out of merory. The other genereted without error message but parts of the documentation are missing in PDF.

I found the error message in the forum. No solution or workaround.

If I generate it as *.rtf it works fine.

Helmut


682
Bugs and Issues / Re: rtf generation no short text for requirements
« on: July 29, 2013, 10:30:19 pm »
Hi,

was my fault.

Helmut

683
Bugs and Issues / rtf generation no short text for requirements
« on: July 29, 2013, 10:28:05 pm »
Hi,

I'm missing the field short text in the requirements.

Helmut

684
Bugs and Issues / rtf fragments destroy content of operations
« on: July 29, 2013, 07:09:01 pm »
Hi,

I created a document by copying it from the basic template. Everything runs fine.

The I added in the template: Insert Template (I used a SPARX example template to add)

After adding the template the attributes- and operation content shows only the field names instead of the field values.
Connectors on the other hand are ok.

The behavior is independant of the inserted template and of the position in the document template. I can also use other document templates. The same behavior.

EA: 1008

Thanks for your help,

Helmut

685
Bugs and Issues / Re: Toolbox diagram. "Save as profile" not showing
« on: July 18, 2013, 09:22:45 pm »
Hello,

last entry in View.

Helmut

686
Bugs and Issues / Re: No parameters in SysML simulation configuratio
« on: July 16, 2013, 04:31:35 am »
Congratulation!

I have a faint memory. Thanks for your hint.

Helmut

687
Bugs and Issues / Re: No parameters in SysML simulation configuratio
« on: July 15, 2013, 07:54:32 pm »
Hello,

have you:
  • created the parameter of type property and connected them
  • create the element script


Well I have a working example. But it was some time ago when I worked with parametrics. I firstly also had problems with input/output parameters.

If you are interested I can send you my example. Just drop me a note. Starting from a working example often makes things easier.

Helmut


688
Bugs and Issues / Re: Incompatible SQL Server types when running SV-
« on: July 08, 2013, 03:21:50 pm »
Hello Peter,

I don't know the SV-6 query.

If you have some experiences with SQL you can solve the problem by yourself. The faulty SQL string and the complete error message you can see at:

%APPDATA%Sparxs Systems\EA\DBError.txt

If you put the SQL string into this Forum someone can help you. It looks like a missing cast to make the two different SQL Server types compatible.

Best regards,

Helmut


689
Bugs and Issues / Re: SysML 1.3 Aggregation
« on: May 27, 2013, 10:38:03 pm »
Hi,

@RobCDeJong
thanks for clarification. I wasn't correct.  In the following I try to explain it for EA.

according to SysML 1.3 page 65 a property may have the stereotypes:
  • <<DistributedProperty>>
  • <<ParticipantProperty>>
  • <<ConnectorProperty>>
  • <<>> No Stereotype it's simply a property

In my opinion the compartments 'parts' and 'references' express the usage of the property (page 54). In EA this is "isReference=true/false" of the property.

In EA:
  • If you use an Association or Reference Association 'isReference' of the Property is true. It's visualized in the reference compartment.
  • If you use a Composition or PartAssociation 'isReference' of the property is false. It's visualized in the properties compartment. In my opinion this isn't according to SysML 1.3

In my opinion there is no explicit Property of type part (it's in fact a compartment and the kind of usage).

I agree that the <<ParticipantProperty>> is part of an association class (thanks for your advice).

I hope that was it. Please check once more with your expertise.

Thanks,

Helmut




690
Bugs and Issues / Re: SysML 1.3 Aggregation
« on: May 24, 2013, 11:47:14 pm »
Hi,

in SysML 1.3 only properties with different stereotypes exist. The property <<ParticipantProperty>> is equal the former part. Parts don't exists in SysML 1.3.

Just drag the <<ParticipantProperty>> from toolbox to the internal block diagram.

If you have the wrong property type set or reset:
- <<ParticipantProperty>>
- isReference = true (advanced properties), if you have a reference
- isReference = false (advanced properties), if it's the original/defining part/property

The EA behavior of auto generating the correct <<stereotyp>>, isReferenced by drag&drop and composition isn't always what you would expect. But by simply correcting <<stereotype>>,IsReference you have a work araund.

Kind regards,

Helmut

Pages: 1 ... 44 45 [46] 47 48 ... 62