Free cookie consent management tool by TermsFeed

Configuring Custom Task Types

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

Overview

Tasks are activities in a workflow that require user interaction. They are actions that need human oversight or decision-making, ensuring that critical steps receive the necessary attention. This involvement helps maintain control and accuracy in your processes.

The CU Life Workbench ships with three pre-configured task types: Confirmation, Decision, and Document Upload. See Preset task types for more details.

cul_create_tasks_default_types_02

This page explains how to set up custom task types for your workflows, if you need them.

Set up custom task types and tasks

To set up custom task types and tasks:

  1. Using your database management tool, add a new row to the ISL_TSK_CFG_TASK_TYPE table with the necessary details for your task type. Refer to an existing task type to populate this information.
    • In the ICON column, enter the name of the icon to display next to the task in the task list.
  2. In Appian Designer, resync the ISL_CFG_TASK_TYPE record type.

  3. Configure any new fields.

    If you are… Then…
    creating a new record type object for the new task data add a record type relationship to relate this new record type to the ISL_TSK_CaseTask record type.
    adding additional fields to an existing record type add new fields to the ISL_TSK_CaseTask record type by using the Modify Source Fields action.
  4. Update the ISL_TSK_CaseTask_RecordAction_AddFromLibrary_CreateUpdate interface and make any necessary configurations to support your new task.
    • For example, if the task requires users to select a value from a set of options, add a dropdown with the values to the interface.
  5. Create the task in Connected Underwriting - Life Settings and add it to a new task block.
  6. Update the a!match() function in the ISL_TSK_CaseTask_RecordAction_Complete interface to specify how the interface should display content for your new task type.
    • The a!match() function uses the TASK_TYPE_ID from the ISL_TSK_CFG_TASK_TYPE table.
    • Pre-configured task types are referenced through constants, so you must create a new constant for each new task type ID.
  7. Update the ISL_TSK_CaseTask_RecordAction_Complete process model if you need to write new data or add unattended activities during task completion, like calling a subprocess to post to an integration.
    • Note: This process is reused for all task types.
  8. Configure the ISL_TSK_CaseTask_RecordView_Summary interface as necessary to include the new task type and add any new data that you want to display on the task's summary page.

Feedback