Runtime configurations

Introduction to runtime configurations

menu Maintenance > Runtime configurations

The Runtime configurations screen provides an overview of your personal runtime configurations for the selected model.

Runtime configurations can have different databases, extended properties, and file storage locations than the default configuration. Settings that deviate from the default configuration are shown in bold.

A runtime configuration provides the environment in which an application is started, defined by the database server and database of the application. By specifying multiple runtime configurations, the same application can be started on multiple environments, for example for development and testing purposes. The runtime configuration to be used is specified in the configuration file.

Runtime configuration overview

Active runtime configurations per user

The user interfaces provide the option to switch between active runtime configurations using the application selector. When a runtime configuration is active, its model and branch are available in the model version selector in the menu Models > Switch branch.

menu Maintenance > Users > tab Runtime configurations > tab Form

In this screen, the Active checkbox indicates whether or not the runtime configuration is activated for the current user.

• Universal GUI Indicium - Runtime configurations need to be activated or de-activated per user. When running applications in development directly in the Software Factory, only the active runtime configurations are loaded for the logged-in user.
• Windows GUI Web GUI - These GUIs will load all active runtime configurations when no model, branch and runtime configuration are specified in the INI file.
• Windows GUI To automatically load a runtime configuration when starting the Windows GUI on the Software Factory without specifying a model and branch, you must select the *Active* checkbox.

Active runtime configurations per user

The order in which active runtime configurations are shown can be modified here as well.

Custom pool user set

Universal GUI

When using the Software Factory in Universal GUI, you can store the pool user credentials in IAM or the Software Factory. These credentials will be safely encrypted and used instead of the credentials stored in Indiciums appsettings.json file.

menu Maintenance > Users > tab Runtime configurations > tab Form

See Store pool user credentials encrypted in the Indicium deployment manual.

Runtime configurations for other users

menu Maintenance > Runtime configurations > tab Other users

Runtime configurations contain personal settings. The Active checkbox does not affect the other users' settings.

In the Other users tab, you can enable or disable a runtime configuration for other users. You cannot add new users in this tab. This can be done in the menu Maintenance > Users > tab Runtime configurations.

The Runtime configurations detail tab shows the active and inactive runtime configurations for the selected user.

To display the users currently not involved in the development process, de-select the Active users prefilter.

Application ID and Alias

menu Maintenance > Runtime configurations

The application ID and Alias are used in the following ways:

• To access the API of the runtime configuration. This is the same use as in IAM, see Create an application.

  For example, if the application ID is 15 and the alias is crm, the customer entity can be accessed via the API using the following urls:

  • https://myserver.app/indicium/sf/15/customer
  • https://myserver.app/indicium/sf/crm/customer

• For the Universal GUI, the application ID or alias can also be used in the login configuration to start a specific runtime configuration. See Settings for the Universal GUI login screen.

Role simulation

menu Maintenance > Runtime configurations

Developers can choose to simulate a role. This can be set in the Runtime configurations screen at Personal settings or at the overview of runtime configurations per user. When the application is started or the model is refreshed, the rights of this role will be applied.

caution

While this setting is configurable in the Runtime configurations screen, this setting will affect all runtime configurations of this user for a branch.

Email provider for a runtime configuration

By default, the email provider as set in the menu Model overview > tab Branches > tab Email providers is used. See Email providers for more information.

You can deviate from this default and set up a different email provider for each runtime configuration. Use this, for example, to use SMTP in your development environment and Microsoft Graph in your test environment.

menu Maintenance > Runtime configurations > tab Email providers

To select another email provider type:

1. Execute task Switch email provider type .

To reset the email provider type to the default as set in the Model overview:

1. Execute task Reset email provider configuration .

File storage location for a runtime configuration

By default, the file storage location as set in the menu Model overview > tab Branches > tab File storage locations is used. See File storage locations in the Software Factory in the Models guide. For an overview of the available file storage types, see File storage.

You can deviate from this default and set up a different file storage location for each runtime configuration.

menu Maintenance > Runtime configurations > tab File storage locations

To select another file storage location type:

1. Execute task Switch file storage location type .

To reset the file storage configuration to the default as set in the Model overview:

1. Execute task Reset file storage configuration .

OAuth server for a runtime configuration

For OAuth process actions, an OAuth server is configurated in menu Models > Model overview > tab Branches > tab OAuth servers.

To override these settings for development or testing:

menu Maintenance > Runtime configuration -> tab OAuth servers