This page outlines the various methods to deploy a package from one environment to another, and which method is best for each type of environment.
When you deploy a package, changes are taken from the source environment and moved to the target environment. Some common deployment paths include:
|Source Environment||Target Environment|
|Development 1||Development 2|
|Break Fix / Hotfix||Development|
The optimal approach depends on the security considerations of your source and target environments, as well as the type of changes you have. Whether you are deploying one or more applications, packages, environment specific data, Admin Console settings, or a mix of these can impact how you decide to deploy. There are three methods for deploying a package in Appian:
Additional logic can be run after direct or external deployments by configuring a post-deployment process.
If you're an Appian RPA customer, remember you'll need to package and deploy robotic processes separately from applications. Learn how to deploy robotic processes and apps.
Appian recommends that production deployments be performed during off-peak hours. A maintenance window can be scheduled in the Administration Console, if necessary. Also, consider adding a post-deployment process to your application to automate any tasks and make your development lifecycle more efficient
If you are moving complete applications from a staging environment to a production environment, take standard precautions to ensure continuity:
Compare and deploy is the easiest and recommended method of deployment. If your DevOps infrastructure is set up, you can enable these connected environments to interact and directly deploy changes from one to another without manually downloading and uploading .zip files. For deployments to higher environments such as Production, you can require a review process by enabling it in the Administration Console
The compare and deploy feature guides you through a few straightforward steps:
Within compare and deploy, you can deploy:
If you’re unsure about what you should deploy, check the table below to see which best matches your use case. You'll be prompted to choose one of these options when you reach the Prepare deployment step.
|Deployment Contents||Reason||More Information|
|Entire application||If the application does not exist in your target environment, you will deploy your entire application. You should also deploy an entire application if changes have been made to the application properties, such as application name, description, application actions, security, or post-deployment process.||You can include database scripts and plug-ins with your application deployment.|
|Package||If the application already exists in your target environment, you can create a package or select an existing package to deploy. To learn how to create a package, check out our Packaging Process.||You can include database scripts and plug-ins when you deploy your package.|
|ONLY database scripts or plug-ins||If your application already exists in your target environment and you only need to deploy plug-ins or make changes to the environment's database via scripts, you can deploy these changes without objects. Database scripts and plug-ins can only be deployed to a target environment using compare and deploy if you are an application administrator.||To deploy database scripts and plug-ins without other objects, the application must already exist in your target environment.|
Once you've determined what needs to be deployed, check that your deployment contents are prepared and ready to be sent to your target environment. If you're deploying a package, make sure that you've properly prepared it for deployment.
After everything has been prepared, it's time to start the compare and deploy process.
To start compare and deploy:
If you don't see any connected environments available, see DevOps infrastructure to learn more about setting up connected environments for deployments.
The Prepare Deployment step helps you get all the objects, database scripts, and plug-ins together for deployment and check out any changes that have been made to objects.
In the Prepare Deployment step, you can:
The Prepare Deployment step compares the objects in the application in your current environment to the target environment.
This comparison determines if the objects that you're deploying:
If the application and objects that you're deploying already exist in your target environment, you can check the status to see which objects have changed.
To check an object's status:
From the Prepare Deployment step, there are three options for deployment:
Skip to the relevant section for what you're deploying.
To review an entire application for deployment:
To review a package for deployment:
Database scripts and plug-ins can be deployed on their own or included within the deployment of an application or package.
Database scripts and plug-ins are not exported along with packages and application objects, so skip this step if you do not have permission to deploy directly to the target environment.
If you're deploying database scripts or plug-ins without any application objects:
To deploy database scripts:
For information on using database scripts and record types with sync enabled, see force sync on import.
Appian must be able to successfully run the scripts before it can attempt to deploy the objects. If an error occurs during script execution, the deployment will stop. To resolve script errors, refer to the deployment log for further details.
To deploy plug-ins:
The Inspect Deployment step checks all of the objects in your package for security warnings, failing test cases, and missing precedents. This step eliminates most manual checks and helps you to identify and resolve issues with the objects in your package.
If you are only deploying database scripts or plug-ins, there is no inspection required at this step but you should review them manually before deployment. Note that if a database script or plug-in fails during deployment, Appian will attempt to rollback changes. For more information on resolving problems with your deployment, see the deployment log.
To inspect your package for deployment:
Warnings are informational and are simply meant to call attention to potential issues before deployment. Warnings will not block your deployment.
Your deployment is almost ready to go. Just review a few high-level details to confirm that this is the information that you want displayed in the deployments view and you’re ready to deploy.
To complete your deployment:
Exporting a package will only include the objects included in that package. It won't include database scripts or plug-ins.
A confirmation dialog will appear once the deployment has been sent to the target environment.
Once your deployment is in progress, the deployment details will be available on the deployments view of both the source and target environments. Deployment details are only visible to system administrators and application administrators.
If your deployment requires review, application administrators and users in the reviewer group will receive an email about the pending deployment. They can approve or reject deployments in the deployments details view.
Appian has native deployment APIs that can be called from external tools, such as Jenkins. There are five endpoints that allow you to inspect and deploy packages, import customization files, and database scripts.
This allows you to programmatically trigger deployments and integrate your Appian release into an automated pipeline. You can set up your pipeline once and run it the exact same way for all future deployments, saving time and avoiding manual errors.
In order to programmatically deploy Administration Console settings or tightly integrate with a version control system to store and retrieve package files, use the Automated Deployment Manager. For more information on setting it up, see the DevOps Quick Start Guide.
Packages can be manually exported from the source environment and then imported into the target. Import and export details are available in the deployments view of every environment. Appian recommends using manual export and import if you do not have environments added to your infrastructure. To deploy objects, plug-ins, import customization files, and database scripts directly to another environment, connect your environments and use compare and deploy.
Import customization files can be included in your packages for manual export and import, but other dependencies, such as changes to Administration Console settings, database scripts, and plug-ins must be handled separately.
Once you've checked your application for missing precedents, you're ready to export your package.
To export an application:
You can also download an application from the application contents view by selecting Export Application in the gear menu.
To export a package:
Exported packages will be automatically deleted after 30 days and will no longer be available for download as attachments. You can change the number of days before export package cleanup in the Admin Console Settings.
Since you can't undo an import, you should always inspect a package before completing the import to check for warnings, conflicts, or missing precedents. Inspecting objects identifies general issues, such as missing dependencies, data stores that don't match the schema on the target environment, and package corruption or invalid XML.
Inspect may not report some errors. Insufficient permissions, duplicate object names, other users editing the object, and missing import customization files are some issues that can cause import failures but are not reported when inspecting objects.
Importing a package at the application level will not add objects to a specific application. You must re-import the package inside the correct application.
Importing an application into another application will add objects to that specific application. You can remove them by selecting the imported objects and clicking REMOVE FROM APP in the toolbar.
To inspect and import a package:
To export multiple packages from the applications list view:
The IMPORT option in the applications view handles both applications and packages for multiple applications. When your import contains multiple packages, the corresponding objects are added to the appropriate applications, depending on where the packages were created.
It's a best practice to include data types created from web service definition languages (WSDLs) in your package before exporting it. If those data types are not included in your package AND they don't already exist on the target environment, they'll be listed as problems in the inspection results. Data types that are normally created by the Call Web Service Smart Service or webservicequery() function during import cannot be created by the package inspection process.
Developers with viewer access to an application and objects are able to create, compare, and inspect packages across environments, and manually export them. Application administrators and system administrators on the source environment are the only roles able to directly deploy to the target using compare and deploy.
Before using compare and deploy, a system administrator account must be specified when setting up deployment configuration in the administration console. The Deploy As account must be in the service account role.
When manually importing a package, you must ensure that you can administer the application and the objects that it contains:
The Last Modified By field displays the user who most recently modified the object and the time at which it happened. If the object supports versioning, the Last Modified By information of previous versions are not affected.
Best Practice: Regardless of deployment method, we recommend using a group for each application called
When objects are deployed to another Appian environment, the deployed objects contain a reference to the users and groups listed in their rolemaps. For example, an exported Knowledge Center contains the list of users and groups with rights to the Knowledge Center.
Rolemap deployment rules:
If an object already exists on the target environment (an object exists there with the same UUID), then:
Because objects in a deployment aren't updated simultaneously, users may see some inconsistencies in their application behavior as objects are updated. For example, during a lengthy deployment, a constant may be updated but the process model that references the constant has not been updated yet.
During deployments that include a record type with sync enabled, the record type must successfully sync in that environment before it will be available. This may mean that your record type will be unavailable to users, processes, or APIs until the import is complete. For more information on record types with sync enabled, see Data Sync in Appian Records.
When deploying database scripts that add rows to the source table of a record type with sync enabled, you can use the force sync command in the import customization file to see the new rows from your source directly after import. The record type does not need to be in the deployment package in order to force a sync. Instead of forcing a sync, you can also wait for the next scheduled sync of the record type or trigger a manual sync on the record type object directly.
To force the sync on import:
recordType.<UUID>.forceSync = true.
<UUID>with your record type’s UUID.
To find your record type's UUID:
For more information on record types with sync enabled, see Data Sync in Appian Records.
Issues may be encountered for various reasons. For example, an error may occur when you are not an administrator of the object, or if you attempt to deploy a group with the same name as another group.
Best Practice: Inspect the package before deployment in order to identify issues ahead of time.
The deployment, including the export and import processes, does not stop when errors are encountered on specific objects.
However, a problem during the import of an object may cause the import of related objects to also fail. For example, a failure to create a group type during an import would cause the import of any groups of that type to also fail (Appian does not attempt to import these groups in this case).
If a group fails to be created during import, and the group exists in rolemaps for other objects - or is a member of another group - the other objects (or groups) will fail to import due to the missing precedent.
The deployment will completely stop when a database script cannot be executed. In this case, Appian will roll back all possible changes that have been executed so far - this will vary depending on your specific database server. Executing subsequent database scripts and deploying objects will not be attempted.
In each case an error occurs, Appian gathers and displays information on any problems after all objects in the package have been processed. Generally, you can do one of the following:
When using compare and deploy, a deployment log is generated. The log details the stages of your deployment - such as the sending and receiving of the deployment request, executing database scripts, and importing the objects - and whether they succeeded. Errors that occur during database script execution or object import are included here. For more information on object import errors, see below.
When manually importing, an import log is generated. Objects with import issues are placed in one of two sections at the top of the import log:
The following example illustrates the log entries that may be generated when an object reference is not included in the package, and is not present in the target environment.
In this instance, an imported process model listed an individual user for the assignment of an activity. We recommend using groups for assignments instead. Otherwise, ensure that the target environment has a user with the same username, prior to importing the application.
Additional sections in the import log include:
See the object comparison statuses for more information.
On This Page