The information provided in this guide is provided within the scope of the application hotfix development and deployment to a production environment. The guidelines and practices outlined here are not meant to be used for supporting concurrent feature…

Overview Over time, user accounts need to be created, updated, and deactivated. Customers who have an existing user directory can use the LDAP Tools plug-in to automatically mirror these changes to Appian without requiring users to work manually through…

RPA Development Best Practices enhance application quality and reduce troubleshooting time. These best practices should be followed, in addition to Appian Documentation . Ensuring that best practices are followed from the beginning maximizes the chances…

Acceptance Criteria Overview Acceptance Criteria, also called "Conditions of Satisfaction", are items that a user story must meet in order to deliver the functionality agreed to by the Product Owner. They provide the necessary details to define the…

This guide deals with writing database scripts which can be rerun (‘rerunnable’). Creating rerunnable scripts makes deployments easier and avoids any unwanted behavior if the code were to run more than once. When modifying or updating a database, running…

There are several questions you need to answer before determining how users will access the system: How will new users be created? How will existing users’ profiles be updated? How will users who should no longer have access to the system be deactivated…

Automated testing reduces the amount of manual testing necessary in an Appian application and reduces risk at each stage of the application development lifecycle. Automated testing can be used throughout the Appian application development lifecycle to…

A hardening sprint is a period of a project where the team stops delivering new features and instead focuses on fixing bugs, preparing deployment activities, performing various types of testing, and cleaning up tech debt. What is the Value of Hardening…

This article provides guidance to application delivery teams regarding the planning and execution of User Acceptance Testing , commonly known as UAT. Although UAT is typically carried out by customer resources, it is important that all team members understand…

Introduction When deploying process model changes to a higher environment, in-flight (active) process instances continue to use the pre-deployment process model version. Additionally, the pre-deployment CDT version is used within these in-flight process…

What is System Integration Testing System Integration Testing (SIT) is the execution of tests to ensure that the different components of an application (Appian application, legacy systems, third party applications, data sources) are integrated and functioning…

Exploratory Testing Overview Exploratory Testing (ET) is a risk-focused testing method in which testers explore systems to identify areas of risk, in addition to checking expected functionality. As testing reveals risks, the tester uses what they have…

Appian provides several DevOps tools to automate the deployment of Appian applications such as Compare & Deploy and Deployment APIs. The Deployment APIs offer a set of API endpoints that allow you to inspect and deploy applications, packages, import…

Skills Covered A key benefit of the Appian platform is that it allows you to create and store development and design objects so you can easily retrieve them for future use. A developer needs to consider reuse in the way a component is built. To enable…

Heuristics of Complex User Stories While scoping, prioritizing and designing user stories for the Appian platform, pay close attention to the technical design and implementation of user stories exhibiting the following heuristics. Appian recommends…