Script Groups in MDG

[William McKenzie]

When I create a new script in EA. I must put it in a 'group', and this group can be specialized for project scripts, diagram scripts, etc. However, when I include those scripts in an MDG export, they lose this group concept and simply end up in a 'Common' group with the name of my MDG. Is there something I am missing about exporting the MDG, or is this grouping of scripts and types of scripts just a concept that is not supported in an MDG?

thanks,
~Bill

[qwerty]

AFAIR Helmut Ortmann had asked this question some time ago. But I don't remember the answer.

q.

[Helmut Ortmann]

I don't think there is an easy way to put the scripts in the correct Group.

I see the following two possibilities:

• Make an Addin to change the table t_script
• Modify the import script.xml file  

The concept for both solutions is the same.
Groups:
ScriptCategory: fix GUID
3955A83E-9E54-4810-8053-FACC68CD4782
ScriptName:  GUID
AcriptAuthor: Null
Notes:
<Group Type="PROJBROWSER" Notes=""/>  or
<Group Type="MODELSEARCH" Notes=""/>  or
<Group Type="DIAGRAM" Notes=""/>           or
<Group Type="NORMAL" Notes=""/>            or
<Group Type="MODELSEARCH" Notes=""/> or
<Group Type="PROJBROWSER" Notes="Scripts which are shown in the browser context menue."/>  

Script: Name of the Group  

Scripts:
ScriptCategory: fix GUID
605A62F7-BCD0-4845-A8D0-7DC45B4D2E3F
ScriptName: GUID
ScriptAuthor: GUID of ScriptName of Group

With knowing this you can easily create your own Group or use it by existing scripts.

@Thomas, a possable content for your book


Good luck,

Helmut

[qwerty]

Thanks, Helmut. I'll add that to the next release!

q.

[Helmut Ortmann]

Script goups are not really supported by MDG.

Therfore it's a good idea not to include scripts in your MDG. Export your scripts  as 'Reference Data' and import it in the repositories where you need the scripts and script groups. You have to restart the repository.

Best regards,

Helmut