We are designing a Travel & Living approval process in ENOVIA 2026x.
Proposed structure:
Parent Route (Travel & Living)
- Estimates Approval Subroute
- Actuals Approval Subroute
Requirements:
- Actuals approvals cannot begin until Estimates approvals are complete
- Maintain traceability between both approval packages
- Minimize user effort when creating routes
Questions:
- What is the recommended ENOVIA 2026x approach for implementing dependencies between parent and subroutes?
- Can subroutes be automatically generated from route templates?
- Is a Parent Route - subroute model preferable to Change Orders for this use case?
