Book a Demo

Author Topic: MDG Selection won't Persist  (Read 4954 times)

philchudley

  • EA User
  • **
  • Posts: 750
  • Karma: +22/-0
  • EA Consultant / Trainer - Sparx Europe
    • View Profile
MDG Selection won't Persist
« on: September 25, 2020, 08:20:00 pm »
Hi All

One of my clients has a strange EA issue.

They have a custom MDG which is definitely in the list of all MDGS (it is loaded from a path). However, many of the MDGs are unchecked including their own. A user can select these (turn them on), but after close the MDG Technologies dialog and reopening, they are all unchecked again.

The same effect happens regardless of whether the MDG is loaded from a path, imported into the model or imported to user. It appears in the list but just cannot be selected.

I thought its a windows registry issue, but upon examining the entry HKEY_CURRENT_USER\Software\Sparx Systems\EA400\EA\OPTIONS\MDG_TECHNOLOGY_STATUS on my own workstation (which has all MDGS activated including the clients), I find that not all my available MDGS are listed in this windows registry entry.

So I am at a bit of a loss as to what to suggest. My gut feeling is to add an entry to the clients registry for their own MDG, but why is it not listed in my own windows registry and the MDGS all work perfectly?

Is there somewhere else I should be looking?

All help greatly appreciated.

Phil

Models are great!
Correct models are even greater!

philchudley

  • EA User
  • **
  • Posts: 750
  • Karma: +22/-0
  • EA Consultant / Trainer - Sparx Europe
    • View Profile
Re: MDG Selection won't Persist
« Reply #1 on: September 25, 2020, 08:28:57 pm »
Further to this post below is the MDG_TECHNOLOGY_STATUS registry entry fr my workstation

GoF=1;AML=1;GML=1;EAScriptLib=1;UMM2FoundV2=1;NIEM 3.0=1;AUTOSAR-401=1;UAF=1;Archimate=1;BPMN1.1=1;GRA-UML=1;UPCC2=1;UPCC3=1;Project=1;SysML1.2=1;SYSENG=1;EP=1;SysML1.1=1;ERD=1;SOMF=1;6581=1;CODEENG=1;WebProfile=1;DFD=1;BPMN=1;UBL21=1;BRM=1;DatabaseEngineering=1;Win32UI=1;ArcGIS=1;ICONIX=1;SoaML=1;NIEM=1;SPEM=1;ODM1.0=1;RT=1;

This is list is far shorter than the total list of available MDGs,

EA version 15.1
Ultimate License

Phil
Models are great!
Correct models are even greater!

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: MDG Selection won't Persist
« Reply #2 on: September 25, 2020, 08:52:37 pm »
Hi Phil,


Could it be to do with required/prohibited technologies?

Have a look in t_genopt. To quote myself from whenever ago:

Quote
In a project where you've fiddled with the required/prohibited MDG Technologies you'll find two rows where t_genopt.AppliesTo is "MDGBlklist" and "MDGRequire". t_genopt.Option for each contains a comma-separated list of MDG Technologies, using the "ID" from the XML file.


/Uffe
My theories are always correct, just apply them to the right reality.

philchudley

  • EA User
  • **
  • Posts: 750
  • Karma: +22/-0
  • EA Consultant / Trainer - Sparx Europe
    • View Profile
Re: MDG Selection won't Persist
« Reply #3 on: September 25, 2020, 08:55:42 pm »
Thanks for the pointer I'll check that out

Models are great!
Correct models are even greater!

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: MDG Selection won't Persist
« Reply #4 on: September 25, 2020, 08:56:43 pm »

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: MDG Selection won't Persist
« Reply #5 on: September 25, 2020, 09:50:41 pm »
I think I remember a similar issue when you have duplicate MDG's loaded (one in your profile, and another in the model) or something like that.

Geert

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: MDG Selection won't Persist
« Reply #6 on: September 26, 2020, 03:25:18 am »
There's another point in that thread Q found (thanks for that, btw): some technology selections aren't in MDG_TECHNOLOGY_STATUS but have their own separate registry values. This may be why you're not seeing all the technologies you're expecting.

Applies to Basic UML and Core Extensions.

/Uffe
My theories are always correct, just apply them to the right reality.