This page is about the deployment process in Appian and the different ways you can deploy updates to your applications. To learn how to deploy your applications and patches, see Deploy to Target Environments.
Deploying packages is how you release your application updates to end users and deliver value. To deploy, you select and package the objects you want to deploy, and then move those changes from a source to a target environment.
There are three methods for deploying a package in Appian:
Appian allows you to deploy different types of packages:
Make sure you understand object-specific behavior before importing or exporting packages for deployment.
Your packages may depend on other files or scripts such as:
Direct deployments are an out-of-the-box approach to simpler deployments, with fewer manual steps and predictable outcomes. This supports continuous delivery by allowing you to deploy packages frequently and reliably.
For those looking for a streamlined deployment process with minimal setup effort, Appian recommends using compare and deploy.
A post-deployment process is a process that automatically runs after a direct deployment has finished on an environment. From this process, you'll be able to access key information about the relevant deployment.
Post-deployment processes provide flexibility, which allows you to automate tasks, leverage third-party tools, and customize your workflow. Automating your post-deployment steps helps you reduce manual tasks and errors.
Appian offers a set of tools that helps organize your deployment processes and further reduces manual steps: the Automated Deployment Manager.
The Automated Deployment Manager consists of two tools:
These tools are best used in conjunction to enhance your deployment process.
For more information about the full benefits of continuous delivery through automated deployment, see the DevOps Quick Start Guide.
On This Page