A macro is a sequence of instructions that become automatic when called.
You can start macros manually in ARIS Architect or automatically in ARIS Architect and ARIS. To start macros automatically, you can define that a macro is started when a certain event occurs.
ARIS is supplied with numerous standard scripts. Authorized ARIS users can analyze and process data using scripts that you provide. The package and license that you have purchased will determine the range of macros available to you.
If you have the ARIS Enterprise Admin license privilege and the Script administrator function privilege, you can perform basic report management in ARIS Administration. If you are familiar with the JavaScript and ARIS Script programming languages, you can edit or write your own scrips in ARIS Architect.
To manage macros in ARIS Administration, click Application launcher >
Administration >
Configuration > Evaluation and select Macros.
All scripts are organized in a clear structure using categories.
Categories
You can if you have no category selected.
Use categories to organize your scripts in a clear structure.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Click Create category.
Enter the name of the new category and click Apply.
The category is displayed only in the current language.
To display the category in multiple interface languages, you must rename the category in each language. If you do not specify a category in a particular language, the category is displayed in English.
If you select a category, you can do the following:
You can change the name of a category or specify the name in a different language. You cannot change the name of the Standard category.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Select the category and click Rename.
Select the related language.
Enter the name in the selected language and click Apply.
The category is renamed in the current language.
You can delete a category and all the scripts that it contains. Software AG recommends that you first export the scripts in order to have backup files.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Select the category that you want to delete. You cannot delete the Standard category.
Click Delete.
Click Delete to confirm.
The category and all scripts that it contains are deleted.
You can import scripts from export files or import common files that a script uses during runtime. This enables you to provide scripts from another tenant or import scripts from a previous version.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Click the category into which you want to import the script.
Import.
Select the related import file and click Open.
If the script already exists in a category, you must confirm in order to import a copy into the selected category.
If the script executes imported common files during runtime, you can enable the required file and confirm the import of the file. Otherwise, the current common file on the tenant is used.
The script is imported.
Create your own event-triggered macro that automatically starts a report or a semantic check.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Click the category to which you want to add the macro or create a new category.
Click Create Macro.
Select the language in which you want to edit the text fields.
Specify the entries in all required languages. Name and Description are especially important. Overwrite the name, subject, author, company, or description, as required.
Select the next language, if required, and edit the text fields in turn.
If required, disable the Available to users check box if you created a macro but have not checked it yet. Scripts can still be edited in the Script Editor (ARIS Architect).
Click Context > Add event and add the event that will automatically start the report or semantic check.
The added event defines the context for which the macro can be started. You cannot add types, such as model types, but you can activate Include derived types. This makes sense if you want the macro to be started, for example, for a model of a derived model type that is not listed in the added model types.
Click Content and in the Content field select The macro runs a report or The macro runs a semantic check, as required.
If you select User-defined macro (available only in ARIS Architect), you can specify basic properties, but you can write the script only in ARIS Architect.
Select the required report or semantic check profile.
Click Output, enable Generate output file, and select the file types if required.
Click Apply.
The macro is available.
If you restrict access for execution to specific users, make sure that these restrictions exactly match the ones of the report or the semantic check profile to be started by this macro.
When you select a macro, you can do the following:
Edit macro properties
You can rename macro scripts in multiple languages or change other text attributes.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Select the related category and select the script.
Click Edit properties.
Select the language in which you want to edit the text fields.
Overwrite the name, subject, author, company, or description, as required.
Select the next language, if required, and edit the text fields in turn.
Click Apply.
The changes are saved.
You can decide whether a macro script is available or not.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Select the related category and select the script.
Click Edit properties.
Enable Available to users.
Click Apply.
Authorized users can use the macro.
You can specify the database items for which the script can be started. Users can run the script only for the database items you specify as context.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Select the related category and select the script.
Click Edit properties.
Click Context and enable the related options. If you enabled Model or Object, you can specify the types for which users can start the script.
If you select model types on which derived model types are based and the Include derived types check box is not enabled, the script can still be run for the derived model types. If you enable model types on which derived model types are based, but have disabled the derived types, the script is still available for the disabled derived model types.
Click Apply to save the changes.
The script is available for the selected context.
.
You can specify events that trigger macro execution.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Select the related category and select the script.
Click Edit properties.
Click Context and in the Context type field, select Event-based context.
Select the required event. If events are missing, click Add event.
Select the missing events and click Add.
If you enable Can be started only by an event, the macro can no longer be started by users.
The macro uses the selected events.
Use evaluation filters to reduce the number of items that are evaluated and listed in the output.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Select the related category and select the script.
Click Edit properties.
Click Evaluation filter and enable Use evaluation filter. All evaluation filters created for this tenant are listed.
Select the related filter.
Click Apply to save the changes.
The script evaluates only items that are contained in the evaluation filter.
You can specify whether a script generates an output file and select the file type of the output file.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Select the related category and select the script.
Click Edit properties.
Click Output.
Enable Generate output file and select the required file types.
Click Apply to save the changes.
You can select the file formats to use for the generated output files. If in the scripts you use fonts that are not installed on the operating system on the machine on which ARIS server is running, you must add these missing fonts. If a font is missing, the content using the font is not readable. The missing fonts are not rendered correctly in the output files, or when pasting a copied model to another application.
If the PDF, RTF, or DOC format was enabled as possible output format for a script, you can change the page properties for generated output files.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Select the related category and select the script.
Click Edit properties.
Click Page layout and change the settings as required.
Click Apply to save the changes.
Output files in the PDF, RTF, or DOC format use the defined page settings.
You can change the set of files that the script imports during runtime.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Select the related category and select the script.
Click Edit properties.
Click Advanced properties.
If the script imports files at runtime, related common files are enabled. If you disable files, the script may no longer run properly.
Click Apply to save the changes.
The advanced properties are saved.
Duplicate standard scripts and files to prevent your changes from being lost. During a system update, all standard scripts and files are automatically overwritten to provide you with the newest features.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Click the category in which you keep the script.
Select the related script and click Duplicate.
The script has been duplicated.
You can modify the duplicated script. The duplicated script will not be overwritten during an ARIS update because it has a new GUID.
You can delete scripts that you no longer require, such asa report scrips. If you export the scripts first, you can make them available again at any time.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Click the category in which you keep the script.
Select the script and click Delete.
Click Delete to confirm.
The script is no longer available on the tenant.
You can save scripts as export files if you want to store different versions or to make scripts available on multiple tenants.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Click the category in which you keep the script.
Select the script and click Export.
If the script executes imported common files during runtime, you can enable the required files and confirm the inclusion of the files in the export file. Otherwise, only the script is exported.
Navigate to the file location where you want to save the file and click Save.
The script has been saved.
By default, all users of a tenant have access to all scripts. You can make scripts available only to members of defined user groups.
Click Application launcher >
Administration >
Configuration > Evaluations and select Macros.
Click the category in which you keep the script.
Select the script, click Restrict access, and enable Restrict access to user groups. All user groups available on this tenant are displayed. Make sure that a related
user group was created in ARIS Administration.
Enable the related user groups and click Apply.
The script can be run only by members of the selected user groups.