Messages

1

Suggestions and Requests / Re: EA 11 wishlist

« on: February 04, 2014, 01:57:30 am »

Just saw the latest version 2.6.0 of Archi (see archimatetool.com), they are definitely on the right track.

So an improvement to avoid mistakes:

In our course, I often make the remark to distinguish between "Delete from diagram" and "Delete from Model". How about making this choice explicit on the appropriate menu's?

E.g. the right-click menu when an element is selected on a diagram, the bottom option now is "Delete '<alias>'". Rename this option to "Delete from Diagram" and add a new option "Delete from Model".

2

General Board / Re: EXport class  properties in Excel

« on: December 12, 2013, 08:48:25 pm »

You could try the CSV import/export feature.

It can be accessed via the package context menu (right-click on the package).
Select menu "Import/Export | CSV Import/Export".
In the window that pops up, you can define a 'Specification' which acts as a 'template' to define the properties of the elements to import or export.

3

General Board / RTF Document templates for J-STD-016 standard

« on: December 10, 2013, 09:24:08 pm »

Some of our customers are using the J-STD-016 standard for system development.
This standard is relatively heavy on the documentation which is prescribed, including a rather rigid content definition.
Does anyone has or know of any support for this documentation standard using the modelling power of EA?

4

Automation Interface, Add-Ins and Tools / Re: Running EA VB.exe Add-in on server

« on: April 25, 2014, 08:16:53 pm »

Unfortunately I'm still stuck on this issue.

I thought I had it running on a server, but that was for a ultimate license.

Is there any difference between a 'normal' and a 'named user' license?

5

Automation Interface, Add-Ins and Tools / Re: Running EA VB.exe Add-in on server

« on: March 28, 2014, 12:26:49 am »

Realizing this limitation, we installed EA on the server.
Now it works for the manual start of the VB application.

However, when trying to start it automatically using the Windows scheduler renders the same issue.

What might be the issue with the scheduler?

6

Automation Interface, Add-Ins and Tools / Re: Running EA VB.exe Add-in on server

« on: March 27, 2014, 12:12:49 am »

Wow, quick responses.

And maybe I named the application mistakenly an add-in.
It basically is a Visual Basic application using "r = New EA.Repository" to create an instance for further processing the model contents.

Anyway, reading these responses, I think I have to either convince the administrator to install EA or find a workstation for running the application.

Thanks again.

7

Automation Interface, Add-Ins and Tools / Running EA VB.exe Add-in on server

« on: March 27, 2014, 12:03:17 am »

Using Visual Studio I wrote an EA Add-in using Visual Basic.
I've got it working fine on a client with EA installed.

Now I would like to schedule the add-in to run daily on a server.
The company policy however limits the installation of software on servers.

Is there any way I can run the add-in on a server where there is no EA client installed?

I do have the Interop.EA.dll installed with the VB.exe.
The VB.exe.config contains the reference to the EA RDBMS and user id password.

8

Automation Interface, Add-Ins and Tools / Re: New status for Maintenance Issues and Defects

« on: April 15, 2014, 01:14:51 am »

The Issues I'm talking about are generated as follows:

• Create a TestSet element.
• Create a test in the TestSet.
• Create a defect from the test generated.

The tests can be shown via the Element => Testing window ("Alt+3").
The defects can be shown via the Element => Maintenance window ("Alt+4").

9

Automation Interface, Add-Ins and Tools / Re: New status for Maintenance Issues and Defects

« on: April 14, 2014, 11:18:27 pm »

Thanks for this quick reaction.

However, I don't think this works as that list contains the values "Approved", "Implemented", "Mandatory", "Proposed" and "Validated", which is different from the list for Maintenance Issues (see question above).

Furthermore, when I would like to configure the auto-number feature for Maintenance Issues, I need to check the "Obj-Issue" type instead of "Issue" (using menu Settings => Auto Names and Counters).

The settings mentioned allow to apply that list for more objects via the button "Applies to...". In this list, the value "Obj-Issue" is missing. And neither "Issue" nor "Object" seems to do the trick.  

10

Automation Interface, Add-Ins and Tools / New status for Maintenance Issues and Defects

« on: April 14, 2014, 09:55:47 pm »

The reference data enables the configuration of several enumerations, e.g. the set of status values for a Requirement.

For Maintenance Issues and Defects however, I cannot find any reference data to modify.
Currently EA (V10.0.1003) supports the values "New", "Verified" and "Complete". I would like to add the value "In Progress" (or similar).

Can some one point me how to add a new status value for Maintenance Issues and Defects?

11

Automation Interface, Add-Ins and Tools / Importing Archimate models from free tool Archi

« on: April 14, 2014, 04:37:05 pm »

Since 9.3 EA is supporting the Archimate modelling language.
With recent updates, EA now even supports Archimate 2.1.

The same language is also supported by the open source tool Archi (see http://www.archimatetool.com/).
This tool uses the file type ".archimate" based on XML.

Is there any easy way to import such an ".archimate" file into EA?

12

Automation Interface, Add-Ins and Tools / Re: Generating daily HTML report of entire reposit

« on: December 12, 2013, 08:58:48 pm »

The suggestion above will generate either a fixed package identified by it's guid or a complete model.

For my solution, I used a tagged value to determine which package to take as a root. The app will scan the complete repository and only report the package(s) where rhrExport is defined to be 'true'.
Tagged values could also be used to determine other parameters used for RunHTMLReport like the path or template to use.