Record Type Tutorial (Web Service)

Introduction

Copy link to clipboard

Your enterprise data may be spread across a number of different systems. If your data sources provide access with a REST API, you can bring all of your data together by creating a service-backed record type, which is a record type that uses a web service as its data source.

This tutorial guides you through the steps for creating a service-backed record type that powers a fictional SpaceX Launch application that manages rocket launch data. We'll use the r/SpaceX API as the data source of our record type. To enable Appian's powerful data modeling features, we'll also enable data sync for the record type.

Most APIs require applications to send authentication credentials with each request. The r/SpaceX API is a free, public, open-source API that doesn't require authentication. This makes it ideal for this tutorial because we don't need credentials in order to connect to it. Specifically, we will use the Launches resource of the r/SpaceX API that supports paging, searching, and filtering.

Objectives

Copy link to clipboard

You'll learn how to use a web service integration to create a record type. Although this tutorial focuses more on the specifics of configuring the record type's data source and record list view, you'll also have an opportunity to create other Appian design objects required to build the record type and SpaceX Launch application.

You'll create the following design objects:

• Groups
• Folders
• Record types
• Connected systems
• Integrations
• Expression rules
• Interfaces

After you complete this tutorial, you will understand how to use your own API to create a service-backed record type. The final configurations of your record type will change based on the field names and data types of your source.

Requirements

Copy link to clipboard

To successfully complete this tutorial, you need to have basic familiarity with building applications and interfaces, as well as an understanding of REST APIs and how to use them. To gain practice designing Appian interfaces, walk through the Interface Tutorial and Process-Backed and Entity-Backed Record Tutorial.

Setup

Copy link to clipboard

Before we create the record type, we need to set up our application and user groups.

Create the application and user groups

Copy link to clipboard

Let's start by creating our SpaceX Launch application:

1. Sign in to Appian Designer.
2. Click NEW APPLICATION.

3. In the Create New Application dialog, configure the following properties:

   Property	Description
   Name	Enter SpaceX Launch.
   Prefix	Replace the default prefix with SpaceX. This prefix departs a bit from the recommended naming standard, but it's within the character limits allowed, it meets our needs for this tutorial, and it's more fun. We'll be using this short, unique prefix whenever we name an object in this application.
   Description	Enter Container for components of the SpaceX Launch application.
   Generate groups and folders to secure and organize objects	Keep this checkbox selected, so that Appian will automatically generate standard groups and folders and assign default security groups for this application.

4. Click CREATE.
5. In the Review Application Security dialog, keep the default settings for the Default (All Other Users), SpaceX Administrators, and SpaceX Users groups.

6. Click SAVE.

   Tip:  The security of the application object is unrelated to the security of each of the objects contained within the application. This means that you will need to set security permissions for every object in an application in addition to the application object itself. For more information about security permissions for the application object, see Application Security.

Now let's create and configure our new record type.

Create the record type

Copy link to clipboard

We will create and configure the record type in steps. We'll start with creating the data source objects, followed by setting up filters and configuring the integrations and expressions, and finally creating the record list view and record type's Summary view.

To begin:

1. In your application, go to the Build view.
2. Click NEW > Record Type.
3. For Name, enter SpaceX Launch. Launches will automatically populate in the Display Name (Plural) field.
4. For Description, enter Record type for the SpaceX Launch application.
5. Click CREATE.
6. In the Review Record Type Security dialog, keep the default security group settings.
7. Click SAVE. The SpaceX Launch record type will open in a new tab.

Configure the record data source

Copy link to clipboard

When the SpaceX Launch record type opens in a new tab, the Data Model page opens by default. From this page, we'll select our data source as the first step in configuring the record type.

1. On the Data Model page, click TELL US ABOUT YOUR DATA.
2. For Choose Source Type, click Web Service.
3. Click NEXT.
4. For Data Sync, choose Build Apps Faster with Sync.
5. Click NEXT.
6. For Choose Record Data Source, click Create Record Data Source to set up the connected system.

Set up the connected system

Copy link to clipboard

Now, we'll set up an HTTP connected system for the r/SpaceX API and the expression rule that calls that integration. This will allow us to use an integration to call the external data into the record type. The configuration wizard will guide us through the process of creating the Appian design objects you need to configure the record data source.

To create an HTTP connected system:

1. Keep the default option, Create a new integration, selected.
2. Next to the Connected System field, click .
3. In the Create Connected System dialog, select HTTP.

   Tip:  For more information about a specific connected system option, including a detailed description, hover over the connected system button to access the tool tip.

4. For Name, enter r/SpaceX API.
5. For Description, enter An API that returns data about SpaceX launches.
6. For System Logo, upload a system logo image.
7. For Base URL, enter https://api.spacexdata.com/v3.
8. For Authentication, keep the default None selected since this is an unauthenticated API.

9. Click CREATE. The new object is created and appears as the Connected System in the Create Record Data Source dialog.

   

Create the record data source integration

Copy link to clipboard

Now we'll create an integration that connects to the r/SpaceX API connected system and calls the external data for the record type.

1. For Name, enter SpaceX_getAllLaunches.
2. For Description, enter Integration that gets all launch data for the SpaceX Launch record type.
3. For Save In, select the SpaceX Rules & Constants folder.
4. Click NEXT.

Create the record data source expression rule

Copy link to clipboard

Next, we'll create the record data source expression.

The record data source expression connects the integration to the record type, calls the integration, and returns the requested data. After we create the integration for the record data source, the configuration wizard automatically defines the property fields for our expression rule.

In the CREATE EXPRESSION RULE step, verify that the following information is automatically populated in each field below:

• Name field - SpaceX_getAllLaunches_recordDataSource
• Description field - The Record Data Source for the SpaceX Launch Record Type
• Application field - SpaceX Launch
• Save In field (folder) - SpaceX Rules & Constants

Click NEXT to continue on to configuring syncing in batches.

Configure syncing in batches

Copy link to clipboard

In the last step of the wizard, you'll specify whether you want to sync your record data in batches.

The record data source can return a maximum of 1,000 records with each integration call, so Appian provides the option to sync larger datasets in batches. The complete set of launch data is fewer than 200 records, so we don't need to make multiple calls to retrieve everything.

To disable syncing in batches:

1. Clear the Enable Syncing in Batches checkbox.
2. Click CREATE.

Two generated objects are listed on the confirmation page: the record data source expression and the integration to get all launch data.

Before you close the Create Record Data Source wizard, we need to edit the generated objects so they return data in the correct format. If you click OK now, you will see an error on the Choose Record Data Source dialog.

Configure the integration path

Copy link to clipboard

First, we'll set the integration object's relative path.

The relative path is appended to the base URL of the connected system to form a URL exposed by the API as an endpoint. The data returned by the endpoint allows the integration to populate the record list and return a list of the objects that will map to the record type. We'll use the launches endpoint to return an array of SpaceX launches. The rule inputs for this integration will be passed into the corresponding expression rule for the record data source.

1. On the Create Record Data Source dialog, click the SpaceX_getAllLaunches integration object to open it.

2. For Relative Path, enter /launches. This will be appended to the Base URL of the connected system to form a URL of https://api.spacexdata.com/v3/launches.

   

3. Click TEST REQUEST. This should return a success message:

   

4. Under the success message, click Convert JSON to Appian value to convert this response body to an Appian dictionary.
5. Click TEST REQUEST again to ensure the test results successfully converted from JSON to the Appian format.
6. Expand the Query Parameters section of the integration.
7. Click Add Query Parameter.
8. For Name, enter limit.
9. For Value, enter 100.
10. Click TEST REQUEST again and verify that the result.body contains 100 items.
11. Click SAVE CHANGES and close the integration tab.

Configure the record data source expression

Copy link to clipboard

By default, the integration's response includes a result.body that is a generic List of Dictionary with many properties describing each launch. Because we only need a few of the returned data points for our application, we will map the needed data to fields that will make up the record type.

Let's update the Record Data Source expression with these changes:

1. On the Create Record Data Source dialog, click the SpaceX_getAllLaunches_recordDataSource expression rule.
2. On line 11, replace the default value of local!integrationResponse.result.body with the following expression:

   1
   2
   3
   4
   5
   6
   7
   8
   9
   10
   11
   a!forEach(local!integrationResponse.result.body,
     a!map(
       flight_number: fv!item.flight_number,
       details: fv!item.details,
       launch_date_utc: fv!item.launch_date_utc,
       launch_success: fv!item.launch_success,
       launch_year: fv!item.launch_year,
       mission_name: fv!item.mission_name,
       rocket_name: fv!item.rocket.rocket_name
     )
   ), 
   Copy

3. Click TEST RULE. The output should be a 100 Lists of Map, each with the fields set in the a!map() of the expression.
4. Click SAVE CHANGES and close the expression rule tab.
5. On the Create Record Data Source dialog, click OK.

Verify data in the preview

Copy link to clipboard

Once you've configured the integration, you can confirm that the record data source expression is working by examining the data preview shown on the Configure Data Source dialog. After you've verified the preview data, click Next.

Configure record type fields

Copy link to clipboard

Appian automatically maps your source data fields to record fields and then lets you pick a primary key field and order the fields as you want.

To select and configure the record type fields:

1. For Primary Key, select flight_number.

2. Click FINISH.

   

3. In the record type, click SAVE CHANGES.

Saving the record type starts a full sync of your record data. Click Sync History to see details of the sync operation and confirm that it completed successfully.

Configure query parameters for an integration

Copy link to clipboard

Next, we'll copy the data source integration and modify the copy to enable searching and filtering with query parameters. Specifically, we'll set up offset, limit, sort, and order query parameters to enable searching, filtering, and paging.

Paging is often the most complicated parameter to configure. This is because REST APIs don't understand Appian's PagingInfo data type, and different APIs handle paging in different ways. See the r/SpaceX API documentation for details on its pagination parameters.

We'll also configure the rocket_name, launch_year, and launch_success parameters to enable filtering by rocket, the launch year, and whether the launch was successful. All of these query parameters have dynamic values and should be configured as expressions. We will populate their values using rule inputs.

Let's begin:

1. From the Build view, select the checkbox next to the SpaceX_getAllLaunches integration.
2. Click DUPLICATE.
3. For Name, enter SpaceX_getFilteredLaunches.
4. For Description, enter Integration that gets user-specified launch data for the SpaceX Launch record type.
5. Click CREATE.
6. In the RULE INPUTS pane, click New Rule Input and add the following rule inputs:
   • pagingInfo with the type PagingInfo.
   • searchText with the type Text.
   • launchYear with the type Number (Decimal).
   • launchSuccess with the type Boolean.
7. For the limit query parameter, use the expression editor to enter ri!pagingInfo.batchSize as the parameter value.
8. Click Add Query Parameter to configure each query parameter and value listed below. Make sure to click the icon next to each query Value field to configure each Query Parameter value as an expression.
   • Add the offset parameter and use the expression editor to enter ri!pagingInfo.startIndex - 1 as the parameter value.
   • Add the sort parameter and use the expression editor to enter index(ri!pagingInfo.sort, "field", null) as the parameter value.
   • Add the order parameter and use the expression editor to enter if(index(ri!pagingInfo.sort, "ascending", null), "asc", "desc") as the parameter value.
   • Add the rocket_name parameter to enable searching by name and use the expression editor to enter ri!searchText as the parameter value.
   • Add the launch_year parameter to enable filtering by launch year and use the expression editor to enter ri!launchYear as the parameter value.

   • Add the launch_success parameter to enable filtering by launch success and use the expression editor to enter ri!launchSuccess as the parameter value.

     

9. Click TEST REQUEST. The response should include all available launch data.
10. To test the paging query parameters, add the following expression as the test value of the pagingInfo rule input.

    1
    2
    3
    4
    5
    6
    7
    8
    a!pagingInfo(
      batchSize: 10,
      startIndex: 12,
      sort: a!sortInfo(
        field: "flight_number",
        ascending: false
      )
    )
    Copy

11. Click TEST REQUEST. The response should include 10 launches starting with flight number 100 and ending with flight number 91.
12. To test the other query parameters, remove the pagingInfo test value and then update the test values with the following:
    • For searchText, enter "Falcon 1".
    • For launchYear, enter 2008.
    • For launchSuccess, select True.
13. Click TEST REQUEST. The response should include one launch: flight number 4 with the mission name "RatSat".
14. Click SAVE CHANGES.
15. Close the integration object.

Build a record data source expression rule with filtering

Copy link to clipboard

The record data source expression calls the SpaceX_getAllLaunches integration to populate the record type with data. Since we enabled the filtering and sorting on the SpaceX_getFilteredLaunches integration, we need to create an expression rule with matching rule inputs and pass the rule input values as parameters to the integration.

We'll build an expression rule for the data source that will let users search for specific data. This expression rule will return the integration response data for the record list view. The rule inputs for this expression rule are taken from the filtered data source's integration rule inputs.

We've made this process easy for you by providing a SAIL template in the expression rule object. To build the expression rule, follow the instructions and comments provided in the template along with the steps below. Note that some sections of the SAIL code are preconfigured for you. As you go through each step in the template, verify that the preconfigured code matches the configurations defined in the steps below.

Let's begin:

1. From the Build view, select the checkbox next to the SpaceX_getAllLaunches_recordDataSource expression rule.
2. Click DUPLICATE.
3. For Name, enter SpaceX_getFilteredLaunches_recordDataSource.
4. For Description, enter Filtered Data Source for the SpaceX_Rocket Record Type.
5. Click CREATE. The expression rule will open in a new tab.
6. In the RULE INPUTS pane, click New Rule Input and add the following rule inputs:
   • pagingInfo with the type PagingInfo.
   • searchText with the type Text.
   • launchYear with the type Number (Decimal).
   • launchSuccess with the type Boolean. The expression rule is preconfigured to call the integration, but we need to add the rule inputs using keyword syntax.
7. Change the initial value of local!integrationResponse to rule!SpaceX_getFilteredLaunches().
8. In rule!SpaceX_getFilteredLaunches, add the following parameters:
   • Set the pagingInfo parameter value to ri!pagingInfo.
   • Set the searchText parameter value to ri!searchText.
   • Set the launchYear parameter value to ri!launchYear.
   • Set the launchSuccess parameter value to ri!launchSuccess.
9. Now, test the expression rule to ensure that it correctly calls the integration and returns the data for a start index of 12 and a batch size of 5 as expected.
   • From the Ad Hoc Test view, enter a!pagingInfo(12,5) in the expression value field for the pagingInfo rule input.

   • Click TEST RULE. The test output should be five Maps starting with flight number 100 and descending to flight number 96.

     

     

10. Click SAVE CHANGES.
11. Check your code with the expression below.

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    a!localVariables(
      /* Call the integration and store the response in a local variable */
      local!integrationResponse: rule!SpaceX_getFilteredLaunches(
        pagingInfo: ri!pagingInfo,
        searchText: ri!searchText,
        launchYear: ri!launchYear,
        launchSuccess: ri!launchSuccess
      ),
      if(
        /* This will return true if the integration succeeds */
        local!integrationResponse.success,
        /* If needed, modify the expression below to return a list of maps, dictionaries, or CDTs that map to your record data */
        a!forEach(
          local!integrationResponse.result.body,
          a!map(
            details: fv!item.details,
            flight_number: fv!item.flight_number,
            launch_date_utc: fv!item.launch_date_utc,
            launch_success: fv!item.launch_success,
            launch_year: fv!item.launch_year,
            mission_name: fv!item.mission_name,
            rocket_name: fv!item.rocket.rocket_name
          )
        ),
        /* If the integration is unsuccessful, handle accordingly */
        if(
          /* Note: handling of out of bounds exceptions varies by web service */
          tointeger(
            index(
              local!integrationResponse.result,
              "statusCode",
              0
            )
          ) = 416,
          /* If this is an out of bounds error, return an empty list to finish syncing */
          {},
          /* If this is a different error, return the integration error. */
          /* If you need additional logic to determine the error, use a!integrationError() in the integration to format the error displayed in the sync monitor */
          local!integrationResponse.error
        )
      )
    )
    Copy

    Now that we've configured the data sources, let's verify that the data returned for your data source expression matches the fields in our data type.

Sync and preview record type data

Copy link to clipboard

Once you save the record type, a full sync occurs to sync your data in Appian. When the sync is successful, that means that your Record Data Source expression is working correctly.

Now you can see a preview of your synced data by going to the Data Preview tab on the Data Model page.

Let's verify that the data results returned for our record data source expression matches the data we expect for the record type.

1. Go back to the SpaceX Launch record type.
2. Go to Sync Options.
3. Click Start Sync. A success message should appear with the date and time of the sync.
4. Go to Data Model.

5. Click the Data Preview tab.

   

   

Configure the list view

Copy link to clipboard

Now let's populate our record list with more meaningful data.

1. In the record type, go to List.
2. Leave the default Style option as Grid.
3. Click Edit List to open the Edit Record List dialog.
4. For Empty Grid Message, enter No launches exist with this criteria..
5. For Rows to Display Per Page, enter 5. This controls the batchSize that is passed into the Paging Info input for your single record source.
6. In the Columns section of the configuration pane, delete the Details column by hovering over the three dots and clicking the X.
7. Delete the following columns in the same way:
   • Launch Date Utc
   • Launch Success
   • Rocket Name
8. Move the Mission Name column to the top of the list by hovering over the three dots and clicking the Move Up arrow.
9. Click the Mission Name link. The grid configuration pane will show details about that column.
10. Click DISPLAY OPTIONS.
11. From the list of options, click RECORD LINK.
12. For Display Value, click Edit as Expression.
13. Set the Display Value using the following expression:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    a!linkField(
      links: {
        a!recordLink(
          label: fv!row[recordType!SpaceX Launch.fields.mission_name],
          recordType: recordType!SpaceX Launch,
          identifier: fv!identifier
        )
      }
    ) 
    Copy

14. Click OK to save all changes and return to the record type.
15. Click SAVE CHANGES.

16. To test your record list configuration, click the link under URL.

    You should end up with a list view that looks like this:

    

Create a user filter

Copy link to clipboard

To make it easier for users to find information about specific launches, we can build user filters that compare user selections with the values of record fields and return the records that match. In this case, we'll create an expression-backed user filter that uses the launch_year field to see data for a selected calendar year.

To create a user filter:

1. In the record type, go to Filters.
2. Click New User Filter.
3. On the Create New User Filter dialog, select the Expression option.
4. For Name, enter Launch year.
5. For the Filter Expression, paste the following expression:

   1
   2
   3
   4
   5
   6
   7
   8
   9
   10
   11
   12
   13
   14
   15
   16
   17
   18
   19
   20
   21
   22
   23
   24
   25
   26
   27
   28
   29
   30
   31
   a!localVariables(
     local!year: a!queryRecordType(
      recordType: recordType!SpaceX Launch,
      fields: a!aggregationFields(
        groupings: a!grouping(
          field: recordType!SpaceX Launch.fields.launch_year,
          alias: "year"
        )
      ),
      pagingInfo: a!pagingInfo(
        startIndex: 1,
        batchSize: 100
      )
     ),
     a!recordFilterList(
       name: "Launch year",
       allowMultipleSelections: true,
       options: a!forEach(
         items: local!year.data,
         expression: a!recordFilterListOption(
           id: fv!index,
           name: fv!item.year,
           filter: a!queryFilter(
             field: recordType!SpaceX Launch.fields.launch_year,
             operator: "=",
             value: fv!item.year
           )
         )
       )
     )
   )
   Copy

6. Click OK.
7. Click SAVE CHANGES.
8. To test your filter configuration:
   • In the record type, go to List.
   • Click the URL to open the record list.

   • Select 2015 from the LAUNCH YEAR dropdown and verify that the grid shows only the seven launches from 2015.

     

Create the Summary view

Copy link to clipboard

The last step of this tutorial is to create the Summary view, a task made easier by using the record view generator. Structurally, a Summary view for a service-backed record type is no different from a Summary view for any other record type. What may be different, however, is how you acquire the data.

1. In the record type, go to Views.
2. Click GENERATE RECORD VIEW.
3. For Data Included in Your Record View, the Launch record type is already selected, so you can click NEXT.
4. For View Name, use the default name Summary and then click NEXT.
5. On the review page, you can see the new interface that will be generated (SpaceX_Launch_Summary). When you are ready to proceed, click GENERATE VIEW.
6. Once the view is generated, click CLOSE.
7. Click SAVE CHANGES.

Update the generated Summary view

Copy link to clipboard

Next, we'll customize our new Summary view with meaningful labels displayed on each record.

1. Open the SpaceX_Launch_Summary interface.
2. Copy the expression below and paste it into the interface in expression mode.

   1
   2
   3
   4
   5
   6
   7
   8
   9
   10
   11
   12
   13
   14
   15
   16
   17
   18
   19
   20
   21
   22
   23
   24
   25
   26
   27
   28
   29
   30
   31
   32
   33
   34
   35
   36
   37
   38
   39
   40
   41
   42
   43
   44
   45
   46
   47
   48
   49
   50
   51
   52
   53
   54
   55
   a!boxLayout(
     label: "Flight #" & ri!record[recordType!SpaceX Launch.fields.flight_number] & " Launch Info",
     contents: {
       a!sideBySideLayout(
         items: {
           a!sideBySideItem(
             item: a!textField(
               label: "Date",
               labelPosition: "ADJACENT",
               value: ri!record[recordType!SpaceX Launch.fields.launch_date_utc],
               readOnly: true
             )
           ),
           a!sideBySideItem(
             item: a!textField(
               label: "Name",
               labelPosition: "ADJACENT",
               value: ri!record[recordType!SpaceX Launch.fields.rocket_name],
               readOnly: true
             )
           ),
           a!sideBySideItem(
             item: a!richTextDisplayField(
               label: "Success",
               labelPosition: "ADJACENT",
               value: a!richTextIcon(
                 icon: if(
                   ri!record[recordType!SpaceX Launch.fields.launch_success],
                   "check-circle",
                   "times-circle"
                 ),
                 color: if(
                   ri!record[recordType!SpaceX Launch.fields.launch_success],
                   "POSITIVE",
                   "NEGATIVE"
                 )
               )
             )
           )
         }
       ),
       a!textField(
         label: "Details",
         labelPosition: "ADJACENT",
         value: ri!record[recordType!SpaceX Launch.fields.details],
         showWhen: not(
           isnull(
             ri!record[recordType!SpaceX Launch.fields.details]
           )
         ),
         readOnly: true
       )
     },
     iscollapsible: true
   )
   Copy

3. Click SAVE CHANGES.

Configure the record title

Copy link to clipboard

The last step is to configure the record's title.

1. In the record type, go to Views.
2. In the Header section, use the default Record Title option of Guided Configuration.
3. For Record Title, clear the default selection and choose mission_name from the dropdown.
4. Click SAVE CHANGES.
5. To test the Summary view:
   • In the record type, go to List.
   • Click the URL to open the record list.
   • Click a mission name to display the record's Summary view.

Congratulations! You've configured your own service-backed record type. Check out the Database-Backed Record Type Tutorial to learn how to configure a database-backed record type.

Feedback

Copy link to clipboard