Classification plan
The classification plan is the cornerstone of the configuration. It describes the expected folder tree, the document natures, the phases, the metadata requested at deposit and the reference lists of the forms.
The shipped plan
The Pristy Marchés Bootstrap places the
plan plan-marches.json and designates it as the global plan. It includes 173 natures, 15
locations, the three phases Préparation, Passation and Execution, and the three
dictionaries expected by the application. Its views are described in
view management.
This plan is a starting point: adapt it to your organisation, in particular the dictionaries.
Some natures set the mm:executionTransmission mark on the deposited documents.
When a contract is notified, the documents of the lot that carry this mark are copied
to the contract documents folder. Removing the mark from a nature excludes it from this
copy.
Without an active global classification plan, the application is largely inoperative: the Views mode shows nothing, the deposit has no destination, and three required fields of the consultation creation form stay empty. It is the first thing to set up on a new instance.
The Classification Plan page
It is reached through Administration > Classification Plan and is divided into two blocks.
The global plan
A drop-down list designates the plan applied to the whole application. A banner shows the current state:
- Active plan: name as information, when a plan is designated,
- No classification plan as a warning, otherwise.
The Save button is only enabled if your choice differs from the plan in place. The choice
is written to the CLASSIFICATION_PLAN_NAME option. The Edit button opens the active
plan in the editor.
The list of plans
The second block lists the available plans. You can:
- Create a plan,
- Import an existing plan from a file,
- open a plan to edit it.
Several plans can coexist in the instance; only one is active. This is the clean way to prepare a change: duplicate the plan in production, rework the copy, then switch the global plan when it is ready.
Editing a plan
The editor opens on eight tabs, nine when the AI context is available.
| Tab | Content |
|---|---|
| Information | the plan name, its short description, an “About this plan” text in Markdown and the “Views used”, where a referenced but missing view is flagged “Missing file” |
| Natures | the document natures, their destination location, their fields and the phases where they are offered |
| Fields | the metadata requested at deposit, and their type |
| Locations | the target folders of the folder tree, designated by a code |
| Folder tree | read-only, the folder tree the plan can create, each nature filed in its location, with Export as PDF |
| Phases | the main stages of the lifecycle, which structure the Views mode |
| Dictionaries | the key / label value lists |
| Lexicons | the mappings used in particular by detection from the file name |
| AI context | shown only if Pristy Core offers the ai.workspace-context capability |
In the shared library, this tab is called “Categories”. Pristy Marchés renames it Phases, to match the vocabulary of public procurement. It is the same object.
Each tab has a filter, and the Export, Import and Reload buttons. Changes are not applied as you go: they must be confirmed with Save File.
After an Import, the application reminds you explicitly: “The classification plan has been imported. Don’t forget to save.” Leaving the page without saving loses the import.
File naming
The name of a plan must start with plan-. The application rejects any other name with
“The filename must start with ‘plan-’”. Plans are stored in the
Data Dictionary/Pristy - Configuration/marches folder of Alfresco, and versioned on each save.
Safeguards on deletion
The editor refuses to delete an item that is still in use, and says so:
| Message | What to do |
|---|---|
| Field “name” is used in at least one nature or location. | remove the field from the natures and locations concerned first |
| Location “code” is used in at least one nature. | reassign the natures concerned |
| Source “id” is used in at least one field. | change the fields that rely on this dictionary |
These refusals are a protection: deleting a referenced item would make the plan inconsistent and would block deposits.
Automatically created fields
When creating a nature or a location, the editor can create a field for you and report it: “Field ‘name’ was created automatically.” These fields carry the mention Auto-created for… in the Fields tab. Review them: their type and whether they are required deserve checking.
Natures and file names
A nature has no “single” or “multiple” setting. At deposit, a file whose computed name already exists in the destination folder receives a distinct name. On requalification, the application asks “A document already has this name” and offers Update (the file becomes a new version of the existing document), Add a number or Correct.
The required dictionaries
Three dictionaries are expected by Pristy Marchés:
| Identifier | Feeds |
|---|---|
COLLECTIVITES | the Buyer field and the Partner buyers |
TYPE_CONTRATS | the Contract type field |
TYPE_PROCEDURES | the Procedure type field |
The Classification Plan page shows one error message per missing dictionary, naming it.
As long as a dictionary is missing, the matching drop-down list stays empty: no value is taken from the configuration. A missing dictionary must therefore be added to the plan.
Related options
Four options of the Configuration page govern the behaviour of the plan:
| Option | Effect |
|---|---|
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 |
FILENAME_NATURE_DETECTION | offers detection of the nature from the file name |
Checking the result
A plan is validated in real conditions, not by rereading the file:
- open a consultation and check that the phases banner is complete,
- start a deposit and check that each phase offers the expected natures,
- check the destination announced at the summary step of the deposit,
- open the consultation creation form and check that the three drop-down lists coming from the dictionaries are filled.
A plan inconsistent with the actual folder tree shows up at deposit as “The choosing folder does not exist or is missing.” or “Value not found in parent folders. Deposit is blocked.”
Last Update - November 5, 2026