Day 4 Design Appian Records Part 1 y Part 2 que aprendiste?

¿Day 4 Design Appian Records Part 1 y Part 2 que aprendiste?

  Discussion posts and replies are publicly visible

Parents
  • Lesson Summary

    In this lesson, you learned how to create a new record type object sourced from an existing database and how to generate a database table from within the record type object. You also learned how to enable data sync on a record type so the vehicle data is cached in Appian, and how to configure Appian to skip a failed sync and to use data from the last successful sync instead. Next, you learned how to initially configure the fields you would like to include in the record type. Finally, you learned about the data model overview screen that shows you the current data structure of your record as well as related record types. 

     

     

     

     

    Query a Record Type

    Learning Objectives

    After completing this lesson, you should be able to:

    • Explain how queried record data can be used in your application
    • Query a record type using the Query Editor

     

     

    a!queryRecordType( )

    Before we walk through how to return a single row of data, let’s briefly discuss how else you might use queries in your applications. First, you may be familiar with the function a!queryEntity(). This function queries your database and returns the requested data. In this lesson you will learn about a similar function called a!queryRecordType( ). Instead of querying a database, it looks up and returns data from your record type object. 

    You can use this function to return:

     

    • a list of values for a single record field 
    • a list of records with a subset of the fields
    • aggregate data
    • a single row of data

     

    Query a Record Type

    In this lesson, you will learn how to generate an expression using the query editor. That expression will query the vehicle record type and return a row of data.

    You’ll see this query used for testing, but record data can be used in any interface within an app. Note that this work is being done in the expression rule object and not in the record type.

     

    Lesson Summary

    In this lesson, you learned how to create a new expression rule to pass in a record id and have that expression query the record data to retrieve a single row of data. 

     

    Configure the Record List

    Learning Objectives

    After completing this lesson, you should be able to:

    • Configure a record list
    • Identify additional objects where record data can be displayed

     

    Apply Filters

    Learning Objectives

    After completing this lesson, you should be able to:

    • Apply source filters to your record
    • Apply default filters to your record list
    • Apply user filters to your record list

     

     

    • Lesson Summary
    • In this lesson, you learned how default filters determine which records appear in the record list and views, based on the conditions you specify. Then you learned how to create interactive filters so users can determine which records appear in their record list or grids that use record data. You learned the difference between static and expression-based filters. You also learned how users can save filters and use the search field in a record list. 

    Create Record Views

    Learning Objectives

    After completing this lesson, you should be able to:

    • Define the purpose of a record view
    • Create a record summary view
    • Create and link an interface used to display a record view

     

    Record Actions

    After completing this lesson, you should be able to:

     

    • Contrast a record action and related action
    • Generate a record list action
    • Create a related action

     

    This lesson is all about record actions. There are two types: record list actions and related actions. In this lesson, we’ll go over the differences between the two and have Appian generate each.

    RECORD LIST ACTION

    A record list action is a link to a process model that a user can start directly from the record list. The most common type of action to configure here is for users to create a new record for that record type. For example, we’re going to configure a record list action to add a new vehicle.

    RELATED ACTION

    A related action is also a link to a process model. This differs from a record list action because these process models are started directly from a record view and use data from that record.

     

     

     

     

     

     


     

    Apply Security

    Learning Objectives

    After completing this lesson, you should be able to:

    • Apply security to record type objects, record actions, and records

     

     

    Create Security Rules

    You can create security rules for different users in your application. You will learn how to set up these rules based on 

    • who is part of the rule? 
    • which records they can see?

     

    Note that users must have at least Initiator permissions to the action's underlying process model.

Reply
  • Lesson Summary

    In this lesson, you learned how to create a new record type object sourced from an existing database and how to generate a database table from within the record type object. You also learned how to enable data sync on a record type so the vehicle data is cached in Appian, and how to configure Appian to skip a failed sync and to use data from the last successful sync instead. Next, you learned how to initially configure the fields you would like to include in the record type. Finally, you learned about the data model overview screen that shows you the current data structure of your record as well as related record types. 

     

     

     

     

    Query a Record Type

    Learning Objectives

    After completing this lesson, you should be able to:

    • Explain how queried record data can be used in your application
    • Query a record type using the Query Editor

     

     

    a!queryRecordType( )

    Before we walk through how to return a single row of data, let’s briefly discuss how else you might use queries in your applications. First, you may be familiar with the function a!queryEntity(). This function queries your database and returns the requested data. In this lesson you will learn about a similar function called a!queryRecordType( ). Instead of querying a database, it looks up and returns data from your record type object. 

    You can use this function to return:

     

    • a list of values for a single record field 
    • a list of records with a subset of the fields
    • aggregate data
    • a single row of data

     

    Query a Record Type

    In this lesson, you will learn how to generate an expression using the query editor. That expression will query the vehicle record type and return a row of data.

    You’ll see this query used for testing, but record data can be used in any interface within an app. Note that this work is being done in the expression rule object and not in the record type.

     

    Lesson Summary

    In this lesson, you learned how to create a new expression rule to pass in a record id and have that expression query the record data to retrieve a single row of data. 

     

    Configure the Record List

    Learning Objectives

    After completing this lesson, you should be able to:

    • Configure a record list
    • Identify additional objects where record data can be displayed

     

    Apply Filters

    Learning Objectives

    After completing this lesson, you should be able to:

    • Apply source filters to your record
    • Apply default filters to your record list
    • Apply user filters to your record list

     

     

    • Lesson Summary
    • In this lesson, you learned how default filters determine which records appear in the record list and views, based on the conditions you specify. Then you learned how to create interactive filters so users can determine which records appear in their record list or grids that use record data. You learned the difference between static and expression-based filters. You also learned how users can save filters and use the search field in a record list. 

    Create Record Views

    Learning Objectives

    After completing this lesson, you should be able to:

    • Define the purpose of a record view
    • Create a record summary view
    • Create and link an interface used to display a record view

     

    Record Actions

    After completing this lesson, you should be able to:

     

    • Contrast a record action and related action
    • Generate a record list action
    • Create a related action

     

    This lesson is all about record actions. There are two types: record list actions and related actions. In this lesson, we’ll go over the differences between the two and have Appian generate each.

    RECORD LIST ACTION

    A record list action is a link to a process model that a user can start directly from the record list. The most common type of action to configure here is for users to create a new record for that record type. For example, we’re going to configure a record list action to add a new vehicle.

    RELATED ACTION

    A related action is also a link to a process model. This differs from a record list action because these process models are started directly from a record view and use data from that record.

     

     

     

     

     

     


     

    Apply Security

    Learning Objectives

    After completing this lesson, you should be able to:

    • Apply security to record type objects, record actions, and records

     

     

    Create Security Rules

    You can create security rules for different users in your application. You will learn how to set up these rules based on 

    • who is part of the rule? 
    • which records they can see?

     

    Note that users must have at least Initiator permissions to the action's underlying process model.

Children
No Data