Add and Configure Task Forms

Task forms are forms that users use to complete the tasks assigned to them within Connected Claims.

This page will introduce you to task forms, how they work, and provide brief examples of how to configure them to best fit your claims management processes.

What are task forms?

When a user is assigned a task, they will open the task to see a task form that allows them to complete all necessary parts of the task. Each task in Connected Claims has a task form associated with it and each task form is automatically populated with the information and data fields from the task created in the Control Panel.

Task forms are pre-configured out-of-the-box (OOTB) and are auto-populated, so unless you need to make further configurations to better fit your use claim, the forms require no additional configurations. If you want to include specific information or make additional configurations to your task form, you can make changes to task forms directly in Appian Designer. These forms cannot be configured in the Control Panel.

How do task forms work?

All task forms in your claims management application are part of one OOTB interface object.

The interface object that holds all of these task forms is CCM_Task_Sub_TaskBehaviorTypeCompleteDynamicDisplay and can be found in the Connected Claims Management Base application in Appian Designer.

The interface object is pre-configured with task forms for the eleven OOTB task types:

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

Using conditional logic, the interface expression sorts the task by task type and uses the a!match() function to define and render the correct form for the specific task.

The following images show the OOTB task forms for some of the task types.

• Task form for the confirmation task type

  

• Task form for the decision task type

  

• Task form for the document upload task type

  

You can also make more configurations to the task forms interface to create task forms for additional task types. To learn how to add new task forms to the interface, see Configure Custom Task Types and Automations.

Configure task forms

Just like with all interface objects, the CCM_Task_RecordAction_Complete interface for task forms is configurable in Appian Designer.

To configure the task form for an existing task type, just edit the section for the task type in the then parameter of the a!match() function in your interface expression. You can edit the existing configurations, add new components, and call information into the task form. Note that task form configurations are made at the task types level. These configurations will apply to the task forms for every task in that task type.

To add configurations that you want to apply to all of the task forms across all task types, add the expressions for the additional configurations above the a!match() function in the contents parameter of the a!columnLayout().

Add summary data from the Control Panel to task forms

One common kind of configuration is adding context for your users to task forms by including data from the claim type summary page in the Control Panel.

This simple and helpful configuration uses three main functions to call and index into the data for a specific claim.

The first function,a!studio_fieldsForRecordType(), returns information about all of the fields relevant to the record type that the tasks are associated with. This includes fields shared in all claims in the Control Panel, as well as the fields for the claim category and claim type of the relevant tasks.

The second function, a!studio_indexRecord(), indexes into a specific record, based on your claim, to call only the relevant fields and data for that record.

The third function, a!studio_getRuntimeData(), runs a query to return the data for the specified record type relevant to the tasks.

You can either add the summary data from the Control Panel to the task forms for all task types in your claims management app, or add the data to the task forms for only one task type. Both of these methods use the same expressions and functions, just in different orders.

Example: Add summary data to the task forms for all task types

To add summary data from the Control Panel to the task forms for all task types:

1. In the expression of the CCM_Task_RecordAction_Complete interface, paste the following expression directly below the definition of local!metrics on line 5 and above the start of the a!formLayout() function on line 6.

   • The pasted expression will now be lines 6-62 in your interface.

     1
     2
     3
     4
     5
     6
     7
     8
     9
     10
     11
     12
     13
     14
     15
     16
     17
     18
     19
     20
     21
     22
     23
     24
     25
     26
     27
     28
     29
     30
     31
     32
     33
     34
     35
     36
     37
     38
     39
     40
     41
     42
     43
     44
     45
     46
     47
     48
     49
     50
     51
     52
     53
     54
     55
     56
     57
     local!claim: rule!CCM_QR_GetClaim(
     claimId: ri!task['recordType!{ee5aa46d-0228-430f-a794-1134a11fbcc0-ccm}CCM_Task.fields.{937a6bf5-2134-4806-a64a-fc67cfdcdf5c-ccm}claimId']
     ),
     local!recordTypeUuids: rule!CCM_UTIL_RejectBlank(
     {
       a!defaultValue(
         value: local!claim['recordType!{d81cdd0e-c54d-4b8e-beec-b7ae37fefe7f-ccm}CCM_Claim.relationships.{8beba714-f253-41d2-9232-e0c0f51bed2e-ccm}cfgClaimType.fields.{3997ebba-9124-4f4a-9f0f-a3e707f28bf1-ccm}recordTypeUuid'],
         default: cons!CCM_UUID_RECORD_TYPE_CLAIM
       ),
       {
         /*we need to check if the parent case category has a recordTypeUuid if not we should not pass any related record*/
         if(
           a!isNotNullOrEmpty(
             local!claim['recordType!{d81cdd0e-c54d-4b8e-beec-b7ae37fefe7f-ccm}CCM_Claim.relationships.{8beba714-f253-41d2-9232-e0c0f51bed2e-ccm}cfgClaimType.fields.{3997ebba-9124-4f4a-9f0f-a3e707f28bf1-ccm}recordTypeUuid'],
           ),
           if(
             and(
               a!isNotNullOrEmpty(
                 local!claim['recordType!{d81cdd0e-c54d-4b8e-beec-b7ae37fefe7f-ccm}CCM_Claim.relationships.{8beba714-f253-41d2-9232-e0c0f51bed2e-ccm}cfgClaimType.relationships.{4ea8efcb-29f4-4396-ad57-dfcc61d8b6ea-ccm}parentClaimType.fields.{3997ebba-9124-4f4a-9f0f-a3e707f28bf1-ccm}recordTypeUuid'],
               )
             ),
             {
               local!claim['recordType!{d81cdd0e-c54d-4b8e-beec-b7ae37fefe7f-ccm}CCM_Claim.relationships.{8beba714-f253-41d2-9232-e0c0f51bed2e-ccm}cfgClaimType.relationships.{4ea8efcb-29f4-4396-ad57-dfcc61d8b6ea-ccm}parentClaimType.fields.{3997ebba-9124-4f4a-9f0f-a3e707f28bf1-ccm}recordTypeUuid'],
               cons!CCM_UUID_RECORD_TYPE_CLAIM
             },
             cons!CCM_UUID_RECORD_TYPE_CLAIM
           ),
           {}
         )
       }
     }
     ),
     local!iteratedStudioFields: a!flatten(
     a!forEach(
       items: local!recordTypeUuids,
       expression: a!localVariables(
         local!recordtypeUuid: fv!item,
         local!studioFields: a!studio_fieldsForRecordType(recordTypeUuid: local!recordtypeUuid),
         a!forEach(
           items: local!studioFields,
           expression: a!map(
             field: fv!item.displayName,
             value: a!studio_indexRecord(
               record: a!studio_getRuntimeData(
                 recordTypeUuid: local!recordtypeUuid,
                 identifierField: 'recordType!{d81cdd0e-c54d-4b8e-beec-b7ae37fefe7f-ccm}CCM_Claim.fields.{f4bdff4d-4087-4519-bf34-34a1139e5c3d-ccm}claimId',
                 identifier: local!claim['recordType!{d81cdd0e-c54d-4b8e-beec-b7ae37fefe7f-ccm}CCM_Claim.fields.{f4bdff4d-4087-4519-bf34-34a1139e5c3d-ccm}claimId']
               ),
               fieldUuid: fv!item.fieldUuid,
               relationshipUuids: fv!item.relationshipUuids,
               default: "Contact your admin"
             )
           )
         )
       )
     )
     ),
     

2. Paste the following expression in the contents parameter of the a!columnLayout() and directly above the a!match() function on line 96. The pasted expression will now be lines 96-103. Since this section of the expression is not contained within the a!match() function, the summary data will display on the task forms for all task types.

   1
   2
   3
   4
   5
   6
   7
   8
                  a!forEach(
                    items: local!iteratedStudioFields,
                    expression: a!textField(
                      label: fv!item.field,
                      value: fv!item.value,
                      readOnly: fn!true()
                    )
                  ),
   

3. Configure the a!forEach() expression you just pasted to display the summary data however you'd like.

   Tip:  The default value in line 56 of the expression in your interface is the message that will show when no record is returned. It is a best practice to edit the default value to show a message appropriate for your use case and audience.

Example: Add summary data to the task form for one task type

This set of steps to add summary data from the Control Panel to the task forms for only one task type is very similar to the example in Add summary data to the task forms for all task types. The only difference is that we need to add the a!forEach() expression into one of the task form definitions for a specific task type. The task form definitions for each task type are found in the then parameter of the a!match() function. Putting the a!forEach() expression inside one of these definitions is what allows the summary data from the Control Panel to display only on the task forms for that specified task type.

To add summary data from the Control Panel to the task forms for only one task type:

1. Follow step 1 in Add summary data to the task forms for all task types.
2. In the then parameter of the a!match() function (the a!match() function is on line 96), find the part of the expression that defines the task type you want to display summary data from the Control Panel for.
   • The line numbers for the OOTB task types are as follows:
     • The Confirmation task type definition starts on line 98.
     • The Decision task type definition starts on line 125.
     • The Document Upload task type definition starts on line 163.

3. Copy and paste the following expression into the definition of the task type you want to add it to. You can put the expression with a!forEach() either above or below the a!richTextDisplayField() within the a!match() expression, depending on where you want the summary data from the Control Panel to appear on the form.

   1
   2
   3
   4
   5
   6
   7
   8
                  a!forEach(
                    items: local!iteratedStudioFields,
                    expression: a!textField(
                      label: fv!item.field,
                      value: fv!item.value,
                      readOnly: fn!true()
                    )
                  ),
   

4. Configure the a!forEach() expression you just pasted to display the summary data however you'd like.

   Tip:  The default value in line 56 of the expression in your interface is the message that will show when no record is returned. It is a best practice to edit the default value to show a message appropriate for your use case and audience.

Feedback