This lesson from the Introduction to Applications course walks you through the basic steps of creating a new application.
This page explains what an application is, and the two ways to create an Appian application:
When using the Application Builders, Designers will have two options for application: Basic and Full.
For specific information about working in the Appian Designer space, see Applications.
Applications are essentially a collection of objects that make up a business solution or function. We recommend creating a dedicated application for every business solution. For instance, Customer Relationship Management (CRM) and Sales Opportunities would be different applications.
In addition to creating applications to serve business functions, you should also create an application for each collection of objects that you intend to reuse across applications, such as a Common Objects application that contains utility rules, icons, and templates.
Each of these application types could apply to the same project. If your first business solution was Customer Relationship Management, then your apps list might look as follows when you were done developing it:
When updating an existing solution, use a patch.
Creating an application from scratch only requires a name, though a description is recommended. Creating an application immediately navigates you into the details view for that app. New applications created from scratch are unpublished by default and contain no objects.
An application is, in itself, an object whose functionality affects what is seen in Tempo (sites or embedded interface users are not affected). Exposed application functionality is found on the Actions tab of Tempo. This section covers the steps necessary to expose application functionality to Tempo if you are creating an application from scratch.
Application actions can be created: manually from the application properties menu, saved as an application action via an interface, and through the application builder. In this page, we will only discuss creating an Action and publishing it from scratch.
To learn more about creating applications in general, check out the Application Building Tutorial.
As long as our application contains an ‘actionable’ process model we can create an action. By actionable, we need the process model to contain a start form, user input task, or some other attended node that will allow a user to interact with the model. This is a logical limitation rather than a functional one… we want actions that allow the user to interact with that process.
When we create actions and publish applications from scratch, we are using the application’s properties to manually define our actions.
Applications actions need names, descriptions, and process models to start. While these applications can be created in any order, they will be ordered alphabetically in Tempo.
Application can be in a published or unpublished state. This feature lets administrators expose or hide application actions from users in Tempo.
When published its application icon in Appian Designer will appear red. A published application will appear as a filter on the Actions tab of Tempo.
Whichever method is used to create and publish an application, security should still be considered. In order for users to see the application and application actions they will need at least View access to the application and process model.
The Application Builder is a feature of Appian Designer that creates an application with pre-defined set of objects. There are two different types: basic and full. Both sets of templates use the same paradigm to create applications, just with a different level of functionality.
A basic template from the application builder creates only the objects necessary to create, view, update, and delete the records in your app.
This template is especially useful if you want to jump start a brand new application. Instead of creating the base objects from scratch, this template will give you a basic application in a few minutes.
A full template has all of the record functionality of a basic application, and also includes functionality for: audit history, collaboration, document management, task assignment, and reporting.
This template is useful if you had planned to implement this functionality in your application anyway; otherwise, a basic application will likely be simpler to enhance and build out.
After the template type and datasource is selected from the Create New Application dialog, the Application Builder will launch. The Application Builder is a four step wizard that will guide designers through the application creation process. Depending on whether a basic or full application was selected, the defaults within the Application Builder will change.
On the first page, users name and describe their application.
Each app stores data in the form of Records in Tempo. We collect the singular and plural name not just because the record type requires them, but also so that we can name and describe other parts of the application in sensible ways. For example, an empty grid in Tempo would say that there are "No (plural entry name) available."
We use the first letter of each word in the application name to generate a prefix for the design objects in the application. For example, a rule in the Support Ticket Management application might be called "STM_GetSupportTicketById". This prefix is guaranteed to be unique among all Quick Apps and generated apps on the system.
On this page, users specify the fields of information they want to capture for each record. This serves as both data and interface design for the app, and provides the core of its unique design.
Users can create fields of the following types:
Users can add the following configurations to fields.
Configurations display on forms, but not on the record dashboard.
When using the full template, three fields are pre-populated: Title, Status, and Priority. Of these, only Title is required (however, the name can be changed). When using the basic template, only the Title field is pre-populated.
A Preview Form option is available on this page. It shows how the currently configured values will manifest in the Action and Records of the completed application. Specifically, it offers a preview of the start form of the Action, and the Summary view of the record type. Users can use this to help design their application to look exactly as they want it to, without having to create it first and then update it to make changes.
Each field added on this page results in a new field on the main CDT of the application, with the following details:
On this page, users specify the people who should use the application. Additionally, for full template applications, designers can choose whether to make this a site-based application (default) or exposed through Tempo.
Collaborators have access to all application functionality.
The people selected at this step are added as members of a group, which is created to secure application activity to.
The application builder, will default for the full template to a sites-based application.
When you click Create Application on this page, your application will be created! Please allow up to a minute for generation of the application.
Once your application has been generated, the final page of the form will load. Links to your new functionality will appear.
Each application is published immediately, and provides record-centric functionality to its users. Creating, viewing, modifying, and collaborating around the data in your records makes up the bulk of work enabled by the application's design. Details on each section of functionality are below.
Each application adds a single Action to the Actions tab, which allows users in the Collaborators group to create new records. This start form will match the preview available while creating the application.
Each application has a record type that is the central hub for work done in the app.
Records for basic and full template applications will include:
For full templates only, each record will also contain:
For targeted alerts and requests, tasks can be sent from the record to any user on the system through a related action on the Summary view.
A report is generated for each application, containing four charts and a records grid.
The News tab is used to post messages to users of an application.
A site can be created using a full template.
For pages will be added to the site: