Free cookie consent management tool by TermsFeed

Installing Connected Underwriting Life

This content applies solely to Connected Underwriting Life, which must be purchased separately from the Appian base platform. This content was written for Appian 23.4 and may not reflect the interfaces or functionality of other Appian versions.

Introduction

Installing the Connected Underwriting Life Workbench (CU Life) solution consists of four main steps:

  1. Download the software package.
  2. Deploy CU Life plug-ins to the Appian environment.
  3. Create the database objects in the business data source.
  4. Import the CU Life application into the Appian environment.

Before starting the installation process, review the System Requirements to ensure all minimum requirements are met.

System requirements

  • Appian version 23.4 or later for CU Life 1.1.0. Recommend using Appian HIPAA Cloud to protect and safeguard any user health data.
  • A supported version of a MariaDB database as a business data source.
    • Note: Instructions below are tailored for MariaDB databases. The SQL scripts used in Step 3 will need to be modified for use with other databases.
  • A supported web browser.

Step 1: Download software package

To install CU Life, you will need to download the software package that contains the following files you'll use in the remaining setup steps.

  • ConnectedLifeUnderwritingv1.1.0.sql: SQL script for creating the database objects needed for the Connected Underwriting Life application.
  • ConnectedLifeUnderwritingv1.1.0.zip: Application package to import into Appian.
  • ConnectedLifeUnderwritingv1.1.0-AdminConsole.zip: Admin console package to import into Appian.

To download the software package:

  1. Go to the SUPPORT tab on My Appian.
  2. Click the DOWNLOADS tab.
  3. Click SOLUTIONS.
  4. Find and open Connected Underwriting Life v23.4.1.1.0.
  5. In Downloads, click the Connected Life Underwriting Installer link.
  6. Click PROCEED to agree to the License Agreement.
  7. Click Connected Life Underwriting Installer to download the ZIP file.
  8. Unzip Connected Life Underwriting v23.4.1.1.0 to access the software installation files.

Step 2: Deploy plug-ins

You must deploy the Appian Solutions and Rich Text plug-ins for the CU Life solution to work. The steps for deploying plug-ins differ for an Appian Cloud or self-managed environment. Be sure to note which deployment steps you need for your environment.

Appian Cloud Environments

To deploy the plug-ins for an Appian Cloud environment:

  1. In the target environment, log in as the deployment user.
  2. Navigate to the Admin Console.
  3. On the left side of the console, click Plug-ins.
  4. Click ADD PLUG-INS.
  5. Search for and click Appian Solutions.
  6. Click DEPLOY.
  7. Search for and click Rich Text.
  8. Click DEPLOY.

Self-Managed Environments

To deploy the plug-ins for a self-managed environment:

Step 3: Create database objects

You will need to run a DDL script in your database to create the structure for the database tables, views, and other objects that are a part of the CU Life application.

To create the database objects:

  • In your database, run the ConnectedLifeUnderwritingv1.1.0.0.sql DDL file downloaded in Step 1.

  • Note: This DDL file is optimized for MariaDB. If you use a different database type, the DDL file may need to be modified.

Step 4: Import the application

The next step needed is installing the CU Life application by importing the application files into the target environment.

To import the application:

  1. In the target environment, log in as the deployment user.
  2. Navigate to the Appian Designer.
  3. Click IMPORT.
  4. Click UPLOAD and choose the ConnectedLifeUnderwritingv1.1.0.zip file downloaded in Step 1.
  5. Click INSPECT.
  6. Review the inspection results. If there are no issues, click IMPORT PACKAGE.
    • NOTE: The import may time out due to file size, but the import will continue in the background.

Note:  A warning will occur when importing the data stores if the business database is not called Appian. To fix this, after the import is complete, go into each record object and manually change the source table to the appropriate database schema.

Feedback