# Low-code configuration The configuration definition is available in the module **Application** Eximee Designer. {% hint style="info" %} Applications that use the configuration server to fetch configuration must have configured [Data model](/documentation/documentation-en/budowanie-aplikacji/model-danych.md) and a start point set. {% endhint %} When going to a given application window, the left panel contains the tab **Configuration,** and in the right window **Configuration Editor**:

Figure 1. Configuration from Eximee Designer - Configuration tab

## Configuration format Configurations are defined in the format: key = value ### Environment setup Additionally, it is possible to specify the environment for which a given setting will be available by adding a suffix to the key **|${environment\_key}** e.g. application.login**|prod**=keyValue Such a setting will by default be available only for the environment marked as "prod". We can define the environment using the ENV - **CONFIG\_SERVER\_ENVIRONMENT\_NAME** in the configuration server application. If there is no suffix key for the current environment, values without a specified suffix are used. ### Comments In the configuration editing window, it is possible to add comments in the configuration content. Comments should start on a **new line**, and the comment content should be preceded by the **hash symbol (#)**. ### **Definition of roles authorized to edit in Eximee Dashboard** {% hint style="warning" %} Please note that in addition to defining roles in Eximee Designer that are authorized to edit a specific configuration in Eximee Dashboard, the Eximee Dashboard user must have assigned a role with permission **feature\_config\_edit**, which gives access to the "Application Configuration" tab. {% endhint %} Together with the configuration in Eximee Designer, you can define roles that will allow editing the configuration [runtime](/documentation/documentation-en/zarzadzanie-aplikacja-biznesowa/zarzadzanie-konfiguracja/konfiguracja-aplikacji-biznesowej-serwer-konfiguracji/modyfikacja-runtime-konfiguracji-biznesowych.md) in Eximee Dashboard. If no roles are defined in the application configuration in Eximee Designer, editing the application configuration from Eximee Dashboard will not be available to any user. Role definitions can be specified in the "Roles authorized to edit in Eximee Dashboard" field above the configuration editor in Eximee Designer. If the configuration server application has the AUTH\_ROLE\_STRIP\_PREFIX parameter defined, then the given role prefix should be omitted from the list items.\ So if AUTH\_ROLE\_STRIP\_PREFIX = "PDC000000001-" and the role is named "PDC000000001-config-editor-role", then in the list in Eximee Designer you should specify "config-editor-role". \ Editing configuration in Eximee Dashboard: [Modification (runtime) of business configurations](/documentation/documentation-en/zarzadzanie-aplikacja-biznesowa/zarzadzanie-konfiguracja/konfiguracja-aplikacji-biznesowej-serwer-konfiguracji/modyfikacja-runtime-konfiguracji-biznesowych.md)

Figure 2. Configuration from Eximee Dashboard - "Application Configuration" tab

### Configuration example CONFIG\_SERVER\_ENVIRONMENT\_NAME = **dev** Configuration content: ```editorconfig #url links to test environment test.url|dev=urlDev test.url=urlDefault test.password=passwordBasic test.password|prod=passwordProd test.password|dev=passwordDev test.login|prod=loginProd test.login=loginDefault test.enabled=true ``` The config server for such settings will return 4 configurations (without suffix): ```editorconfig test.url=urlDev test.password=passwordDev test.login=loginDefault test.enabled=true ``` ### **Configuration editing** Editing the configuration locks the application artifact, therefore new artifacts cannot be added to it, e.g. a process, form. However, an attempt to add such an artifact **will create it in the repository**, but **it will not be attached** to the application artifact.
In the case of syntax errors in the configuration (e.g. invalid unicode was provided for a configuration of type PROPERTIES), an error will occur when saving the configuration, which will have the general form of errors occurring when saving an artifact:

Figure 3. Error while saving an invalid application configuration

The user will remain in editing mode and will be able to correct any syntax errors and try saving the configuration again. ### Using configuration values in ScriptCode In ScriptCode, we can retrieve a value from the configuration using the configuration retrieval API:\ \ API: ```typescript interface Api { config: { v1: { get(key: string): string; getOrDefault(key: string, defaultValue: string): string; } } } ``` example script using the API: ```javascript function callService(context) { let value1 try { value1 = api.config.v1.get("dummy.url2"); } catch(e) { value1 = "default" } var value2 = api.config.v1.get("dummy.url"); var value3 = api.config.v1.getOrDefault("not_existing_key", "defaultValue") return [{'value1': value1, 'value2': value2, 'value3': value3}]; } ``` {% hint style="info" %} \*The API also works for script calls in the data model. {% endhint %} The editor also offers suggestions:

Figure 4. Example of a suggestion while typing code

#### Using configuration values in a script task Example script task: ```javascript function handle(task, context) { // Retrieve variables from the configuration const skipTask = api.config.v1.get("script.task.skip.task") const titleName = api.config.v1.getOrDefault("script.task.title.name", "Default title") // Finish the task and pass variables (skipTask, titleName) to the process context.complete({'skipTask': skipTask, 'titleName': titleName}); } ``` use in the process:

Figure 5. Example of using configuration values in a process

As a result, the values from the configuration will be passed to the process and saved under the keys: skipTask and titleName. {% hint style="info" %} Business configuration in Eximee: [Business Application Configuration](https://eximee.com/business-application-configuration/) {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.eximee.com/documentation/documentation-en/zarzadzanie-aplikacja-biznesowa/zarzadzanie-konfiguracja/konfiguracja-aplikacji-biznesowej-serwer-konfiguracji/konfiguracja-z-poziomu-low-code.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.