Free cookie consent management tool by TermsFeed

Setting up Connected Claims

This content applies solely to Connected Claims, which must be purchased separately from the Appian base platform.

Introduction

After installing Connected Claims, there are several configurations you will likely perform to customize the solution for your organization's processes. To ensure your solution remains flexible and aligns with best practices, we have provided instructions to guide you through some common configurations.

This page outlines the order we recommend for configuring the default solution to work for your organization after installation. However, these instructions can be used to modify the solution at any time.

Note:  Updates in Appian Designer should be done cautiously by someone familiar with Appian development.

Step 1: Create a service account

Before you begin, verify you have installed all the required plugins and components.

  1. In the Admin Console, click the Users page from the Authentication section in the left-hand pane.
  2. Click Create.
  3. Give this new service account a username and then click Create.
  4. Keep the service account credentials backed up. You might not be able to view them again.

Step 2: Verify and publish data stores

Ensure all data stores are verified and published for use.

Step 3: Configure the rule object

To ensure that the rule object ICM_returnGlobalConfigValueByKey is correctly configured to use the Connected Claims AI skills, you must change the comments on some keys.

To configure the rule object:

  1. In the rule object ICM_returnGlobalConfigValueByKey, locate the following keys marked with curly braces {}.

    • Key: FNOL_Read_Claim_Document_AutoMobile
    • Key: FNOL_Read_Claim_Document_WC
    • Key: FNOL_Read_Claim_Document_Death
    • Key: FNOL_Read_Claim_Document_STD

  2. For each key, switch the comments: remove the comment from the line after the key and comment out the line with the curly braces.

Example

Here is an example of how the code should look after you switch the comments for each key.

/FNOL_Read_Claim_Document_AutoMobile: {},/
FNOL_Read_Claim_Document_AutoMobile: cons!ICM_FNOL_CLAIM_DOC_IDP_AUTOMOBILE_PM,
/FNOL_Read_Claim_Document_WC: {},/
FNOL_Read_Claim_Document_WC: cons!ICM_FNOL_CLAIM_DOC_IDP_WC_PM,
/FNOL_Read_Claim_Document_Death: {},/
FNOL_Read_Claim_Document_Death: cons!ICM_FNOL_CLAIM_DOC_AI_DEATH_PM,
/FNOL_Read_Claim_Document_STD: {},/
FNOL_Read_Claim_Document_STD: cons!ICM_FNOL_CLAIM_DOC_AI_STD_PM,

Step 4: Extract the demo driver and run scripts

To set up the environment for logging claims and demoing the application, begin by extracting the contents of Connected Claims_2.0 - Demo Driver.zip. Inside, you will find two folders:

  1. Customers, Policies & Configurations Data Loader - Contains SQL scripts that initialize your environment with the necessary configurations, customer information, and policy data.
  2. Process Mining Data Loader - Includes SQL scripts tailored for setting up process mining functionalities.

Follow the detailed instructions provided within each folder to properly run these scripts and configure your system.

Step 5: Set up and adjust application objects

Ensure all objects are correctly aligned with the target environment by verifying or updating each object. There are two approaches for this:

  1. Direct Modification: Directly change the values to match your target environment specifications.
  2. Package Redeployment: Identify the necessary values, then redeploy the package with these values set in the configuration file.

For a complete list of the objects you must configure, see the Connected Claims Object Reference.

Step 6: Run the CJF Wrapper process model

Run the CJF Wrapper Process to Write PM ID From UUID process model to automate process model ID assignment.

This process automatically populates the table with the process model ID specific to your target environment, ensuring all workflows use the correct process model ID. It works by querying the unique, unchanging UUID of each process, identifying the corresponding process model ID in the target environment, and updating the CJF_PHASE_STEP_PROCESS.PROCESS_MODEL_ID accordingly. Since this process updates the database, it may take several minutes to complete. If the database tables are cleared and reinserted for any reason, you must rerun this process to ensure correct data alignment.

Step 7: Configure the BAM calendar

Configure the BAM Calendar with working hours.

To set up a new calendar:

  1. Navigate to All Objects and select Process Calendar.
  2. Click New Calendar
  3. Enter BAM Calendar as the calendar name and click Save. Note: If you encounter an "Invalid Time Zone" error during this process, save the default calendar first, then attempt to create the new calendar again.
  4. Choose the appropriate time zone for your location.
  5. Specify the working hours for the company, or save the default working hours (9 AM to 5 PM).
  6. Click Save.

Step 8: Remove API keys

Remove API keys from all integrations for security.

Step 9: Update the database

Update the SERVICE_360_WORKER table with the current user's username. To update the username for the currently deployed user in the SERVICE_360_WORKER table, use the following SQL command:

1

UPDATE 'SERVICE_360_WORKER' SET 'APPIAN_USERNAME' = 'USERNAME' WHERE <condition>;

Replace 'USERNAME' with the actual username of the deployed user.

Step 10: Configure user groups and security

Before you configure user groups and security, here's what you need to know:

  • If your organization has additional business roles not covered in the default groups.
  • What users should be members of each group?

For more information on how to configure groups and security, see the following page:

Feedback