Getting Started with Appian: A Look Inside the Acme Auto App

What exactly is an Appian application? At its core, an Appian application is a container that holds a collection of various design objects to solve one or multiple business use cases. To understand how this works in practice, let's explore Appian through the lens of Acme Auto, a fictional company that uses the platform to manage its fleet of corporate vehicles.

The Business User Experience For employees like registrars, mechanics, and supervisors, Appian provides a dedicated site to get their daily work done. Upon logging in, they can view a homepage dashboard complete with Key Performance Indicators (KPIs), search capabilities, and a list of vehicles needing review.

Clicking on a specific vehicle reveals a detailed summary featuring maintenance information, recent events, and an AI chat tool designed to provide quick insights. From this summary, users can immediately take action, such as requesting maintenance or clicking an "UPDATE VEHICLE" button to fill out a form and seamlessly update the vehicle's backend data. With the ability to navigate to different pages—like the maintenance department or fleet reports—the site provides a comprehensive view of the entire business.

The Developer Experience: Inside Appian Designer On the backend, developers build these cohesive user experiences using design objects. Using the Navigation Menu dropdown, users with the correct system permissions can easily access different workspaces, including Appian Designer.

Appian Designer acts as the primary workspace for developers, featuring an Applications view that lists all applications within the environment. When developers open a specific application, they start in the Plan view, which gives them access to Appian Composer, an AI-powered planning and building tool. By switching to the Build view, developers can then see, create, and configure all the specific design objects that extend the application's functionality.

The Core Building Blocks Design objects are the true building blocks of Appian, providing essential capabilities like data management, process execution, user experiences, and AI functionality. Here are the primary objects developers use:

• Sites: These act as the user-facing entry points to the application, organizing the various pages and navigation menus.
• Interfaces: These determine what the users see and how they interact with the app, encompassing dashboards, data grids, and forms. Interfaces can be highly customized, allowing developers to set required fields or enforce character limits on text inputs.
• Record Types: These objects connect to and model your enterprise data. For instance, a Vehicle record type can connect directly to vehicle data stored in a database table to power the lists you see on a dashboard.
• Groups: Groups represent users who share a common role and are heavily utilized to configure security and visibility. Thanks to groups, a registrar viewing the site will see a list of fleet vehicles, while a mechanic logging into the exact same site will instead see a list of their assigned maintenance requests.
• Process Models: These are the engines that automate your business workflows. When a user adds a new vehicle, a process model opens the necessary form, writes the new data upon submission, and manages what happens at each step of the process. Developers can even embed AI agents into these process models to evaluate submitted vehicle data against company policies and return a final risk summary.

Ultimately, these design objects work together seamlessly under the hood. By securely managing the flow of data, automating complex business processes, and guiding the user experience, Appian provides a powerful, block-by-block approach to building modern enterprise applications.