Creation
This flow configures the course of a content or business object creation: what the user enters, what Any computes, and what is checked before the save.
It applies to contents as well as to business objects. A switch moves from one configuration to the other. Actions can be chained.
Content creation
The actions follow one another in this order: the choice of templates, an inheritance, a form (mandatory), a metadata uniqueness, a relation creation, a set of metadata composers, a propagation (package and relation only), then the application of a lifecycle.
Package-based creation
When the creation template is a package whose components are themselves templates, the flow is evaluated several times:
- a first pass creates the package.
- after the form step and the relation creation, the flow is re-evaluated to create each of the components: the uniqueness is not evaluated on the components.
- once every component is created and added to the package, the first pass resumes where it stopped, at the steps that follow the form.
This order has a useful consequence: the end-of-flow steps see an already filled package, which propagates, for instance, metadata from the package to the components that have just been created.
Relation creation
Metadata can be propagated from the created content to the content targeted by the relation, provided the relation is carried by the created content: that is, that it goes from the parent to the child.
Business object creation
The actions follow one another in this order: a metadata uniqueness, a set of metadata composers, then the application of a lifecycle.
Available actions for contents
Templates: templates offered at creation. Mandatory.
Metadata inheritance: inheritance applied to the content.
Form: input form. Mandatory.
Metadata uniqueness: uniqueness check applied.
Relation: relation created with another content.
Metadata composer: composer applied.
Metadata propagation: propagation applied.
Lifecycle: lifecycle applied to the content.
Components: automatic attachment of components to the created package.
Transfer metadata: saves, or not, the metadata into the primary format.
- Save into the primary format / Do not save.
- The format is only changed if needed, and only if it handles metadata transfer.
- If the primary content is changed, a Transfer metadata audit is generated (advanced display: "Metadata saved into the format: DOCX/XLSX").
Available actions for business objects
Page: Data Object page displayed at creation. Mandatory.
Metadata uniqueness: uniqueness check applied.
Metadata composer: composer applied.
Lifecycle: lifecycle applied to the business object.