Navigating Your Workday: A Guide to Appian Sites

In our previous posts, we built a robust data model for our fictional company, Acme Auto, and secured it with precise permissions. But how do users actually interact with this underlying data? They do it through Appian Sites. Sites provide a tailored, branded frontend experience that gives logged-in users quick access to the exact information and tasks they need to do their jobs efficiently. Let's explore what makes up an Appian site!

Navigating the Interface

When an Acme Auto registrar logs in, they might first land on a comprehensive list of all vehicles in the fleet. From there, they can easily drill down into specific vehicle details by simply clicking a VIN.

Navigation is intuitively handled via a header bar where users can click between different site pages, or use a dropdown menu to access other workspaces and sites they have permission to view. The user menu also allows them to update their profile, adjust settings, or log out. For larger applications, developers can organize related pages into page groups using dropdowns or a sidebar layout. Best of all, these sites automatically work on mobile devices without any extra configuration—developers just need to ensure their underlying interfaces are optimized for different screen sizes.

Common Site Pages

Each page within an Appian site features a unique name and icon so users understand its purpose at a glance. While you can build almost anything, the most commonly used pages include:

• Record Lists: A primary view of your data, like the initial vehicle list the registrar sees upon logging in.
• Reports and Dashboards: A dedicated report tab might show the registrar a breakdown of the fleet by vehicle age or a list of vehicles they've personally added. More complex sites often open to a home page dashboard loaded with KPIs, charts, and data grids so users can see vital, high-level information immediately.
• Process Forms: A page containing a form allows users to seamlessly kick off business processes, such as adding a brand new vehicle to the Acme Auto fleet.
• Tasks: A specific page dedicated entirely to a user's awaiting tasks helps keep their daily work organized and prioritized.

Connecting the Backend

While the site is the frontend that the end-user sees, it acts as a container for other backend Appian objects. The actual contents of these pages are powered by the very record types, interfaces, and process models that developers build behind the scenes.

Tailored for Every Role

A major advantage of Appian Sites is the ability to create highly specific experiences for different roles while maintaining standard company branding. For Acme Auto, you could build entirely separate sites for supervisors and mechanics, or you can simply grant different user groups customized views within a single shared site.

Ultimately, sites are designed to tie your entire application together, allowing your end users to navigate swiftly and intuitively between their most important pages and tasks throughout their workday.