User configuration module

This section describes the runtime configuration of the frontend, to see the configuration of the application on startup see Settings.

Front-end configuration

It is possible to perform simple configuration of the MO frontend using the configuration module.

Configuration database

To use the configuration module, MO needs a database to store the configuration. The connection parameters must be set in the MO Settings under [configuration.database].

Available options

Currently, it is only possible to configure options for OUs. The currently available options are:

  • show_location Indicates whether the location of units should be visible in the top of the page.
  • show_user_key Indicates whether the user key of units should be visible in the top of the page.
  • show_roles Indicates whether the column Roller should be shown in the OU overview
  • show_kle Indicates whether the column KLE-opmærkninger should be shown in the OU overview
  • show_time_planning Indicates whether the time planning field should be enabled for OUs
  • show_level Indicates whether the level field should be enabled for OUs
  • show_primary_engagement Indicates whether the ‘primary’ column should be enabled for engagements
  • show_primary_association Indicates whether the ‘primary’ column should be enabled for associations
  • show_org_unit_button Indicates whether to show the external integration button for OUs
  • manager_inheritance Whether manager inheritance should be enabled for the UI
  • substitute_roles Comma-separated list of uuids of association-roles for which having a substitute is possible
  • extension_field_ui_labels Comma-separated list of labels used when displaying extension attributes
  • show_engagement_hyperlink Whether to hyperlink to the detailed engagement page

If a option is identicated for a given unit, this will be used. If the option is not available, it will inherit the value from the nearest parent in the tree with the value set. If no parent has a value for the particular option, a global value will be used.

Reading configuration options

Currently active options

The currently active options for a unit can be read directly from the API call for the particular OU:

curl http://localhost/service/ou/799aeaa4-129b-4f47-8632-1ee6ce987b21

Included in the response will be an output similar to:


From this response, it is not possible to distinguish if the option is local, inherited or global.

OU specific options

The actual configuration options set directly on the OU, can be read from the dedicated configuration api:

curl http://localhost/service/ou/cc238af7-f00f-422f-a415-6fba0f96febd/configuration

The reply could be:


In this case the value for show_user_key will be read from this configuration value, and the rest of the configuration options will be inherited or read from global scope.

Global options

The current global options can also be read from the configuration api:

curl http://localhost/service/o/configuration

With the reply:

   "show_location": "True",
   "show_roles": "True",
   "show_user_key": "True"

Global options are global for all organisations.

Writing configuration options

The payload for updating global or OU-specific settings are identical:

     "show_roles": "False"

Currently, there are only settings for org units and thus the outer key will always be "org_units". It is possible to update more than one key per request.

Global options

To update a global options:

curl -X POST -H "Content-Type: application/json" --data '{"org_units": {"show_roles": "False"}}' http://localhost/service/configuration

OU specific options

To update or create a option for a specific OU:

curl -X POST -H "Content-Type: application/json" --data '{org_units": {"show_user_keys": "False"}}' http://localhost/service/ou/cc238af7-f00f-422f-a415-6fba0f96febd/configuration