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 - Aaron B

Pages: [1] 2 3 ... 63
Yes, the installer size is correct (592KB).

MDG DOORS v3 requires DOORS 9.6.1 or higher. It's not supported for connection to DOORS 8.3.

Do you have more than one version of DOORS installed on your system? This has been known to cause issues.

If needing further assistance, can you please send an email to with the steps you are following with MDG DOORS v3 and DOORS 9.7? Include details such as your EA version, MDG version, DOORS version(s), Operating System etc. Also include screenshots where possible.


The current release of MDG Link for DOORS v3.0 requires DOORS 9.6 or higher and won't work with DOORS 8.4. If you need to try connecting with DOORS 8.4, the older version of MDG DOORS 2.2 can also be downloaded here:

Your problem when trying to connect MDG DOORS 3.0 to DOORS 9.7 however does seem strange. If you are still having this issue, please send an email to our support team at for further assistance.

General Board / Re: IBM Doors / Sparx EA integration
« on: April 09, 2021, 10:13:08 am »
As Sunshine points out there is the MDG DOORS add-in, which is now a free download. This targets the desktop version of DOORS 9.6 and allows for import and export of Requirements between EA and DOORS.

Pro Cloud Server can integrate with DOORS NG via the IBM Jazz platform. See:

General Board / Re: little red A
« on: February 25, 2021, 05:07:12 pm »
Correct. The red letter 'A' indicates a Linked Document on this element.

See the Notes section at the bottom of this page:

What type of connectors are they? Also try looking in the Relationships window (Start > Desktop > Design > Relationships).

The Traceability window also allows you to filter out some relationship types. Try clicking the drop down "Relationship Selector" on the toolbar to see what is currently enabled/disabled.

Just as a test - What happens if the model file is copied to your local machine first and opened from there? Are you able to browse the entire model from there without issues?

My general advice would be to avoid accessing EAP files over a network drive where possible. Depending on various factors such as the speed and reliability of the network connection, and the size/complexity of the file, there is a risk of corrupting the model file.

If you have a shared model which multiple users need to access and work on then you are better to configure a server based repository, or use Pro Cloud Server.

PCS General Board / Re: PCS Management client ssl connection
« on: January 19, 2021, 10:55:37 am »
Hi Typia,
There is no way to connect the Pro Cloud Config Client via https that I'm aware of. It's only intended to be accessed this way on a private network.

The description from the config file:

Code: [Select]
# The SERVER_PORT setting defines the TCP Port that the
# Configuration Client and the ISAPI module will communicate on.
# It is NOT recommended to expose this port outside of
# your private network.

If you need to manage the configuration over https then I'd suggest using WebConfig instead.

Log entries such as checkouts and checkins for the PCS Floating License Server should be available in the PCS log files. (Default location: C:\Program Files (x86)\Sparx Systems\Pro Cloud Server\Service\Logs)

A Username and Password is required to access the PCS Floating License Server.

When using floating licenses the logs can tell you some basic information such as checkout and checkin times, but other than that there is no other explicit way to track user activity that I'm aware of.

Automation Interface, Add-Ins and Tools / Re: What about Visual Studio 2019?
« on: September 15, 2020, 01:29:36 pm »
@MichaelJ It's possible that our Compare Editions page needs to be updated in this regard - I'll ask about this.

@Pino In regards to the issues you're having, can you please either send an email to, or better yet submit a support request / bug report via the forms on our website? Provide as much detail as you can and any sample files where possible and we'll investigate it further.

Automation Interface, Add-Ins and Tools / Re: What about Visual Studio 2019?
« on: September 14, 2020, 12:56:05 pm »
Hello Pino,

Importing Visual Studio projects is now built-in feature with Enterprise Architect and supports the current versions of Visual Studio. The MDG Integration for Visual Studio add-in (which is what I assume you were looking at) is no longer required. As you observed, the MDG Integration add-in only supported up to VS 2013.


PCS Bugs and Issues / Re: Service Now Disabled by Licensing
« on: September 10, 2020, 11:58:02 am »
Hello Phil,
Integrations such as Service Now require a licensed Pro Cloud Server. Can you confirm whether this PCS installation has a valid license or tokens? If PCS is currently unlicensed (or perhaps the license has lapsed?) then these integrations will not be available.

General Board / Re: Support mail quota exceeded
« on: June 30, 2020, 10:31:19 am »
Thanks for letting us know. These errors should now be resolved.

Which instructions are you referring to which tell you to use the address ""? Was it this page?

That address is just provided there as an example. The address "" is a site owned by Sparx Systems. It is not a reference to your own PCS instance. If you are currently on the same machine as where PCS is installed you can try just connecting to server name "localhost", or otherwise you'll need to know the name or IP address of your PCS server.

When upgrading an existing Pro Cloud Server installation to a newer version, please also refer to the instructions here:

Note that if you are using WebEA, you may need to update your WebEA and WebConfig files manually. The latest files should be in your installation folder, but may need to be manually copied to the appropriate location on your web server.

Sorry, I missed missed the page where you had initially taken the script from. Having copied the original script from that page, replaced the ActiveXObject line with COMObject like you describe, unfortunately I couldn't reproduce your error. The script seemed to execute fine for me as JavaScript. Tested with EA 15.0.1514 and 15.1.1528. I was only testing running the script directly from the Scripting window however, I was not attempting to invoke it from a script fragment.

It's not clear what type of objects xmlRoot or xmlDataSet are in your examples so far.

Can you perhaps send a complete copy of your script (or sample model file) to our support email for further investigation?
Send to:

Or otherwise perhaps post a more complete code sample here on the forum which demonstrates the problem?

Pages: [1] 2 3 ... 63