Metadata inheritance
This module pre-fills the creation or the import form: it designates the metadata a new content takes from its context: the template used, the selected content, the room, the current filters.
The information is already there when the user creates: they work in the room of a customer, under a filter on the current year, from a contract template. Making them type it again is time lost and an opportunity for error. The inherited metadata arrives filled in the creation dialog box, where it stays editable.
Select in the dual list the metadata to inherit.
Inheritance from context
These two options make the content inherit from what the user is looking at when they create it. Only the metadata present in the inheritance configuration is concerned.
Inherit active filters
The current filters serve as starting values for creation and import.
A filter is only retained if it designates a unique and certain value. A filter that expresses a choice or a range cannot pre-fill anything: there is no value to take.
The facet and editable filters are taken into account, as soon as they amount to an equality:
- "contains" and "contains whole phrase".
- a multiple value carrying a single value.
- a multiple value combined with an "AND".
Are ignored:
- the "advanced" filter compositions.
- the multiple values combined with an "OR" or a "NOR".
- the date ranges.
Date metadata follows the same rule: the date is only taken if it is neither a range nor a comparison (before or after another date). It can be complete (day, month, year) or partial (year, or year and month), whether it comes from the simple filter management or from the advanced one. A partial date is completed by default: to the first day of the month, and to January for the current year.
Inherit active view
The view and the level reached in that view serve as starting values for creation and import.
Resolution order
In both cases, a metadata is searched in this order, and the first source that carries it wins:
Room > (Folder or View + active filters) > Template > Selected content
Filters and views also serve to resolve the templates whose query holds wildcards ($). This resolution happens even when no inheritance of the filters or the views is possible.
Inheritance from the room or the folder
A metadata can also be taken from the room or the folder in which the user creates or imports. These values are the ones entered and saved in the form of the Room Metadata display and Folder Metadata display flows: a metadata can therefore be inherited this way only if it appears in the form configured in one of these flows. It must also be selected in the inheritance configuration.
In the resolution order above, the room comes before the folder.
Content selection's metadata inheritance
This part defines the default behavior:
- Enable at creation
- Enable at import: ticked by default.
These options change the behavior of creation and import when the flow tests whether an inheritance is possible and a selection is made: the "Inherit metadata from selected content" checkbox then takes the state configured here.
When the flow does not display a dialog box (quick creation or import), a confirmation is asked before the inheritance. If the matching option is enabled in the module, this confirmation is not asked.
Relation with the selection and the inherited template
Create a relation with selected content: creates a relation between the created content and the content that was selected at creation time. Select the relation to use.
Create a relation with the template: creates a relation between the created content and the template used for its creation. Select the relation to use.
Inherit from another source
Inheriting from another source finds the source in the first result of a GQL predicate. When that predicate relies on wildcards, they are resolved from the incoming metadata coming from the form step or from the incoming message, depending on the flow used.
Flows
This module can be used in the following flows: