Free cookie consent management tool by TermsFeed

Design Objects

On This Page

Applications contain a set of objects that function together to meet one or several business use cases. Applications allow these objects to be deployed from one environment to another.

When an object is created, it is assigned a universally unique identifier (UUID). This internal (hidden) property is not editable or configurable.

Each design object provides a specific piece of functionality, and each application contains many objects grouped by common purpose. Technically, applications do not contain these objects, but simply have a list of objects that are associated with them. The Objects view shows a list of objects ignoring the application association. The following sections describe each Appian object.

AI

AI objects allow you to integrate artificial intelligence into your applications. AI object icons appear in a purple-to-pink gradient in Appian Designer.

AI AgentAI Agent

An AI Agent is an intelligent assistant that you can integrate into your applications to automate complex, goal-driven processes. They reason through decisions, act on your data, and trigger workflows automatically so that your users can focus on higher-value work.

AI SkillAI Skill

Use the AI Skill to create, train, and use machine learning models in your applications. The AI Skill interface offers a low-code way to customize a model to your use case and specifications.

For example, train an AI Skill to classify documents that are passed to your process. Use the smart service output to route the process properly.

Data

Data objects store and structure the information your applications use. Data object icons appear orange in Appian Designer.

Record TypeRecord Type

A record type is the primary way to work with data in your applications and the foundation of Appian's data fabric. Each record type represents a major business concept or process, such as customers, orders, or cases. You can relate multiple record types from different sources to create a unified view of all your data.

Record types come with built-in features like record views, record lists, record actions, and record-level security.

Data TypeData Type

A custom data type (CDT) is a developer-defined data structure that represents a logical grouping of related data. You can use CDTs to:

Because a data type is always used in the context of another object, it does not have individual security settings.

Business process objectBusiness Process

The business process object allows you to deploy a process that was created in Process HQ.

A business process in Process HQ consists of a case record type, an event history record type, and any relevant related record types that contain data relevant to the case or its events.

Note:  You cannot create a business process from Appian Designer. Business processes are created in Process HQ and automatically appear in Appian Designer.

Integration

Integration objects connect your applications to external systems and services. Integration object icons appear bright green in Appian Designer.

Connected SystemConnected System

A connected system makes it easy to connect to databases and external web services. They provide a central location to store authentication details and connection information. Several authentication types—such as OAuth 2.0, API Key, and OpenID Connect—can only be used through a connected system.

You can deploy connected systems across environments alongside an import customization file, allowing you to use different authentication information for each environment.

IntegrationIntegration

An integration can be used to call external systems and web services from Appian. Integrations can be called in expressions, interfaces, web APIs, and process models to query or modify data in external systems. They can inherit connection details from a connected system.

Web APIWeb API

A web API provides a way to expose an Appian endpoint to an external system. When a client makes an HTTP request to the given URL, the associated expression is executed and the result is returned to the client. Web APIs can be used to push data to Appian, to pull data from Appian, and initiate Appian processes.

Event ConsumerEvent Consumer

An event consumer connects your Appian applications to Apache Kafka topics, allowing you to filter incoming events and take action on each one. The event consumer listens to a Kafka topic through an Apache Kafka connected system, filters events using an expression, and triggers an action for each matching event. Actions include starting a process model or writing event data directly to a record type.

User experience

User experience objects provide interactive displays for your application users. User experience object icons appear blue in Appian Designer.

InterfaceInterface

An interface is an object that returns one or more components to display on a record view, site page, or process form. This is the primary object that developers use to show user interfaces to application users.

SiteSite

A site is a customizable user interface where a developer can create focused work environments for signed-in users. When working in a site, users can view and submit tasks, view records, start actions, and view Process HQ reports and dashboards.

PortalPortal

A portal is a public web app that allows users access to Appian workflows and information without having to sign in to Appian. Portal users can submit or view information in a portal, and their actions can start processes in Appian.

A portal object allows you to configure the settings and content for your portal.

ReportReport

A report object allows you to deploy a report that was created in Process HQ. Reports can be viewed individually or included in a dashboard.

DashboardDashboard

A dashboard object allows you to deploy a dashboard that was created in Process HQ.

Control panel objectControl Panel

A control panel object is a set of configurations that make up the underlying structure of the Control Panel workspace. The control panel object allows developers to set guardrails for the configurations to data and interfaces made by business users in the Control Panel workspace.

Logic

Logic objects are used in expressions to reference specific values and perform complex operations or queries. Logic object icons appear purple in Appian Designer.

Expression RuleExpression Rule

An expression rule is a reusable piece of logic that you can call from interfaces, record types, process models, and other design objects throughout your application. Expression rules can query and transform data, perform calculations, and encapsulate common logic. You can add rule inputs to dynamically change the data an expression rule returns.

DecisionDecision

A decision is a grouping of business rules that answers a specific question based on inputs. Decisions are best used to encapsulate complex, business-specific logic.

Decisions can be called from any expression, so they can be reused across multiple objects throughout the system.

ConstantConstant

A constant holds a single literal value or list of values. A constant allows you to define a value once and then use it in many places in an application. If the value needs to be updated in the future, it only needs to be updated in one location. Constants are also used to reference other design objects in expressions.

The most common uses for constants include storing:

  • A single primitive value.
  • A list of text values.
  • A reference to an Appian object.

Translation set iconTranslation Set

The translation set object is a collection of translation strings that allow you to easily translate new and existing applications in multiple languages. Each translation string is a collection of values translated into multiple languages, and includes the necessary contextual information for developers or translators.

Translation strings can be used in any expression editor throughout an application using the translation! domain prefix and a reference to a specific translation string.

Workflow

Workflow objects define how your processes and automations function. Workflow object icons appear dark blue in Appian Designer.

Process ModelProcess Model

A process model is the primary tool in Appian for describing a workflow. Developers graphically lay out the workflow, which may assign user tasks, manipulate data, post system events, or update other design objects. Process models are frequently used with record types to provide users with tools to act on the information shown by the record.

Robotic TaskRobotic Task

A robotic task interacts with other applications through their front-end interfaces. Use them to automate manual, repetitive tasks on systems that don't have the right APIs. Developers can integrate robotic tasks into their Appian applications to achieve complete automation.

Learn more about Appian RPA.

Robot Pool Robot Pool

A robot pool enables you to group robots based on their unique roles and capabilities and ensure that there is always a robot available and ready to handle any robotic task execution. With several robots in each pool, each robot pool can even handle multiple executions simultaneously. When you're creating or updating a robotic task, you get to choose the appropriate robot pool responsible for executing the task.

Organization

Organization objects help you manage users, permissions, and application content.

DocumentDocument

A document is a file stored in Appian. Documents managed by record types do not appear as objects in Appian Designer.

While process reports are stored as documents, they have a unique icon and are sorted and filtered as reports.

FolderFolder

Folders allow you to organize your application content and centralize security settings. Design objects and documents can only belong to one folder at a time.

There are four types of folders: rule, process model, document, and knowledge center. For details on each type, see Folder.

You can create folders within folders for multiple levels of organization. Items in a folder (including subfolders) are listed in both the folder view and the objects grid in either the Objects view or Build view.

Security settings for the folder apply to all items within it (with the exception of process model folders). Folders created within other folders by default inherit security from their parent folder.

GroupGroup

A group allows developers to organize users, usually for the purpose of determining what permissions they have to build or use application objects and data. In addition, tasks and News entries can be targeted to one or more groups, as well as to individual users. A group can either be a custom group or use an existing group type, as well as a list of users and member groups that belong to it.

Group TypeGroup Type

A group type is used to organize groups, and can only be created by System Administrators. For example, the Region group type allows a developer to organize their sales teams by creating a different Region group for each sales team (Commercial West, Commercial East, Midwest).

Group types also define attributes that are shared across groups. For example, the group type Region might have a "regional VP" attribute. Then, each group of that group type would have a different value for the attribute, based on who that region's vice president is.

Other

These additional design objects support functionality across your applications.

Data StoreData Store

A data store is a reference to an external relational database that is used to store application data. Each data store contains one or more data entities that correspond to a table in the database. When saving data from Appian to an external database, the data store defines the connection to the database, while data types define the structure of the data entity being stored.

Process ReportProcess Report

A process report displays data from active and recently completed processes and tasks. Developers can choose to create process reports from scratch or pick from one of several dozen of out-of-the-box report templates.

Tempo ReportTempo Report

A Tempo report allows developers to display an interface on either the Reports tab (default) or the Tasks tab in Tempo.

FeedFeed

A feed is a channel for delivering content to the News Feed in Tempo or Sites. Every post or event in the News Feed that isn't directly created by a user has a feed associated with it. Generally, developers use a separate feed for each topic for which their application creates events or comments.

Feedback