Configure Attended and Unattended Tasks

Overview

This page explains how to set up attended and unattended tasks for your workflows.

Attended tasks are tasks within a workflow that require user interaction. These tasks are designed for 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.

Unattended tasks automatically start at their designated point in the workflow, perform a specific action, and then move to the next task without needing user interaction. This automation helps streamline processes and saves time, letting you focus on more important tasks.

Case Management Studio comes with three pre-configured attended task types: confirmation, decision, and document upload. Unattended task types are not provided. If you need additional attended or unattended task types, follow the steps on this page to add them.

Set up an attended task

To set up an attended task:

1. Using your database management tool, add a new row to the CMGT_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 an attended task. This identifies the task as attended.
   • 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 CMGT_CFG_TASK_BEHAVIOR_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 CMGT_Task record type.
   adding additional fields to an existing record type	add new fields to the CMGT_Task record type by using the Modify Source Fields action.

4. Update the CMGT_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.
5. Create the attended task in Studio and add it to a new task block.
6. Configure a case type workflow with this task.
7. Update the a!match() function in the CMGT_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 CMGT_CFG_TASK_BEHAVIOR_TYPE table.
   • Create a new constant for each new task type ID, as pre-configured task types are referenced through constants.
8. Update the CMGT_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 that this process is reused for all task types.
9. Configure the CMGT_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 an unattended task

To set up an unattended task:

1. Using your database management tool, add a new row to the CMGT_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 1. This identifies the task as unattended.
   • 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 CMGT_CFG_TASK_BEHAVIOR_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 CMGT_Task record type.
   adding additional fields to existing record type	add new fields to the CMGT_Task record type by using the Modify Source Fields action.

4. Create the unattended task in Studio and add it to a new task block.
5. Design a process model to complete the task, ending with a call to CMGT_Task_Complete to set the task status to complete.
   • This completes the task and opens any subsequent tasks.
   • If you are creating an automated decision task, make sure to pass in the appropriate response option.
   • Be sure to Save & Publish.
6. Add logic to the CMGT_Task_Complete_AutomatedTask_Wrapper process model to trigger the new process model for the unattended task.
   • Be sure to Save & Publish.
7. Test the workflow with the new unattended task to ensure it works correctly.
8. Update the CMGT_Task_RecordView_Summary interface to adjust the task 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.

Feedback