Enterprise Architect implements a flexible and easy to use scripting capability based on both industry standard Javascript and Microsoft JScript and VBScript. Using a built in 'Repository' object, you can programmatically inspect and/or modify elements within your currently open model. There are built in tools to edit, run, debug and manage your scripts.

Scripts can be used for a wide range of purposes, including:

·Inspecting and reporting on model and element composition
·Modifying and updating element properties
·Running queries to obtain extended model information
·Modifying diagram layouts
·Being called from report document templates to populate reports
·Creating and implementing process workflows
·Being included in MDG Technologies to augment domain specific languages


Scripting can help you get the custom information you need from your model, verify the structure of your model and help you automate time consuming manual tasks.




See also


Scripts executed in Enterprise Architect have access to the currently open model and are a powerful tool for querying and updating the model in situations that would otherwise require you to perform time consuming and repetitive GUI tasks.

Enterprise Architect supports management of scripts using the following script engines:

·Microsoft JScript
·Microsoft VBScript


The management interface for Scripting is the Scripting window, which contains the:

·Script Tree View (Scripts tab), which you use to review, create and edit scripts
·Script Console (Console tab), which you use to operate on an executing script


Scripts are managed in groups: the first group in the list is always Local Scripts, which are files in the Scripts subdirectory of the Enterprise Architect installation - any instance of Enterprise Architect that has a currently open model can see these scripts; you cannot create, edit, drag-and-drop or delete Local scripts.

All other groups are User Scripts, which you create yourself; a user group can be one of several types, each of which applies a template and certain conditions to the scripts you create within that group.

User scripts are only visible inside the model in which they were created; the contents of the scripts are stored with the model, although they can be saved to the file system easily using the Script Editor.

During the development of a script, you can debug it as you test it and analyse the execution; for example, by recording a Sequence diagram of the script execution, and halting execution to view local variables.










Scripts Tab

Console Tab



Script Group Properties




Script Editor


Script Debugging


·This facility is available in the Corporate, Business and Software Engineering, Systems Engineering and Ultimate editions
·If you intend to use the Scripting facility under Crossover/WINE, you must also install Internet Explorer version 6.0 or above


Learning Center topics

·Alt+F1 | Enterprise Architect | Automation | Scripting