Initially, I considered using deployment packages to track changes. However, I noticed that once changes are pushed from UAT to Production, the environments become synchronized. As a result, all objects appeared in the deployment package; however, the ones that were initially modified before being pushed to Production are no longer listed as 'modified.' This makes it difficult to track the specific changes made during that deployment.I'm looking for a reliable approach to maintain visibility into code changes with each deployment. Has anyone found a good solution or best practice for this scenario?
Discussion posts and replies are publicly visible
We implement traceability by adding every changed object to user stories, and note user stories in the code where the change happens.
Some store full app exports to a GIT repo.
In the end, it depends on what you want to achieve.
Once you deploy a package and the environments are synced, the "modified" status for objects resets, So you can’t rely on deployment packages alone to track changes.
A better approach is to use the Deployment History (which permanently logs everything that was deployed), check the version history of individual objects, and make use of the Compare & Deploy feature before pushing changes.
For full traceability, it’s best to integrate with an external source control system like Git or SVN and use Appian’s deployment APIs to export package details.Combining these methods will help you maintain a clear record of all changes, even after environments are synchronized.https://github.com/richardschoen/appiandeploymentapihttps://docs.appian.com/suite/help/25.2/Deployment_Rest_API.html