- A single project can use multiple approval policies, allowing different policies to be organized in separate files. Each can be maintained by a different team or stored at a different location while still applying all of these to the same project.
- Approval policies can now be assigned to a template, this allows enforcing certain policies on the created environments regardless of their location (the project it belongs to).
- It is now possible to execute both project and environment-level custom flows, this allows project admin to use custom flows to run validations and security checks while allowing environments to customize their hooks. Also, project-level custom flows apply on environments that sit under sub-projects, this allows utilizing the project / sub-projects hierarchy to configure custom flows.
- A single project can also use multiple custom flows now allowing different checks/ validations to be organized in separate custom flow files each can be maintained by a different team or stored at a different location while still applying all of these to the same project. You can also easily reorder the custom flows in the table to decide their execution order.
v3.0.731
you won’t have access to the new approval policies enhancements until you upgrade it.
To configure multiple approval policies/custom flows for a project you can go to the project’s policies settings page and click the +Add Custom Flow / Approval Policy
button:


+Add Approval Policy
button:
