Saving and Using Application Configurations

You can save user-specific settings and settings as model-wide application configurations in various editors. The settings can be used by all model users as model-wide configuration.

Using Application Configuration

You can save user-specific settings as application configurations in various editors.

The Edit Model-Wide Configurations privilege enables an existing user-specific setting to be saved in the model that can be made into model-wide configurations. Model-wide configuration can be used by all users. You can directly edit and save model-wide conigurations with this privilege.

This process works in the following editors and processes:

Save the configuration for mapping themes for reuse. User-specific settings are limited to one model.

Command in the Beamer tool window:

  • Configure...

    Opens a dialog where mapping themes can be modified.

    Configuration management for mapping themes is integrated in the dialog. (see "Configure Mappings Dialog")

Configurations can be stored separately for content and display of the analysis graph.

Commands in the Impact Analysis>Configuration context tab:

  • Select

    The drop-down list shows content or display configurations. Icons split perspectives into two groups:

     Model-wide configuration

    User-defined configuration

    Selecting a configuration restores its settings.

  • Manage

    Open a dialog which allows managing the configurations. (see "Managing Application Configurations")

  • Save

    Save the current settings to the selected configuration. If a model-wide configuration is selected, you need the privilege 'Edit Model-Wide Configurations', otherwise you can choose a name for saving the configuration user-specifically. The saved configuration is then considered loaded.

  • Save As

    Save the current settings into a new or existing configuration, model-wide or user-specific. Saving a model-wide configuration requires the privilege 'Edit Model-Wide Configurations'. The saved configuration is then considered loaded.

You can manage configurations for importing ArchiMate, BPMN or DMN files in a tool window.

Open the Configuration context tab with Import/Export>Import>ArchiMate|BPMN|DMN>Configure.

Commands in the Import>Configuration ribbon group:

  • Select

    The drop-down list shows application configurations. Icons split perspectives into two groups:

    Model-wide configuration

    User-defined configuration

    Selecting a configuration restores its settings.

  • Manage

    Open a dialog which allows managing the configurations. (see "Managing Application Configurations")

  • Save

    Save the current settings to the selected configuration. If a model-wide configuration is selected, you need the privilege 'Edit Model-Wide Configurations', otherwise you can choose a name for saving the configuration user-specifically. The saved configuration is then considered loaded.

  • Save As

    Save the current settings into a new or existing configuration, model-wide or user-specific. Saving a model-wide configuration requires the privilege 'Edit Model-Wide Configurations'. The saved configuration is then considered loaded.

Save the configuration for filter settings for reuse.

Commands in the Align Models>Filter context tab:

  • Select

    The drop-down list shows filter configurations. Icons split perspectives into two groups:

    Model-wide configuration

    User-defined configuration

    Selecting a configuration restores its settings.

  • Manage

    Open a dialog which allows managing the configurations. (see "Managing Application Configurations")

  • Save

    Save the current settings to the selected configuration. If a model-wide configuration is selected, you need the privilege 'Edit Model-Wide Configurations', otherwise you can choose a name for saving the configuration user-specifically. The saved configuration is then considered loaded.

  • Save As

    Save the current settings into a new or existing configuration, model-wide or user-specific. Saving a model-wide configuration requires the privilege 'Edit Model-Wide Configurations'. The saved configuration is then considered loaded.

Save the current layout of the tool windows and document area as perspectives and open them.

Command in the View>Windows>Arrange Windows default tab:

Load or save the configuration for the process manual. The configuration is always available in all models. You require the Edit Model-Wide Configurations privilege.

Commands in the Extras>Update Process Manual ribbon group:

  • Load Application Configuration

    Loads the model-wide application configuration from the $INOHOME\ProcessCharacteristics.json file. Changes only take effect after the model editor has been restarted.

  • Save Application Configuration

    Saves the model-wide application configuration as the $INOHOME\ProcessCharacteristics.json file.

Save configuration for a tab in the Find dialog for reuse.

The management is integrated in the dialog. (see "Saved Searches")

Save the configuration of a table view for reuse.

Commands in the Design>Table View context tab:

  • Select

    The drop-down list shows table views. Icons split perspectives into two groups:

    Model-wide configuration

    User-defined configuration

    Selecting a table view restores its settings.

  • Manage Table Views

    Select element types or stereotypes for table views.

    Open a dialog which allows managing the configurations. (see "Managing Application Configurations")

  • Save

    Assign current table layout and, if applicable, stereotype filter to the view selected in the ribbon.

  • Save As

    Assign current table layout and, if applicable, stereotype filter to a new or existing view and select it in the ribbon.

Managing Application Configurations

You can initially save an editor or a process' respective configuration as user-defined under a certain name.

The Edit Model-Wide Configurations privilege enables:

  • Saving existing user-defined configurations in the model so that they can be used for model-wide configurations for the respective context by all users.

  • Direct editing and saving of model-wide configurations in the inline and ribbon control elements and in the Manage dialog

  • Direct editing of model-wide configurations in the Manage dialog

You can filter the lists of configurations of various applications to one text pattern. These filters are available across sessions.

The following commands can be used to manage the configurations.

  •  New

    Creates a new user specific configuration. It will be saved with the current settings, and it will be loaded then.

  •  Rename

    Rename the selected configuration. Renaming a configuration which has pending changes is not possible. Renaming a model-wide configuration requires the privilege 'Edit Model-Wide Configurations'.

  •  Delete

    Delete the selected configuration. Deleting a model-wide configuration requires the privilege 'Edit Model-Wide Configurations'.

  •  Copy

    Create a user specific copy of the selected configuration. The copy is loaded. Copying is not possible when the loaded configuration has no pending changes.

  •  Deploy

    Create a model-wide application configuration from the selected user-specific configuration. After deployment as a model-wide configuration, the user-specific configuration is deleted. The selected configuration must not have pending changes. The privilege 'Edit Model-Wide Configurations' is required.

  •  Save

    Save the current settings to the selected configuration. If a model-wide configuration is selected, you need the privilege 'Edit Model-Wide Configurations', otherwise you can choose a name for saving the configuration user-specifically. The saved configuration is then considered loaded.

  •  Save As

    Save the current settings into a new or existing configuration, model-wide or user-specific. Saving a model-wide configuration requires the privilege 'Edit Model-Wide Configurations'. The saved configuration is then considered loaded.

  •  Discard Changes (for directly editable configurations)

    Discards the changes on the edited configuration.

  •  View Content

    Opens a dialog which allows viewing the configuration as text. Changes are not possible.

  •  Edit Content (replaces View Content for defective configurations)

    Opens a dialog which allows editing the configuration as text. In this way can a configuration be repaired that cannot be loaded anymore.

    Proceed carefully as invalid structure changes may make the configuration unusable.

Related Topics Link IconRelated Topics