Changing the configuration from the application

Pristy Portail, Pristy Espaces and Pristy Marchés have the same Configuration page. It edits the application’s env-config.json file, stored in Alfresco under Pristy - Configuration/<application>, in the Data Dictionary. No server access is needed: a change takes effect when the application is reloaded.

Only the list of options differs from one application to another. They are described in the configuration options.

Accessing the page

Click Configuration in the administration section of the side menu:

ApplicationMenu sectionRestricted to
Pristy PortailAdministrationsuper administrators and members of GROUP_PRISTY_ADMINISTRATORS
Pristy EspacesAdministrationmembers of GROUP_PRISTY_ADMINISTRATORS
Pristy MarchésAdministrationmembers of GROUP_PRISTY_MARCHES_ADMINISTRATORS

The page offers three tabs: Structured Edition, Raw Edit (JSON) and Versions.

Structured edition

This is the tab for everyday use. The list on the left shows the options by group: Display, Applications, Authentication, Features, Classification plan, Rocket Chat, Matomo, Search, Pagination, Metadata, Security and Other. The Filter configurations… field finds an option by its key or its description.

Click an option to edit it in the right-hand panel, which shows its description, its type (Text, Number, Boolean, List, Object or Choice) and its default value. Lists have a dedicated editor, with Add item and a handle to reorder them.

The list combines the options present in the file and those the application knows without them being in the file yet. The latter are marked “This option is not defined”:

  • Define adds the option to the file, with its default value,
  • Undefine removes it from the file: the application goes back to the default value.

Leaving an option undefined and explicitly giving it its default value are not the same: an undefined option follows the product’s changes, a defined option keeps its value.

Changes stay in memory until you click Save, at the top of the page. Leaving the page with unsaved changes asks for confirmation.

Raw edit (JSON)

The tab shows the whole file in a JSON editor:

  • Format reindents the content,
  • Discard changes goes back to the saved file,
  • Save JSON fully replaces the configuration with the editor’s content. Invalid JSON is rejected.

It is also the only way to add an option the application does not know.

Below the editor, Choose a file and replace replaces the configuration with an env-config.json file from your computer.

Replacing with a file is done without confirmation. The editor rejects incorrect syntax, but not a valid yet incomplete configuration: check the file before uploading it.

Versions

Each save creates a version of the file. The Versions tab lists them, with the date, time and author of each one:

  • select a version to compare it with the current version,
  • download it,
  • or restore it.

Restoring creates a new version, with the comment “Restored from version n.”: nothing is overwritten. The most recent version cannot be restored onto itself.

What the page does not change

  • Server-side options (AUTH and the authentication options, ALFRESCO_HOST, PORTAIL_HOST, ACTES_HOST, PREVIEW_URL…) are neither read nor written by this page: the Pristy Core configuration endpoint filters them out. They are set at deployment.
  • The common configuration shared by all applications, including the list of the application switcher, is set from the Bootstrap page of Pristy Portail.

Last Update - November 5, 2026
Call To Action 📣

Try Pristy

You can try the Pristy demo by signing up using the link below.

Demander une démo