Configuration Editor
The Administration > Configuration page edits the instance env-config.json file,
stored in Alfresco. It is restricted to members of the
GROUP_PRISTY_MARCHES_ADMINISTRATORS group.
This page is shared by Pristy Portail, Pristy Espaces and Pristy Marchés: its three tabs, the definition of an option, saving, raw editing and versions are described in the Configuration page. This page only describes what is specific to Pristy Marchés.
Options specific to Pristy Marchés
CLASSIFICATION_PLAN_ENABLED- Enables the classification plan feature.
CLASSIFICATION_PLAN_NAME- Name of the global plan file, for example
plan-marches.json. CLASSIFICATION_PLAN_ALLOW_NO_NATURE- Allows a file to be deposited without a nature.
CLASSIFICATION_PLAN_FULL_VIEW_THRESHOLD- Number of files from which the deposit shows a progress bar and status filters (5 by default).
CLASSIFICATION_PLAN_INLINE_METADATA_THRESHOLD- Maximum number of fields of a nature for its metadata to be entered on the file row (3 by default).
CLASSIFICATION_PLAN_NATURE_CODE_PROPERTYAlfrescoproperty in which the deposit writes the nature code; empty by default, the code is then not written.FILENAME_NATURE_DETECTION- Offers detection of the nature from the file name.
SHOW_MONTANT_MARCHE- Shows the Market price field in the consultation creation and modification forms.
DASHBOARD_PERSONAL_ENABLED- Allows each user to customise their dashboard.
SEARCH_USER_QUERY- Template of the search query, where
%sreceives the text entered; the shipped file also searches the consultation and market numbers and subjects. SEARCH_FACET,SEARCH_FACET_QUERIES- Facets offered to refine the search (see below).
SHOW_ACA_LOGIN_LINK- Shows, on the login page, a link to
Alfresco Content Application. OPEN_PDF_WITH_COLLABORA- Opens PDFs in
Collaborainstead of the built-in viewer. METADATA,ASPECTS,CONSTRAINTS- Displayed properties: preferably edit them from the Metadata page.
PREVIEW_URL, the address of share links, is a server-side option: it is set
at deployment and does not appear on this page.
The env-config.json file of an instance installed before version 26.1 contains three keys
LIST_COLLECTIVITES, LIST_TYPE_CONTRATS and LIST_PROCEDURES. They are not read by the application:
the corresponding lists come from the dictionaries of the classification plan. Changing them
has no effect, and leaving them in place keeps the confusion alive.
Customising the search facets
The shipped file offers six facets (SEARCH_FACET) and two groups of dates
(SEARCH_FACET_QUERIES):
| Facet | Queried field | Label key |
|---|---|---|
| Direction | SITE | facets.fields.location |
| Market Type | mm:typeMarche | facets.fields.market_type |
| Procedure Type | mm:typeProcedure | facets.fields.procedure_type |
| File Type | content.mimetype | facets.fields.file_type |
| Document Type | pm:natureDocument | facets.fields.document_type |
| Additional information | mm:infoComplementaire | facets.fields.info_complementaire |
| Creation Date | mm:dateCreation | facets.categories.creationDate |
| Notification Date | mm:dateNotification | facets.categories.notificationDate |
A SEARCH_FACET facet declares a field, a mincount and a label. A
SEARCH_FACET_QUERIES entry declares a query, a label and the group under which it
is displayed.
The label is a translation key. The application already knows facets.fields.code_budget
(“Budget code”) and facets.fields.titulaire (“Market holder”), which are not
used by the shipped file. The label of a new key is added in the
locales/fr.json file deployed with the web application, which completes and overrides the
application’s translations.
Options with no effect
SHOW_FAVORITES, SHOW_RECENT, SHOW_SEARCH, THEME, ALLOWED_FILE_EXTENSIONS,
BREADCRUMB_ROOT_URL and MIME_TYPES may appear in the file, but Pristy
Marchés does not read them: changing them changes nothing.
Last Update - November 5, 2026