This page describes how to delete both prepared and deployed packages.
A prepared package is defined as the package you prepare during development. A prepared package is not affected by any automatic removal settings that affect deployed packages. A prepared package can only be removed manually.
We recommend that you delete prepared packages in your source environment once the packages have been successfully deployed. This practice allows you to keep your applications clean, so long-running or unused packages don't build up over time. If your team works in sprints, you can also delete multiple packages in bulk at the end of each sprint or release.
To manually delete a prepared package:
During deployment, Appian keeps a ZIP file of the package contents at the time of deployment. This ZIP file is sometimes referred to as a deployed package or a deployment package. You can access this deployed package through the Deployments view.
A deployed package may start out as a prepared package before deployment, but any relationship to that prepared package ends at deployment. Deleting a deployed package does not affect the prepared package. Similarly, deleting a deployed package does not affect the original objects in the application. Keep in mind, however, that if you delete a succesfully deployed package that you only constructed during compare and deploy, you will delete any database scripts or plug-ins you added at that time.
It is a maintenance best practice to delete a deployed package as soon as it is no longer needed:
You can choose to delete the deployed package during a direct deployment or a manual export.
A system administrator can configure the Enable Periodic Cleanup of Deployment Packages option to automatically delete deployed packages after a certain number of days. This option does not delete prepared packages.
On This Page