Introduction
In today's fast-paced business environments, efficient document approval management is essential.
Traditional approval processes often rely on manual intervention. But what if approvals could be triggered automatically, streamlining workflows with minimal effort?
In the current release (R2025xFD01), ENOVIA supports the automatic route creation for document object.
This happens when the maturity state changes from 'In Work' to 'Frozen', 'Frozen' to 'Released' or 'Released' to 'Obsolete'. This intelligent workflow ensures that the right stakeholders are notified and approvals happen seamlessly.
Let's dive into how this automation can be defined and configured in ENOVIA:
Step 1- Defining and Configuring Automatic Route Creation
User Profile – Leader
In R2025xFD01, we introduced a new 'Applies To' tab for Route Templates, enabling you to define rules for automatically creating routes based on the template.
- Enable Automatic Route Creation
Select the 'Create and start automatically a route from this template when the following event occurs' checkbox.
2. Define the Criteria
Policy:
Choose the governing policy for which the rule is being created.
For documents, select 'Document Release' as the policy
Type:
Specify the object type governed by the selected policy.
The available object types depend on the selected policy.
For documents, select 'Document' as the type.
Maturity Transition:
Select the maturity transition that triggers the route creation.
The route is created between the chosen maturity states.
The available transitions depend on the selected policy.
For documents, the following transitions are available:
In Work → Frozen
Frozen → Released
Released → Obsolete
3. Apply Additional Conditions (Optional)
To further refine the target documents for route creation, select the 'Condition to apply template on subset' checkbox.
Criteria:
Choose the criteria for defining the condition:
- Attribute
- Credentials
If 'Attribute' is selected as the criteria, specify the Attribute Name, choose the appropriate operator, and provide the Attribute Value.
Note: Currently, the 'Title' attribute is the only available attribute out of the box.
If 'Credentials' is selected as the criteria, the Platform Administrator can specify the Collaborative Space and Organization.
In this case, the Route Template will apply only if the specified Collaborative Space and Organization match those of the document.
Important Note: As a Leader, you can define the 'Apply To' setting, but you cannot specify the Collaborative Space and Organization for the Credential criteria.
Only the Platform Administrator has the authority to set these parameters.
Step 2- Releasing the Route Template
User Profile – Platform Administrator
The Platform Administrator receives a request notification to release the Route Template to make it available for use.
As a result, a ‘Require Route for Maturity Change’ rule is automatically added in the
‘Collaborative Spaces Configuration Center’ → ‘Maturity Graph’, based on the parameters specified
in the ‘Applies To’ tab.
If multiple templates are configured, the system will display multiple rules for the selected transition,
and multiple routes will be instantiated accordingly.
Step 3- Applying the Route Template
User Profile – Any Platform User
Once the configuration is complete and the template is released, a route will automatically be generated whenever a user triggers the selected maturity change for a document that meets the defined criteria.
As a result, the document’s lifecycle will be controlled by the route, preventing manual promotion of its maturity state.
The following video illustrates the process and shows how to automatically generate a route upon Document maturity changes:
