Allow for PI AF templates to be version controlled. Include the ability to revert to previous template version, or continue to use old versions for specific elements. This will reduce the risk of deployment and improve change/release management process.
Template versioning is not even half as capable as what SVN or GIT could do for a DEV team.
Template versioning allows us to version a particular Element or Template Element, but we cannot version a subset of templates together under the same version
There is no Branching & Merging
Rollbacks and History: Element Template Versioning can't hard-reset your entire codebase back to a specific commit ID, effectively wiping out or archiving subsequent commits.
Granularity: Element Template Versioning tracks changes on a particular template, but it doesn't allow creating a subset of templates to be tracked together on a particular change.
No easy or automated handling between Pre-Prod/DEV and Prod Environments for template deployments. (NO CI/CD Pipelines)
Please consider adding this feature to work similar to individual Element versioning. We are heavy template users, and being able to manage template versions or roll back would be very helpful for our data and change management processes.
This would be a very valuable feature to have, especially so we can quickly revert changes that cause parts of our model to break while working on a fix.