Overview of functional administration
Who administers
The Administration section of the side menu only appears for members of the
PRISTY_MARCHES_ADMINISTRATORS group. The check queries the groups of the logged-in account;
an indirect membership, through a group nested in the administration group, is
therefore sufficient.
This group is not the same as ALFRESCO_ADMINISTRATORS. A super administrator
who does not belong to PRISTY_MARCHES_ADMINISTRATORS will not see the Pristy Marchés
Administration section.
Two rights combine for some actions: the Manager role on a direction is still required to modify a consultation you did not create, even as a Marchés administrator.
The five administration pages
| Page | Purpose |
|---|---|
| Configuration | edit the instance options |
| Metadata | choose the displayed properties and how they are presented |
| View Management | compose the predefined views |
| Classification Plan | define the folder tree, the document natures and the dictionaries |
| Dashboard | assemble the home page |
Where the configuration is stored
All this configuration lives in Alfresco, not in files placed on the
web server. It is stored in the Data Dictionary/Pristy - Configuration folder, under a sub-folder named
after the instance name: marches for this application.
This folder contains:
env-config.json: the instance options,plan-*.json: the classification plans,vue-*.json: the predefined views.
Setup by the Bootstrap
This folder and its initial content are created by the Pristy Portail Bootstrap, which offers three files for Pristy Marchés:
| File | Content |
|---|---|
Initialisation (init.yaml) | the PRISTY_MARCHES_ADMINISTRATORS group, the pristy-marches-service service account, the marches configuration folder, the Inbox Pristy Marches, Reload Pristy Marches and Error Pristy Marches folders under Pristy Marchés, the plan plan-marches.json, its 14 views and the document templates |
Démonstration (init-demo.yaml) | accounts, memberships and a demonstration workspace, to apply after the initialisation |
Configuration de Pristy Marchés (init-env-config.yaml) | the update of the env-config.json file only |
These files are versioned: each save creates a new version, and the configuration page lets you view and restore an earlier version. This is the safety net to know about before any significant change.
The configuration health check
For a super administrator, the application checks at startup that the
instance folder does exist under Pristy - Configuration. If it does not, a red
dot appears on the Settings button of the top bar. Other users,
members of PRISTY_MARCHES_ADMINISTRATORS included, do not see this dot.
The full message is shown on the About page, in the Settings menu:
The configuration folder for instance “marches” is not accessible at the expected Alfresco path. Search features (classification plan, etc.) may not work correctly.
Run “Bootstrap Pristy” from the Pristy Portail administration to create the instance folder.
As long as this message is present, there is no point looking elsewhere for the cause of a classification plan that does not load, or of empty drop-down lists: the configuration is not readable. The remedy is the Bootstrap given by the message; see also the About guide.
The About page runs this check again each time it is opened. It also shows the version of the application, its revision and its build date: the information to attach to a support request.
Last Update - November 5, 2026