Topics

1

Bugs and Issues / Timeout on SQL search query

« on: October 18, 2018, 07:11:17 pm »

We are using an SQL Server backend and one of our export searches returning a timeout after a while.
Does anyone know if you can somehow increase the timeout?
When running the same query directly in SQL Server Management Studio we don't get a timeout.

I know I can probably improve the performance of the query by rewriting it, but that is not what I'm looking for.
Optimizing the query would take a non-trivial amount of time, and since it's something we run only once every couple of months, we don't care if it takes 10 minutes to execute.

The query is a bit too long to post here (34.000 characters, 508 lines, the forum only allows 20.000 characters per post)

Thanks

Geert

2

Bugs and Issues / «trace» relation has changed type from Abstraction to Dependency

« on: October 11, 2018, 10:39:19 pm »

When I create a «trace» relation in v12.1.1230 I get a connector of type Abstraction with stereotype «trace»
When I create the exact same «trace» relation in v14.1.1427 I get a connector of type Dependency with stereotype «trace»

WTF!

Who?/Why?/What?

So now we are getting a nice mix of abstractions and dependencies in our models.
Not to mention the countless queries that are now broken, and a number of add-ins that depend on this relation being an Abstraction.

Was this an intentional change (I didn't see anything about it in the release notes) or a mistake?
In case of the latter I hope it gets rectified real soon.

Geert

PS. I'm not arguing Abstraction is better somehow than Dependency.

3

General Board / Automatically maintain users from AD group

« on: September 11, 2018, 05:03:42 pm »

In the release notes for version 14.1 I see this:

- Added option to automatically maintain the list of available users based on Windows Active Directory or OpenID groups

But I can't seem to figure out how this automatic function works.
Surely they can't mean that you can now press a "sync" button can they? That wouldn't count as automatic for me.

What I'm expecting from this is that I now only once have to set the link between the AD groups and EA groups and that's it. No more adding/removing users of users anymore. (Just like all the other products that integrate with AD) Am I expecting too much?

Geert

4

Bugs and Issues / EA 14 bug: Color and appearance when saving UML profile from package

« on: September 10, 2018, 08:44:12 pm »

V12.1: When saving a UML profile from a package you could select the checkbox "Color and Appearance" to save the default appearance of an element in the UML profile.

V14(.1): The option to save Color and appearance is only available when saving a UML profile from a diagram (although the menu option is still called "save package as UML profile"


I can somehow understand the reasoning behind the change, but it was working fine before when using the default appearance (which is an attribute of the element, not of a diagramObject). Why change? Now I save all my profiles from their packages, except for the UML profile, for which I have to select the diagram.

Geert

5

Automation Interface, Add-Ins and Tools / Redefine toolbox for other MDG technology

« on: September 10, 2018, 07:01:00 pm »

Context:

My users are doing modelling Archimate Business Processes and linking them to Archimate Business Objects. The use
- Business Process
- Business Object
- Flow
- Some of my own Stereotypes extending standard Archimate elements.

They don't need any of the other Archimate element/connector types, and I don't even want them to.

Question:
Is there a way to link the existing Archimate Business Diagram to a toolbox of my own?
I know how to do it with the standard UML and Extended toolboxes, but hat process doesn't seem to work with MDG diagram types such as Archimate.

Thanks

Geert

PS. If all else fails I'll make a new diagram type in my MDG and change the stereotype all of the standard Archimate Business Diagrams to my new diagram stereotype, but I would prefer it to work on standard Archimate diagrams.

6

Bugs and Issues / Toolbox with extended stereotypes

« on: September 10, 2018, 04:30:16 pm »

I'm having issues building a toolbox for extended stereotypes.

The help page says to create a generalization between the stereotype and the metaclass that represents an existing stereotype.

I did as instructed, and then I tried to create a toolbox for my stereotype using the profile helper. I use the button "Add" and select my stereotype, but then nothing happens.

In previous versions of EA you had to create two connectors. One generalization to the existing stereotype, and one extend relation to the base metatype.
As an experiment I tried this and it magically made it work.

Does anyone have similar experiences? Am I doing something wrong, or is there a bug in the profile helper for toolboxes.

Geert

7

Automation Interface, Add-Ins and Tools / UML profile example (v14 flavor)

« on: September 05, 2018, 11:25:58 pm »

Hi,

Does anyone know a good resource to serve as an example for a UML profile in the v14 flavor?
I'm specifically looking for examples for things like
- metaconstraint
- metarelation

These should now be used as an alternative to the dreaded quicklinker CSV definition.

The manual still leaves a lot to my imagination.

Thanks

Geert

8

General Board / Diagram alignment helper lines

« on: September 05, 2018, 06:36:42 pm »

At the very start of v14 I was excited to see new red helper lines when placing elements on a diagram.

Now for some reason I don't see them anymore . Does anyone know how to turn them back on?

I'm on v14.0.1422

Thanks

Geert

9

Bugs and Issues / EA.Element.Runstate setter does not work

« on: August 29, 2018, 11:52:31 pm »

The setter for EA.Element.Runstate doesn't seem to work.
No Code below results in
"Runstate = " where I would expect "Runstate = 123"

Code: [Select]

option explicit

!INC Local Scripts.EAConstants-VBScript

sub main
dim selectedElement as EA.Element
set selectedElement = Repository.GetTreeSelectedObject()
selectedElement.Runstate = "123"
Session.Output "Runstate = " &selectedElement.Runstate
end sub

main
Anyone know why? The manual simply says it's a string and it is read/write, so I would expect this code to work.

Geert

10

Bugs and Issues / DAO.QueryDef [3131] Syntax error in FROM clause.

« on: August 14, 2018, 10:30:00 pm »

I'm trying to write a somewhat complicated query, and I don't seem to be able to get EA to execute my query if it does a join with a subquery
I boiled it down to this type of statement:

Code: [Select]

select * from
t_attribute ta
inner join (select a.ID, a.Name from t_attribute a) dataq on dataq.ID = ta.IDwhen I execute this in EA I get

DAO.QueryDef [3131]
Syntax error in FROM clause.

The annoying thing is that this executed perfectly fine on the same model when I execute it using SQL Anywhere.

Geert

Does anyone know a workaround for this problem?

11

Suggestions and Requests / Ability to automate schema composer generation

« on: August 03, 2018, 05:26:51 pm »

I would like to be able to automatically generate schema composer profiles.

We use the schema composer to construct our message definitions (XSD) and with each release we need to be able to generate them all.
This is now a manual task that can take up a significant amount of time, so it would be great if EA would allow access to the schema generation via the API.

Geert

12

Bugs and Issues / Schema can still be changed even when not checked out

« on: August 01, 2018, 04:47:48 pm »

Details:
If you put a schema composer artifact in a controlled package the schema itself is not rendered read-only. It can still be changed even without checking out the package.
The same problem with the locking mechanism of user security.

Steps to Reproduce:
- Create a schema composer artifact in a controlled package
- Check in the package
- Try to update the schema in the schema composer
- Notice that you can still change the schema although it should be read-only.

Reported

Geert

13

Suggestions and Requests / Export reference data -> allow selection of scripts

« on: July 05, 2018, 04:27:35 pm »

I would like an option in the export reference data to select only certain scripts for export.
EA only has an option to export ALL the scripts (including a bunch of temp debug stuff that should never be exported anyway) and that is costing me a lot of time (and thus my customers a lot of money)

Each time I update a script in DEV that needs to be promoted to TEST/PROD
- Export all scripts
- Open the resulting xml file
- Copy paste the script parts I need to a new file (not forgetting the groups if not yet existing on the target model)
- Remove all scripts in the file with only those I copied

That could be so much easier if I could just select the scripts I want to export.

(bonus points if the export feature would automatically detect !INCLUDES and export those as well)

Geert

14

Bugs and Issues / RTF template: Exclude diagram type does not work for diagram elements

« on: May 30, 2018, 09:55:30 pm »

Found an annoying problem today.
I have a template that basically looks like this:

Code: [Select]

package >
diagram >
{Diagram.DiagramImg}
{Diagram.Name}
element >
< element
This should not be if the diagram is excluded
< diagram
< package

This works find and reports all diagrams.
Then I decided that I only wanted this report for a particular type of diagram.
So I configured the exclude filter on the template and excluded all but my own type of diagram: MyDiagramType.

Now when I run the report I get only the images and names of the diagrams of type MyDiagramType, so far so good.

But the text: This should not be if the diagram is excluded still appears for each diagram in the package, regardless of the diagram type.

Problem found in v 12.1 but still a an issue in v 14.0.1421

Geert

15

Bugs and Issues / EA 14 v 1420 Diagram Flow direction is completely broken

« on: May 16, 2018, 05:04:36 pm »

Setting the flow direction to horizontal on a (horizontal) BPMN diagram completely messes up the layout (and model)

All Pools and lanes get reduced in size making the Activities fall out of them (they also get moved out of the pool/lanes in the project browser)

Manipulating a (correct) diagram made in a previous version with the flow direction set also results in the same mess.

The only way to use BPMN diagram in v14 is to set the flow direction to None.

Geert