How to Think About Appian Applications

Appian Max Team — Thu, 18 Apr 2024 16:07:34 GMT

Current Revision posted to Article by Appian Max Team on 4/18/2024 4:07:34 PM

Use this article to map your business needs to an Appian application before you start building individual components.

1. Data

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

Tags: Solutions Architecture, Architecture

How to Think About Appian Applications

Appian Max Team — Thu, 18 Apr 2024 16:07:12 GMT

Revision 13 posted to Article by Appian Max Team on 4/18/2024 4:07:12 PM

Use this article to map your business needs to an Appian application before you start building individual components.

1. Data

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

Tags: Solutions Architecture, Architecture

How to Think About Appian Applications

joel.larin — Thu, 02 Nov 2023 13:37:52 GMT

Revision 12 posted to Article by joel.larin on 11/2/2023 1:37:52 PM

Use this article to map your business needs to an Appian application before you start building individual components.

1. Data

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

Tags: Solutions Architecture, Architecture

How to Think About Appian Applications

matt.cosenza — Wed, 01 Nov 2023 17:33:04 GMT

Revision 11 posted to Article by matt.cosenza on 11/1/2023 5:33:04 PM

Use this article to map your business needs to an Appian application before you start building individual components.

1. Data

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

Tags: Solutions Architecture, Architecture

How to Think About Appian Applications

matt.cosenza — Wed, 01 Nov 2023 17:31:10 GMT

Revision 10 posted to Article by matt.cosenza on 11/1/2023 5:31:10 PM

Use this article to map your business needs to an Appian application before you start building individual components.

1. Data

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

Tags: Solutions Architecture, Architecture

How to Think About Appian Applications

matt.cosenza — Wed, 01 Nov 2023 17:30:35 GMT

Revision 9 posted to Article by matt.cosenza on 11/1/2023 5:30:35 PM

Use this guide to map your business needs to an Appian application before you start building individual components.

1. Data

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

How to Think About Appian Applications

joel.larin — Wed, 18 Oct 2023 14:18:30 GMT

Revision 8 posted to Article by joel.larin on 10/18/2023 2:18:30 PM

Use this guide to map your business needs to an Appian application before you start building individual components.

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

How to Think About Appian Applications

joel.larin — Wed, 18 Oct 2023 14:14:22 GMT

Revision 7 posted to Article by joel.larin on 10/18/2023 2:14:22 PM

Use this guide to map your business needs to an Appian application before you start building individual components.

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

How to Think About Appian Applications

joel.larin — Wed, 18 Oct 2023 14:02:15 GMT

Revision 6 posted to Article by joel.larin on 10/18/2023 2:02:15 PM

Use this guide to map your business needs to an Appian application before you start building individual components.

1. Data

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

How to Think About Appian Applications

joel.larin — Wed, 18 Oct 2023 13:22:04 GMT

Revision 5 posted to Article by joel.larin on 10/18/2023 1:22:04 PM

Use this guide to map your business needs to an Appian application before you start building individual components.

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

How to Think About Appian Applications

joel.larin — Wed, 18 Oct 2023 13:21:41 GMT

Revision 4 posted to Article by joel.larin on 10/18/2023 1:21:41 PM

Use this guide to map your business needs to an Appian application before you start building individual components.

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

How to Think About Appian Applications

matt.cosenza — Tue, 17 Oct 2023 19:43:09 GMT

Revision 3 posted to Article by matt.cosenza on 10/17/2023 7:43:09 PM

Use this guide to map your business needs to an Appian application before you start building individual components.

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

How to Think About Appian Applications

matt.cosenza — Tue, 17 Oct 2023 19:22:13 GMT

Revision 2 posted to Article by matt.cosenza on 10/17/2023 7:22:13 PM

Use this guide to map your business needs to an Appian application before you start building individual components.

Start with the information that's most important to you and your organization. Common examples are customers, orders, service requests, or assets.

Expose these critical objects as records to provide a single, consistent place to view this information.

Records can include data from within Appian and from external systems (relational database, web service, etc).

2. Process

Next, define your business processes. Think about how they interact with your records. If records are the nouns, processes are the verbs.

Use actions when there is no specific record involved initially (such as when creating a new record). Use related actions to act on a specific record.

Change can be initiated by users (action or related action), on a schedule, or by an external message/integration.

Use tasks to involve other people in a process. For example: a review or approval.

3. Reporting

With Appian managing your data and processes, build reports to aggregate metrics from across your organization.

4. Interfaces

Determine how users will access your application. Everything you build is shared regardless of whether they use Appian through Sites, embedded, mobile, or Tempo.

5. Platform

As you plan your applications, think about how they will interact to form a complete business platform.

How to Think About Appian Applications

joel.larin — Thu, 31 Aug 2023 19:08:11 GMT

Revision 1 posted to Article by joel.larin on 8/31/2023 7:08:11 PM

temp