Create Custom Task Types and Automations

On This Page

The capabilities described on this page are included in Appian's advanced and premium capability tiers. Usage limits may apply.

What are custom task types and automations

This page explains how to set up custom task types and custom automations for your claims workflows.

Tasks are activities in a claim workflow that require user interaction. Tasks are designed for actions that need human oversight or decision-making like Claim Data Validation for ensuring that critical steps receive the necessary attention. This involvement helps maintain control and accuracy in your claim journeys.

Workflow automations are activities in a claim workflow that do not require user interaction. They automatically start at their designated point in the workflow, perform a specific action based on conditions met, and then move to the next activity without human intervention (for Eg. Auto Adjudicate or Create Assessor Summary). Claim Workflow automations help streamline processes and save time, letting you focus on more important tasks.

Connected Claims comes with some common workflow automations and the following pre-configured task types:

Confirmation
Decision
Document Upload
Set Reserves
Make Payment
Liability Assessment
Cost Estimate
Settlement
Survey
Create Claim
Send Email

If you need custom task types or custom workflow automations, follow the steps on this page to add them for your claims.

Set up custom task types and tasks

To set up custom task types and tasks:

Using your database management tool, add a new row to the CCM_CFG_TASK_BEHAVIOR_TYPE table with the necessary details for your task type. Refer to an existing task type to populate this information.
- Set IS_AUTOMATED to 0 for a task. This identifies the activity as a task.
- In the ICON column, enter the name of the icon to display next to the task in the task list.

In Appian Designer, open the CCM_CFG_TaskBehaviorType record type.

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 CCM_Task record type.
Adding additional fields to an existing record type	Add new fields to the CCM_Task record type by using the Modify Source Fields action.

Update the CCM_WFL_ReferenceTask_RecordAction_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.
Create the task in Connected Claims Configurations and add it to a new task block.
1. Configure a claim type workflow with this task.
Update the a!match() function in the CCM_Task_RecordAction_Complete interface to specify how the interface should display content for your new task type.
- The a!match() function uses the TASK_BEHAVIOR_TYPE_ID from the CCM_CFG_TASK_BEHAVIOR_TYPE table.
- Create a new constant for each new task type ID, as pre-configured task types are referenced through constants.
Update the CCM_Task_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.
Configure the CCM_Task_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.
- There is an a!match() function for displaying completed tasks by task type. Modify the a!match() function to include the new task type, ensuring completed tasks display accurately.

Set up a custom automation

Before you design a custom automation, understand how Connected Claims 2.0 runs background work. Several built-in subprocesses no longer block the main claim process. Document security, document storage, AI summarization, and email notification all run in parallel with it.

This affects how you design a custom automation. Do not assume that these subprocesses have finished by the time your automation runs. If your automation depends on the result of one of them, such as a stored document or an AI summary, check that the data exists before you read it rather than relying on the order the activities appear in the workflow.

To set up a custom automation

Using your database management tool, add a new row to the CCM_CFG_TASK_BEHAVIOR_TYPE table with the necessary details for your task type. Refer to an existing automation to populate this information.
- Set IS_AUTOMATED to 1. This identifies the activities as automation.
- In the ICON column, enter the name of the icon to display next to the automation in the activities list.

In Appian Designer, resync the CCM_CFG_TaskBehaviorType record type.

Configure any new fields.

If you are…	**Then…
Creating a new record type object for the new automation data.	Add a record type relationship to relate this new record type to the CCM_Task record type.
Adding additional fields to an existing record type	Add new fields to the CCM_Task record type by using the Modify Source Fields action.

Create the automation in the Control Panel.
Design a process model to complete the automation and include two script tasks to update the task status and update the task status relationship.
In the Update Task Status node, add a custom output for updating the task status.
Update the expression for the custom output to look similar to this expression:
In the Update Task Status Relationship node, add a custom output for updating the task status relationship.
Update the expression of the custom output to look similar to this:
End the process with a call to the CCM_Task_Complete subprocess to set the task status to complete.
- This marks the automation as completed and opens any subsequent tasks.
- If you are creating an automation with a decision, make sure to pass in the appropriate response option.
- Be sure to Save & Publish.
Add logic to the CCM_Task_Complete_AutomatedTask_Wrapper process model to trigger the new process model for the automation.
- Be sure to Save & Publish.
Test the workflow with the new automation to ensure it works correctly.
Update the CCM_Task_RecordView_Summary interface to adjust the automation summary page.
- There is an a!match() function for displaying automations. Modify the a!match() function to include the new automation, ensuring completed automations display accurately.

Feedback

Was this page helpful?