Messages

31

Automation Interface, Add-Ins and Tools / Set color to an element for appearance in all the diagrams

« on: September 04, 2020, 03:52:17 am »

i'm trying to set a background color on an element object, in order to give this element the same color on each diagram it appears.

      activity.SetAppearance 1,0,RGB(35, 169, 242)
      activity.Update()

But because this doesn't work, ik was wondering I shouldn't use a diagramObject instead of an element?

32

Automation Interface, Add-Ins and Tools / Re: Edit StereoTypeEx in database

« on: September 03, 2020, 05:50:44 pm »

The plain stereotype name is in t_object.stereotype. The FQN is in t_xref.description of the record which has client=ea_guid.

q.

Thanks qwerty

33

Automation Interface, Add-Ins and Tools / Re: Can't drop elements on a diagram

« on: September 02, 2020, 04:00:53 am »

Thanks Geert and Qwerty to make this clear.

34

Automation Interface, Add-Ins and Tools / Re: Can't drop elements on a diagram

« on: September 01, 2020, 05:14:10 pm »

Not sure where you read that about the Refresh()

What it does is reload the EA.Collection from the database.
Not needed, unless you want to iterate the same collection after adding or removing items.

Geert

In the example scripts:

      dim testElement as EA.Element
      set testElement = elements.AddNew( "Login to Website", "UseCase" )
      testElement.Stereotype = "testcase"
      testElement.Update()
      thePackage.Elements.Refresh()

But I thought that is was necessary to put the changes to the database or refresh the project browser

35

Automation Interface, Add-Ins and Tools / Re: Can't drop elements on a diagram

« on: September 01, 2020, 04:16:11 pm »

Mathias,

You might need to create the object type explicitly and then set the stereotype

Code: [Select]

dim startEvent as EA.Element
set startEvent = poolElement.Elements.AddNew("Start", "Event")
startEvent.StereotypeEx = "BPMN2.0::StartEvent"
startEvent.Update()
Geert

PS. The lines in your current to set the stereotype, and to Refresh() are probably not needed.

Tanks Geert,

I always read that is was necessary to refresh the parent where you create the element, this can be a package or another element. But this is not necessary? even if you create (child) diagrams?
 

36

Automation Interface, Add-Ins and Tools / Re: Can't drop elements on a diagram

« on: September 01, 2020, 02:11:43 pm »

The BPMN events extend two different UML metaclasses, it sounds like your script has created one using the other one from what you normally use.

I queried the element object type with an external database viewer, and it seems I created a 'Node' instead of an 'Event'. When I query the element with the model search, the event is an 'Event'.

         dim startEvent as EA.Element
      set startEvent = poolElement.Elements.AddNew("Start", "BPMN2.0::StartEvent")
      startEvent.Stereotype = "StartEvent"
      startEvent.Update()
      poolElement.Elements.Refresh()

37

Automation Interface, Add-Ins and Tools / Edit StereoTypeEx in database

« on: August 31, 2020, 11:49:27 pm »

In what table can you modify the StereoTypeEx for an object?

38

Automation Interface, Add-Ins and Tools / Can't drop elements on a diagram

« on: August 31, 2020, 08:43:24 pm »

I created a BPMN2.0::StartEvent through a script and add it to a pool. In my project browser the StartEvent is created within the pool, but when I try to drag it to my diagram, I got the following error message:

When dropping embedded elements (Ports, Object Nodes, etc.) on to a diagram, you must drop them on their correct owner. For embedded elements fixed to a parent edge, drop them near the desired edge

The activities that I created in the same way, are perfectly possible to drop onto the diagram in and outside the pool.

The StartEvent is only dropable on the edge of the pool, and then appears a blue startEvent right on the border/edge of the pool element. Very strange...

39

General Board / Re: Importing WSDL

« on: July 10, 2020, 06:16:25 pm »

Version 14

When I import a WSDL to a package, sometimes the stereotype <<XSDschema>> is displayed on the package, when I import that same WSDL again, the stereotype is not displayed.

40

General Board / Importing WSDL

« on: July 10, 2020, 06:02:42 pm »

We tried to import a WSDL to our repository, sometimes EA adds the stereotypes to a folder, and sometimes EA doesn't...

Has it something to do with database issues?

41

Automation Interface, Add-Ins and Tools / Re: MS Word crashes after generating document

« on: April 21, 2020, 05:03:55 pm »

Solved!

It was caused by a heading conflict.

42

Uml Process / Re: Link between project requirements and use case diagrams

« on: April 20, 2020, 05:04:43 pm »

Hi

The best way to do this, is to drag and drop the requirements into the Use Case when is open in the Use case Diagram.
It gets link right away.
So when you run the Documentation or your Requirement Relationship Matrix it will show linked.

I published an eBook to do all this and much more at Leanpub.com

https://leanpub.com/uml-erpworkshop

Thx I'll take a look.

For now, I used composite diagrams but that isn't a preferred solution.

43

Automation Interface, Add-Ins and Tools / Re: Quality of images in report is poor

« on: April 20, 2020, 05:02:50 pm »

15 and 14. Today I will create all my templates again, hoping that that will solve the problem.

44

Uml Process / Link between project requirements and use case diagrams

« on: April 17, 2020, 10:32:37 pm »

I'm busy with the setup of a repository in order to generate documentation.

For each project we have a separate project package. The starting point are requirements. We have a package called 'Requirements', with underneath four child packages (Functional Requirements, Non-Functional Requirements, Architectural Requirements and Security Requirements). In each of that packages there's a requirement diagram and a sub package with the requirement elements.

Each project can have multiple use case diagrams, so my question is: what's the best practice to link those requirements to de use case diagrams? Or better, how can I link my 'project' to the requirements and the use case diagrams? What's the best starting point to generate documentation? The project folder, or a diagram?

45

Automation Interface, Add-Ins and Tools / Re: Quality of images in report is poor

« on: April 17, 2020, 08:49:54 pm »

I doesn't help.

We use EA in a Citrix VDI console, could that cause the problem?