Metadata Configuration

This page determines which Alfresco properties are visible in the information panel, the tables and the forms, how they are grouped and in what order.

This setting is editable in the interface, with a preview.

Page layout

Three areas:

  • on the left, the list of groups of metadata, each group matching an Alfresco aspect or type,
  • in the centre, the editor of the selected property,
  • on the right, the preview panel.

Groups carry the labels of the data model: Classification information, Consultation folder, Procurement folder, Consultation, Document information, Market information, Lot, Consultation actors, Period, Classification plan, as well as the standard aspects (General, Title, Audit, Content…).

On a new instance, the list shows “No metadata configured”.

Adding properties

The Add button offers two ways.

From a model

Metadata (from model) opens the Model Explorer, which lists the Aspects and Types of the Alfresco model, with a search field.

By selecting an aspect or a type, you see all its properties, with their identifier, their title, their data type and their Status: a property already selected is marked Already configured.

Tick the ones to add, then confirm with Add n property(ies).

This is the preferred way: it guarantees that the property identifier actually exists in the model, whereas manual entry can produce a metadata field that will never be filled.

A search field

Search field adds an entry that is not a property of the model, but a queryable field, for example TYPE, SITE or TEXT. You enter its Field identifier and its Title.

These fields are used by the criteria of the predefined views and of the search.

Setting up a property

The central editor exposes, for the selected property:

SettingRole
Property IDthe Alfresco identifier, for example mm:numConsultation
Titlethe displayed label
i18n key (labelId)the translation key, preferable to the title for a bilingual instance
Input typethe input mode (text, date, list…)
Displaythe contexts where the property appears
Read-onlyprevents changes from the interface
Orderthe position within its group
Aspect / Typethe link to the model

Display combines four contexts:

ContextThe property is
Edit formoffered in the property edit dialog
Properties panelshown in the Properties panel of the document
Viewsoffered as a criterion in the view editor
Cards and gridsoffered to each user under the documents in card and grid display, with the gear of these displays

Fill in the i18n key rather than the Title as soon as the instance is used in French and English: a hard-coded title is not translated.

A whole group is deleted with Delete group, in the group actions. Deleting a property requires explicit confirmation.

The preview

The Preview panel shows how the configuration renders on a dummy item, which saves looking for a real document to judge the result.

Edit values lets you fill this dummy item with values of your choice, to check how a date, a list or a long text is displayed. Reset values goes back to the default values.

Saving

Changes are not saved automatically. The Save button writes the configuration; the application confirms with “Configuration saved”.

When leaving the page with unsaved changes, the application asks for confirmation: “You have unsaved changes. Do you want to leave this page?” Answering yes loses the changes.

Saving updates the METADATA, ASPECTS and CONSTRAINTS entries of the instance env-config.json file. As this file is versioned, an unfortunate change can be undone from the Versions tab of the Configuration page.


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