Integrating Auto-Assignment with CU Life

Introduction

Installing the Auto-Assignment Add-On module with your Connected Underwriting Life Workbench solution consists of three main steps:

• Step 1: Import the database script
• Step 2: Import the application
• Step 3: Incorporation with CU Life

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

System Prerequisites

• Appian platform version 23.3 or greater.
• A supported web browser.
• Imported Connected Underwriting Life Workbench base application.

Step 1: Import the database script

To import the database script:

1. In the target environment, log in as the deployment user.
2. Navigate to the Cloud Database.
3. Click the Appian database.
   • Note: If the base Connected Underwriting Life Workbench application uses a different database than the Appian database, select and click it.
4. Click the Import tab.
5. Upload the sql file and click Import.

Step 2: Import the application

To import the application files:

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 application zip file.
5. Click INSPECT.
6. Review the inspection results. If there are no issues, click IMPORT.
   • Note: The import may time out due to file size, but the import will continue in the background.
7. Review the import results.

Step 3: Incorporation with CU Life

The following incorporation steps are required to utilize the full functionality of the Auto-Assignment Add-On Module.

Configuration of Assignment Rules on the Settings site

1. In the target environment, log in.
2. Navigate to the Appian Designer.
3. Open the Insurance Life Underwriting application package.
4. Search for and open the following interface object: ISL_SitePage_AdminSettings.

5. In expression mode, add an additional map item to local!navBarSections, as seen below:

   

6. In the match() statement in the second column layout (the column that displays the left sidebar navigation), add a condition for displaying the assignment rules page, as seen below:

   

7. Save the interface.

Disable default selection and manual selection of assigned group and underwriter

1. Search for and open the following expression rule: ISL_API_CreateCase_ConstructCaseFromRequestBody
2. Delete or comment out the initialization of the role-related record.
3. Save the rule.
4. Search for and open the following interface object: ISL_Case_Sub_UpdateMiscellaneous
5. In expression mode, where ISL_Role_Sub_Manage is called, pass in false for the showAssignees rule input instead of true.
6. Save the interface.

Incorporate the auto-assignment logic in the case creation process

1. Search for and open the following process model: ISL_Case_Create.
2. Just before the end event, add a synchronous subprocess node labeled Auto Assign. Set up the node as seen below:
3. Save and publish the process model.

Optional Incorporation

The following steps are optional to utilize the full functionality of the Auto-Assignment Add-On Module.

Adding New Fields to Drive Auto Assignment Rules

The following steps are optional and allow you to add additional fields in the auto-assignment logic.

1. Identify which additional fields on the case record type, or on its nested record types, you want to include in auto-assignment logic.
   • Example: Coverage Purpose.
2. Navigate to the Appian Designer and open the ISL Auto-Assignment of Cases application package.
3. Search for and open the following expression rule: ISL_AA_CFG_assignmentFieldReference.
   • Note: This rule stores the configurations for each field that is able to be used in the auto-assignment logic. Take some time to review the design paradigm. Each field has its own map item that contains a reference to its evaluation rule, a reference to its configuration interface, allowed operators, etc.

   

4. Create an evaluation rule for your new field by duplicating an existing evaluation rule and following the same design approach.
   • Note: Choose an existing evaluation rule to duplicate that is most similar to your new field evaluation. For example, since a coverage purpose rule condition will have similar evaluation logic to a product type rule condition, duplicate ISL_AA_RuleCondition_evaluationForProductType.
     • Example: ISL_AA_RuleCondition_evaluationForCoveragePurpose
     • Required rule inputs:
       • ruleCondition: ISL_AA_CFG_RuleCondition
       • case: ISL_Case
       • Note: The rule should contain a match() statement where each possible operator for the field has its own expression to evaluate.
5. Ensure that the new rule is added to the ISL Auto-Assignment of Cases application package.
6. Create a configuration interface for your new field by duplicating an existing configuration interface and following the same design approach.
   • Note: Choose an existing configuration interface to duplicate that is most similar to your new field configuration. For example, since coverage purpose will be configured in a similar way to product type (selecting a value from a dropdown of options from a reference table), duplicate ISL_AA_RuleCondition_configurationComponentForProductType.
     • Example: ISL_AA_RuleCondition_configurationComponentForCoveragePurpose
       • Required rule inputs:
         • currentRuleCondition: ISL_AA_CFG_RuleCondition
         • genBundle: Any Type
         • conditionMap: Map
         • isLabelCollapsed: Boolean
         • accessibilityText: Text
7. Ensure that the new interface is added to the ISL Auto-Assignment of Cases application package.
8. Add a map item to ISL_AA_CFG_assignmentFieldReference.
   • code: Create a constant for the code that you want to use to represent this field, and call the constant here.
   • evalRule: Rule reference to the evaluation rule you just created.
   • label: Create a key-value pair in the ISL_AA bundles for the label that will display when configuring this type of rule condition (i.e., “Coverage Purpose”), and call the key here.
   • configurationComponent: Interface reference to the configuration interface you just created.
   • allowedOperators: List of allowed operators using the available constants (same as the operators used in the match() statement of the evaluation rule).
     • {cons!ISL_AA_TXT_CONDITION_OPERATOR_EQUALS, cons!ISL_AA_TXT_CONDITION_OPERATOR_NOT_EQUALS}
9. Search for the existing operator constants by searching for ISL_AA_TXT_CONDITION_OPERATOR_.
10. Repeat steps 8-9 for each desired additional field.
11. Save ISL_AA_CFG_assignmentFieldReference.
12. Test the new rule condition types by creating and applying assignment rules using them.

Feedback