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.


Topics - Geert Bellekens

Pages: 1 2 [3] 4 5 ... 14
31
According to http://sparxsystems.com/enterprise_architect_user_guide/12.1/automation_and_scripting/connector2_2.html the EA.ConnectorClass should contain a property called AssociationClass, but I get a compile error when trying to use that.

Bug reported

Geert

32
Since one of the newer versions, if you add a state machine to class it adds the statemachine, adds the state machine diagram, but then it also adds the statemachine to the diagram looking like a diagram reference.

Why is this happening all of a sudden? The feature was working fine as it was.

If it ain't broke, don't fix it!
I'll report it as a bug

Geert

33
I have a client who would like to have a specific stereotype for the Association Class, but combine that with another stereotype for the association itself.

I created a stereotype extending AssociationClass, but now both the Association as the AssociationClass get the same stereotype (and the same tagged values, of which I only want one set)

I haven't found a way to tell EA that the stereotype for the association should be «a» but the stereotype for the association class should be «b»

Any idea's (using standard MDG approach)?

Geert

34
When making an BPMN2.0 Business process Diagram you typically create the BusinessProcess element and have a diagram nested under that element.
Now typically when creating things on a diagram these things are located at the same place as the diagram.
So if I add something on the diagram it will be nested under the Business Process element.

That is true for everything except for BPMN2.0 Messages. They get moved out of the business process to be on that same level.
I don't know why that is, and if there is a good reason for it, but that in itself wouldn't be a big problem for me.

Now because we want to depict Messages on a diagram more then once (we put the message icon next to the MessageFlow to make navigation to the composite diagram of the message easy) we use Message Instances.
I created a stereotype Message for Object as well (with a shapescript that makes it look like a BPMN Message) so our Message instances look like messages. (a script takes care of the composite diagram for the instances)

The problem is that EA moves my Message Instances out of the Business Process element as well.

So please, if possible remove the strange behaviour that moves messages out of the business process.
If that is not possible then at least check the type of the element (Class) as to leave objects alone when moving.

Thanks

Reported as bug.

Geert

35
Bugs and Issues / Extending BPMN stereotype doesn't work (properly)
« on: April 22, 2016, 04:53:37 pm »
My client needed a special type of BPMN 2.0 messages with some extra information -> Functional Information Stream
So what I did was create the stereotype «FIS» that specializes BPMN 2.0::Message.

So far so good, I added my extra attribute and a shapescript to differentiate «FIS» from a regular Message

This all worked fine up until we needed to model messageFlows. The tagged value messageRef only accepts BPMN2.0::Message stereotypes, but doesn't allow to select my «FIS» stereotype (which IS a BPMN2.0::Message)

So bye bye elegant solution, back to adding random tagged values with a script to a subset of all BPMN Messages  :(

Reported as bug.

Geert

36
Suggestions and Requests / Association classes in Schema Composer
« on: April 21, 2016, 05:11:30 pm »
If I select an association that is linked to an Association Class, I would expect the Schema Composer to recognize this and add the Association Class to the list of classes so I could select attributes from that Association Class.

Feature request sent.

Geert

37
Sometimes it would be useful to apply a diagram filter when reporting a diagram in an RTF template.

We have a case where monitoring items are added to business process diagrams, but we don't want the business process documents to be impacted by the monitoring items.
Using diagram filters we can filter the monitoring items out of the diagrams, but unfortunately there's no facility to apply those diagram filters when generating a document.

Geert

38
Bugs and Issues / Script fragment error only on first try
« on: February 26, 2016, 06:28:50 pm »
I have  a weird problem that I can't seem to get my head around.

I'm using RTF templates with some script fragments. Now usually the first time I generate a document I get an error (or more) and some of the content from the script fragments has not been generated. Not all of it mind you. Some parts (using the same script fragment template) generate just fine, but other don't.

When I try that a second time it (almost always) generates perfectly fine.
What do they say again about someone who does exactly the same thing but expects a different outcome ???

It feels like the script engine has to "warm up" before it is ready to really do the job. :-\
Running the script manually always works just fine.

Anyone had the same problem, or has an idea how to solve it?

Anyway here's the script I use in the script fragment

Code: [Select]
'[path=\Projects\Project A\Template fragments]
'[group=Template fragments]
option explicit

!INC Local Scripts.EAConstants-VBScript
!INC Atrias Scripts.Util

'
' Script Name:
' Author:
' Purpose:
' Date:
'
function MyPackageRtfData(packageID, tagname)
dim package as EA.Package
dim element as EA.Element
set package = Repository.GetPackageByID(packageID)
if not package is nothing then
set element = Repository.GetElementByGuid(package.PackageGUID)
if not element is nothing then
MyPackageRtfData = MyRtfData (element.ElementID, tagname)
end if
end if
end function

function MyRtfData (objectID, tagname)

dim xmlDOM
'set  xmlDOM = CreateObject( "Microsoft.XMLDOM" )
set  xmlDOM = CreateObject( "MSXML2.DOMDocument.4.0" )
xmlDOM.validateOnParse = false
xmlDOM.async = false

dim node
set node = xmlDOM.createProcessingInstruction( "xml", "version='1.0'")
    xmlDOM.appendChild node
'
dim xmlRoot
set xmlRoot = xmlDOM.createElement( "EADATA" )
xmlDOM.appendChild xmlRoot

dim xmlDataSet
set xmlDataSet = xmlDOM.createElement( "Dataset_0" )
xmlRoot.appendChild xmlDataSet

dim xmlData
set xmlData = xmlDOM.createElement( "Data" )
xmlDataSet.appendChild xmlData

dim xmlRow
set xmlRow = xmlDOM.createElement( "Row" )
xmlData.appendChild xmlRow

dim element as EA.Element
set element = Repository.GetElementByID(objectID)

dim formattedAttr
set formattedAttr = xmlDOM.createAttribute("formatted")
formattedAttr.nodeValue="1"

dim descriptionfull
descriptionfull = getTagContent(element.Notes, tagname)

dim xmlDescNL
set xmlDescNL = xmlDOM.createElement( "DescriptionNL" )

xmlDescNL.text = getTagContent(descriptionfull, "NL")
xmlDescNL.setAttributeNode(formattedAttr)
xmlRow.appendChild xmlDescNL

set formattedAttr = xmlDOM.createAttribute("formatted")
formattedAttr.nodeValue="1"

dim xmlDescFR
set xmlDescFR = xmlDOM.createElement( "DescriptionFR" )
xmlDescFR.text = getTagContent(descriptionfull, "FR")
xmlDescFR.setAttributeNode(formattedAttr)
xmlRow.appendChild xmlDescFR

MyRtfData = xmlDOM.xml
end function

'msgbox MyPackageRtfData(3357,"")
function test
dim outputString
dim fileSystemObject
dim outputFile

outputString =  MyRtfData(62899, "definition")

set fileSystemObject = CreateObject( "Scripting.FileSystemObject" )
set outputFile = fileSystemObject.CreateTextFile( "c:\\temp\\NLFRtest.xml", true )
outputFile.Write outputString
outputFile.Close
end function

'test

39
Bugs and Issues / newlines dissappeared from script fragment
« on: February 26, 2016, 12:59:42 am »
Since version 12.1.1227 or 12.1.1228 ALL newlines are being stripped from script fragments that return formatted text.
In version 12.1.1226 it was still OK.

Bug reported.

Geert

40
Bugs and Issues / Setting up automatic checkout of shared license
« on: January 18, 2016, 07:47:48 pm »
We tried to setup some clients for automatic checkout of shared licenses, but apparently there's an error in the deployment whitepaper with regards to the registry settings needed to change.

In the whitepaper it says to set the registry key
"AutoCheckoutEx"=hex:1a,00,00,00

Whereas my tests revealed that it started working when we set the key to
"AutoCheckoutEx"=hex:02,00,00,00

I've sent an email to support about this.

Geert

41
Bugs and Issues / Navigability information lost on associations
« on: January 13, 2016, 08:00:44 pm »
When I change the navigability of one of the ends of an association EA correctly changes the arrow of the associations to show the updated navigability.
Until I close and re-open the diagram. Then suddenly the navigability information is lost ???
I can now only change the navigability by changing the "direction" on the association level.

This seems to happen in v12.1 (1225) but not in v12 (1215)

Reported as bug

Geert

42
I have a very simple example model. A bi-directional association between Class1 and Class2
Class1[1..1]<------->[1..*]Class2
Now I want to generate an XML Schema for this.
I would expect Class1 to reference Class2, and vice-versa, Class2 to reference Class1
But for some reason I only get Class1 that references Class2, but not the other way around.
This is what I get
Code: [Select]
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Class1" type="Class1"/>
<xs:complexType name="Class1">
<xs:sequence>
<xs:element name="Class2" type="Class2" minOccurs="1" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:element name="Class2" type="Class2"/>
<xs:complexType name="Class2">
<xs:sequence/>
</xs:complexType>
</xs:schema>

And this is what I was expecting
Code: [Select]
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Class1" type="Class1"/>
<xs:complexType name="Class1">
<xs:sequence>
<xs:element name="Class2" type="Class2" minOccurs="1" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:element name="Class2" type="Class2"/>
<xs:complexType name="Class2">
<xs:sequence>
<xs:element name="Class1" type="Class1" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
Anyone know how to massage EA into getting it to produce the latter?

Thanks

Geert

43
Bugs and Issues / Cannot use two Schema Composer addins together
« on: January 07, 2016, 03:42:16 am »
Apparently you cannot have two working Schema composer add-ins at the same time.
I first activated Rodrigo's example, which worked fine.
Then I activated mine, and suddenly "Rods Canonical Model" is no longer available and only my schema set is available next to the standard schema sets.

I'll report the bug.

Geert

44
Bugs and Issues / Schema composer automation broken in v12.1
« on: January 06, 2016, 06:32:02 am »
I'm writing (or trying to anyway) an add-in to extend the Schema Composer.
I checked the documentation (after I finally found it), and Rodrigo's example, but for some reason I couldn't get the import formats to appear when pressing the Generate button.

After trying the the SC Addin example from the program files folder, and the example downloaded from Rodrigo's site I saw that both of them didn't work either.

I rolled back from v12.1.1225 to 21.1.1224 but still no luck.
After rolling back to v 12.0.1214 it started working again.

I'll report it as a bug. I must say I'm off to a very bad start for the first day on my new project  :-\

Geert

45
I was just looking for the API documentation in order to create a Schema Composer add-in, so naturally I looked at the Automation and Scripting Chapter in the Manual.
Much to my surprise I didn't find anything at all :o

Looking further I a little bit of documentation in the Schema Composer Chapter

@Roy, can you please set this straight?

There's also an error in the operation definition:

Code: [Select]
bool
EA_IsSchemaExporter (EA.Repository, ref string displayName);

The first parameter doesn't have a name.

Thanks

Geert

Pages: 1 2 [3] 4 5 ... 14