View Management
A predefined view is a saved search that users browse like a folder list. It is the default navigation mode, and it only exists if you feed it.
The shipped views
The Pristy Marchés Bootstrap places 14
views, attached to the phases of the plan plan-marches.json:
| Phase | Views (file) |
|---|---|
| Préparation | none |
| Passation | PREPARATION (vue-preparation.json), DEFINITION (vue-passation-definition.json), CONSULTATION (vue-passation-consultation.json), OUVERTURE (vue-passation-ouverture.json), ONR (vue-passation-onr.json), ATTRIBUTION (vue-passation-attribution.json), NOTIFICATION (vue-passation-notification.json), PJ DEPENSES (vue-passation-pj-depenses.json), CONTROLE LEGALITE (vue-passation-controle-legalite.json), TRANSMISSION EXECUTION (vue-passation-transmission.json) |
| Execution | PIECES MARCHE (vue-execution-piece-marche.json), GESTION ADMINISTRATIVE (vue-execution-gestion-administrative.json), EXECUTION FINANCIERE (vue-execution-execution-financiere.json), SUIVI TECHNIQUE (vue-execution-suivi-technique.json) |
The Passation and Execution phases of the plan also reference a vue-fichiers.json view,
which is not shipped: the Information tab of the plan editor flags it
“Missing file”.
The View Management page
Administration > View Management lists the existing views. Each one is a
vue-*.json file of the instance configuration folder.
This page lets you create a new view, open a view to edit it, export it, import it or delete it. Deletion asks for confirmation, naming the view.
The view editor
The editor has two columns: the query builder on the left, the test context and the results on the right.
The query builder
It is made of two blocks.
Locations delimits the search scope. Each location is set to Include or Exclude, with its type: a site or a folder. Without a location, the block shows “No locations defined.”
Criteria holds the conditions on the metadata: a field, a Condition and a Value. The block shows “No criteria. Click on ‘+’ to start.” as long as it is empty.
A view without any criterion can be saved, but is unusable: it shows users “This view has no search criteria configured.” Always check that a view produces a result before attaching it to a phase.
Testing before publishing
The Test context block is the most useful tool of the page. In this block you designate a Site / Workspace then, optionally, a real Consultation, and the Test button runs the view in this context.
You get two outputs:
- the Test results, that is what users will see,
- the Generated AFTS query, useful to understand why a view returns too many or too few items.
The list of consultations is only offered after a workspace is chosen: otherwise the application shows “Select a site first to see available consultations.”
Test on a representative consultation, divided into lots and with notified contracts. A view validated on an empty consultation proves nothing.
Saving the view
Saving asks for:
- the View identifier: technical and stable, for example
exec-pieces, - the View name: the label shown to users, for example Pièces du marché,
- a Description (optional).
The file produced is named vue-<identifier>.json. Like the other configuration
files, it is versioned on each save.
The identifier is the key that attaches the view to the phases of the classification plan. Changing it detaches the view from the phases that reference it, and it disappears from the interface without an error message.
Attaching views to phases
Creating a view does not make it visible: you still have to state in which phase it appears. This attachment is done in the classification plan, Phases tab: each phase has a Views column, and a View Selection selector lets you compose its list, with a search among the available views.
The relationship to remember:
- the view defines what to search for,
- the phase of the plan defines where it is displayed,
- the user sees the phases as tabs, and the views within each phase.
Diagnosing a view that is not displayed
| Symptom | Probable cause |
|---|---|
| The banner shows “No categories configured” | no phase is defined in the active plan |
| A phase is there, but without a view | no view is attached to this phase |
| “This view has no search criteria configured.” | the view has no criterion |
| The view is empty although documents exist | criteria too restrictive, badly delimited location, or documents not yet indexed |
The last case is settled with the test context and the generated AFTS query: if the query is correct and returns nothing, indexing is at fault, not the view.
Last Update - November 5, 2026