Application Settings

Introduction

The application settings are maintained through the .restapplicationsettings file. (src/backend/.restapplicationsettings) Developers using B1 are free to add whatever properties they want to this file, to maintain any custom settings they might need within the application.

The settings work on a multi-layered system, allowing new settings to be automatically be picked up and, optionally, overriden. This is achieved through the dedicated "BaseConfig" property.

The B1 plattform ships with a dedicated json schema to provide easy access to all properties from within the application file itself.

The file itself is a json containing different properties, organized into categories/types.

It is recommended that the same format is followed for any custom properties, root level properties should be avoided for better isolation.

How-to: Reading the application settings from pro-code

💡

Because the application settings could contain sensitive information, not all application settings are exposed to the webui.

When adding backend-only application settings, a namespace starting with underscore ('_') should be used.

‣

Read the settings from OpenEdge backend

‣

Read the settings from the WebUI

Most common standard Settings

Attribute	Description	Example/Values
Deactivate frontend caching		`"memoryCache": { "menus": false, "repository": false },`
...	...

Back to Documentation

Back to Home Page