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 - AliBeadle

Pages: [1] 2
Bugs and Issues / Re: DOORS MGD - No Import Button
« on: January 11, 2023, 11:26:36 pm »
Oh, I found the issue:

I had one of my displays set to 150% scale (Windows desktop, Display Settings > Scale and Layout). When reset to 100% the dialogue looks as it should!

It seems EA does not cope well with UI scaling in this dialogue. Still technically a bug, so I have reported it, but at least I can work around it now.

Bugs and Issues / Re: DOORS MGD - No Import Button
« on: January 11, 2023, 11:01:36 pm »

This is what the dialogue looks like vs how the manual says it should look:

It seems the missing buttons are actually present - just hidden outside the visible dialogue window.

Bugs and Issues / Re: DOORS MGD - No Import Button
« on: January 11, 2023, 10:08:11 pm »
Update: I have found that if I use tab to switch between fields the 'missing' fields are accessible but hidden from view - so I can make it work, sort of, but it is very difficult to guess what options I am selecting. Looks like a bug in the MGD, with hte dialog box fixed size but too small to show all the fields. So maybe I will raise a ticket to report it as a bug. But has anyone else seen anything like this?

Bugs and Issues / DOORS MGD - No Import Button
« on: January 11, 2023, 09:42:10 pm »
Hello. I am trying out the DOORS MGD link 3.0 with EA 15.2 and DOORS 9.7.

I have successfully installed the MGD and linked a test project to a DOORS module,. However when trying to import data the dialog box I get only has 'DOORS Module' and 'Profile Name' fields - no button to actually start the import!

I.e. it looks just like the image in the documentation here except only with the top two fields - the three option boxes and three buttons are not visible - the dialog box ends under the 'Profile Name' field.

I have selected a module and a profile. The dialogue box refuses to be resized. I have tried a restart of EA. I have tried an export and it has the same issue.

Any thoughts or ideas about what may be wrong?

General Board / Tagged Values of Properties Inconsistent Display?
« on: October 07, 2021, 09:11:04 pm »
I am not sure if this is a bug or I am just doing it wrong:

When I create a tagged value on a property (in my case the property that represents an instance of an SysML block) I find EA is very inconsistent in whether or not it will list the presence of the tagged value.

On diagrams they are always listed (if the diagram properties require it).

If I initially look in the Tags tab of the properties window, then they are not shown UNTIL I double click the property and try to look at the tags there - after doing that once they will then appear in the Tags tab.

If I double click the property on a diagram (or right click it in the browser and select Properties>Properties) then the tagged values are NEVER displayed in the 'Tags' tab of that window.

I do not get this problem with Tagged Values in general, ONLY Tagged Values of Properties.

It seems like a bug to me. But are there any peculiarities of Tagged Values of Properties that I should be aware of that may explain this?

Bugs and Issues / Re: Virtual Document ignoring RTFTemplate
« on: July 30, 2021, 05:56:56 pm »
Ah, that is it! It was staring me in the face too!  :-[

To be fair, the documentation does say " the 'Tags' tab of the Properties window..."
In reply to my support ticket I have suggested a documentation clarification.

Thank you.  :)

Bugs and Issues / Re: Virtual Document ignoring RTFTemplate
« on: July 28, 2021, 08:02:44 pm »
No problem, thanks for getting me this far.

Tried a clean install of the latest build, still no joy. At least I can describe the problem and what we have tried clearly to the support team. Opening the ticket with support now, will post here if I can add anything useful when they get back to me...

Bugs and Issues / Re: Virtual Document ignoring RTFTemplate
« on: July 28, 2021, 06:05:55 pm »
Ah, that does seem to be the root of the problem, thanks!

I double checked and I think I am using the right diagram (Extended > ModelDocument, but I tried a default 'requirement' diagram as well, same result) and element (Documentation > Report Package). The element I get on the diagram looks like the images in the documentation and is stereotyped as "EAUML::report package", but the Tags pane only has an empty "Package (name)" heading - no default tags!

I don't think I changed anything in the MDG Profile. I created a new project and tried again to check, but with the same result - no default tags.

Bugs and Issues / Re: Virtual Document ignoring RTFTemplate
« on: July 27, 2021, 06:46:26 pm »
Thanks for checking. No, it does not seem to be that.

I have re-created the problem with simplest possible case, I think I must be missing a step or using the wrong 'element' somewhere:

* Drag a Report Package onto a diagram - name it but do not change any other settings.
* Open the child diagram formed in the Report Package folder.
* Drag a Model Document onto that diagram.
* Add a tag to the Model Document called RTFTemplate (it is not there by default, but I can add it).
* Edit that RTFTemplate tag to select a document template (it provides a pull down list for this).
* Save changes to all diagrams.
* Select the Report Package, select Report Builder, and press generate.

Bugs and Issues / Virtual Document ignoring RTFTemplate
« on: July 27, 2021, 12:58:12 am »
I am trying to use Virtual Documents for the first time but having a problem where it appears to be ignoring my RTFTemplate tag and defaulting to 'Model Report'.

I have followed the documentation to generate a Report Package and some contained Model Documents.

I have used the RTFTemplate tagged value to specify a template for each Model Document.

However when I run the report generator, although it is correctly selecting the packages and contained elements, it is always defaulting to the 'Model Report' template and ignoring my RTFTemplate tagged values.

If I try to generate the document from the Report Package, the 'Template' drop down is greyed out (and set to 'Model Report'). If I try to generate a part of the document from  a Model Document the 'Template' drop down is not greyed out (and set to 'Model Report'). If I generate the document in either case, the output reflects the 'Model Report' template, not the ones specified by the RTFTemplate tagged values.

I am aware of the following previous reports of similar things from this Forum, but they do not seem to be the case here:,39259.msg242782.html#msg242782. I can confirm that I am specifying full templates in my RTFTemplate tag, not fragments.,39368.msg243219.html#msg243219. I have closed and re-opened the model. The preoblem persists, so does not appear to be a caching issue.

I am running EA 15.1.1528.

General Board / Working from Home with Floating Licences
« on: March 16, 2020, 08:50:23 pm »
We are looking at helping staff possibly needing to work from home over the next few weeks. We use floating licences on the company network. I note that a laptop user on the network can take out a licence and the server can be configured so that it does not release it when they disconnect - allowing them to continue working at home later.

But is there a solution for someone who wants to 'check out' a licence and then use it on a home PC that is not connected to our company network?

Options I have thought of, but looking for alternatives:
  • Get the home users to setup their own local keystore server and transfer a licence to them temporarily (disabling it on the network version for that period0: a bit complicated and possibly not something all user's will want to do with their own home PCs,
  • Setup a VPN so that home users can access the company networked licence server: almost certainly too much for our IT department to setup in time ;)
  • Get the home user to register for the 30 day trial licence: Hope the situation does not last that long. Also suspect legality given the licence clause "it is licensed to you for evaluation purposes only"?

Bugs and Issues / Re: Printer Problems with V15 Build 1507
« on: September 18, 2019, 05:05:23 pm »
Latest build on 17-Sep-2019 was 1511, available in the members area:

Bugs and Issues / Re: Printer Problems with V15 Build 1507
« on: September 12, 2019, 08:39:58 pm »
I am having the same problem: printing 'scale to 1 page' diagrams on EA 15 build 1510 results in a blank frame only printout.

Turning off scale to page is sort of a workaround if you can cope with printouts over multiple pages:
  • Right click diagram
  • Select Properties
  • Select Diagram
  • Select Advanced under Page Setup
  • Turn off 'Scale to 1 Page'

A better workaround (for me) is leave 'Scale to 1 Page' on and then use print to PDF and  separately print the PDF:
  • On the ribbon, select 'Publish'
  • Under 'Print' select 'Print to PDF'

General Board / Re: Markup Glossary Terms not working?
« on: June 27, 2019, 10:02:47 pm »
OK, I think I have worked out the problem: the markup of glossary terms in documentation is case sensitive!

Most of my terms are in the body of the text were without initial capitals and all of my glossary terms were with initial capitals - so generally the case sensitive markup did not match them. If I change the capitalisation to match the glossary then it works.

This is annoying as the markup within the tool is not case sensitive. Further the Glossary will not allow me to enter two terms with different capitalisation (it says "There is an existing glossary with the same name"!) so I cannot work around the problem that way either.

So I guess I will have to remember to capitalise any word I want to be marked up as a glossary item?

Oh - and submit a bug report...

General Board / Markup Glossary Terms not working?
« on: June 13, 2019, 09:04:35 pm »
I have a glossary defined and am using the terms in my artifacts. In the model notes fields they are correctly highlighted by underlining.
I would like to highlight them in the generated documentation too - but cannot get this working.
> I have assigned Markup Styles to all of the glossary term types.
> I have also selected "Markup Glossary Terms" in the Generate Documentation dialogue.
However the terms remain in normal text in the resulting output.
Any thoughts on what may be wrong here? Has anyone else got this working?

(I note this similar question, but that was a few years ago and for EA 12:,26473.msg206638.html#msg206638)

Pages: [1] 2