Day 7: ¿Que entendiste de: Process Modeling 101: Automate Your Business Processes?

Day 7: ¿Que entendiste de: Process Modeling 101: Automate Your Business Processes?

  Discussion posts and replies are publicly visible

Parents
  • DIA 6

    Lesson Objectives

    After you complete this lesson, you'll be able to:

     

    • Create a site
    • Configure a page
    • Define page capabilities
    • Identify what branding elements can be managed
    • Discuss best practices when customizing site branding

     When you assign a display name to a new site, consider the following guidelines.

    • Do not start the display name with the application prefix, because end users will see the entire display name.
    • Use a short name that is meaningful to your end users.
    • Use title case.
    • Appian uses the display name to construct a default web address identifier for the site. To refine the site URL, edit the default web address identifier.
    • The display name can duplicate another object name in the Appian environment, but the web address identifier must be unique.

     

     

     

     

     

     

    Watch: Customize Site Branding!!!!!!!!!!!

     

     

     

    Lesson Objectives

    After you complete this lesson, you'll be able to:

     

    • Describe how to ensure a user is able to view the site
    • Discuss how a user’s access can be controlled across pages

     

     

     

     

     

     

     

     

    Lesson Objectives

    After you complete this lesson, you’ll be able to:

     

     

    • Explain what a portal is, and recall common use cases
    • Describe the high-level steps for designing a portal

     

     

    Common Use Cases

     

    In its simplest form, a portal is one or more interfaces created in Appian and published at a public URL, but it can also include a number of additional design objects. For example, if you want a user to fill out a form, and then launch an Appian process, you'll build an interface and a process model, along with any other necessary objects. 

     

    Interfaces added as pages in a portal can't use rule inputs, so you'll use local variables instead. 

     

    Configure Permissions

    Portals are publicly accessible, but that doesn't mean they aren't secure.

    To control access to your Appian environment, you'll create a service account. A service account acts on behalf of portal users, providing the portal with permissions to connect to selected information and processes in Appian. 

    You can create the service account directly from within the portal object, but then you'll need to add this account as a user to your app’s All Users group (or any other group that you want to use for your portal’s security).

     

    After you implement all configurations, it's time to publish, test your published portal, and prepare for deployment. Keep a few details in mind:

    • You only need to publish the portal once. Appian will automatically republish the portal upon deployment, or if you update the portal object or its precedents. 
    • For a portal to auto-publish in a new environment, set up a service account with the same name as the service account in your source environment.
    • To test, navigate to the published portal and use it the way the end user would.
    • To deploy a portal to another environment, add it and all precedents to the deployment package.

     

    Before creating a portal form you could need:  

     

    • Interface
    • Process

    OJO el usuario genérico se crea en otro lado!!!

     

     

    Display Data with a!queryRecordType

    If your app uses record types and you want your portal to display data from Appian, configure the underlying interface using the a!queryRecordType function. This is what our developer did in the interface for the Acme Automobile’s Auditor Validation Portal. She added a local variable - local!maintenanceData - and then used the a!queryRecordType function to query the Maintenance record type. 

     

    Tip: You can review this example in the Appian Community Edition environment. Request your instance, and navigate to the Acme Automobile Reference Application. Review the interface used in this app's portal (AA_PRTL_DSH_AuditorDashboard).  

     

Reply
  • DIA 6

    Lesson Objectives

    After you complete this lesson, you'll be able to:

     

    • Create a site
    • Configure a page
    • Define page capabilities
    • Identify what branding elements can be managed
    • Discuss best practices when customizing site branding

     When you assign a display name to a new site, consider the following guidelines.

    • Do not start the display name with the application prefix, because end users will see the entire display name.
    • Use a short name that is meaningful to your end users.
    • Use title case.
    • Appian uses the display name to construct a default web address identifier for the site. To refine the site URL, edit the default web address identifier.
    • The display name can duplicate another object name in the Appian environment, but the web address identifier must be unique.

     

     

     

     

     

     

    Watch: Customize Site Branding!!!!!!!!!!!

     

     

     

    Lesson Objectives

    After you complete this lesson, you'll be able to:

     

    • Describe how to ensure a user is able to view the site
    • Discuss how a user’s access can be controlled across pages

     

     

     

     

     

     

     

     

    Lesson Objectives

    After you complete this lesson, you’ll be able to:

     

     

    • Explain what a portal is, and recall common use cases
    • Describe the high-level steps for designing a portal

     

     

    Common Use Cases

     

    In its simplest form, a portal is one or more interfaces created in Appian and published at a public URL, but it can also include a number of additional design objects. For example, if you want a user to fill out a form, and then launch an Appian process, you'll build an interface and a process model, along with any other necessary objects. 

     

    Interfaces added as pages in a portal can't use rule inputs, so you'll use local variables instead. 

     

    Configure Permissions

    Portals are publicly accessible, but that doesn't mean they aren't secure.

    To control access to your Appian environment, you'll create a service account. A service account acts on behalf of portal users, providing the portal with permissions to connect to selected information and processes in Appian. 

    You can create the service account directly from within the portal object, but then you'll need to add this account as a user to your app’s All Users group (or any other group that you want to use for your portal’s security).

     

    After you implement all configurations, it's time to publish, test your published portal, and prepare for deployment. Keep a few details in mind:

    • You only need to publish the portal once. Appian will automatically republish the portal upon deployment, or if you update the portal object or its precedents. 
    • For a portal to auto-publish in a new environment, set up a service account with the same name as the service account in your source environment.
    • To test, navigate to the published portal and use it the way the end user would.
    • To deploy a portal to another environment, add it and all precedents to the deployment package.

     

    Before creating a portal form you could need:  

     

    • Interface
    • Process

    OJO el usuario genérico se crea en otro lado!!!

     

     

    Display Data with a!queryRecordType

    If your app uses record types and you want your portal to display data from Appian, configure the underlying interface using the a!queryRecordType function. This is what our developer did in the interface for the Acme Automobile’s Auditor Validation Portal. She added a local variable - local!maintenanceData - and then used the a!queryRecordType function to query the Maintenance record type. 

     

    Tip: You can review this example in the Appian Community Edition environment. Request your instance, and navigate to the Acme Automobile Reference Application. Review the interface used in this app's portal (AA_PRTL_DSH_AuditorDashboard).  

     

Children
No Data