How to customize the display of a worklist
This poses a challenge when you need to present a new column in a worklist display.
To address this, V4.2 includes nine generic, unassigned properties to support worklist displays. You can use these properties to hold additional data from work objects, and to hold values that depend upon or vary by work type.
For Process Commander V5.4+, a more direct approach is available. See How to customize the worklist display using a JOIN.
The approach is to use normal properties in the work object for most processing and computations, but then to automatically copy appropriate data over to these generic worklist properties, using a simple Declare Expression rule, for display.
These generic properties apply to the class Data-Assignment-. They are referenced in database view
pcv4_assignment_summary, (corresponding to the class Data-Assignment-Summary) and they are also exposed as columns in database table
Assume that you need to enhance the worklist display for one work type (for example, the work type Customer Requests) to include an extra column for property pyAgeFromDate. This property is not exposed a database column in the pc_work table.
Before the change , the worklist display for Customer Requests appears as:
After the change the worklist includes the Age From Date value. Note the added column Age from Date, which presents the values of property pyAgeFromDate (which is still not an exposed property).
Below is a worklist presented in the Process Work space, when All (is selected as the Work Type. (This is part of the My Work in Progress gadget).
In this example, there are four work types:
Below is a worklist display restricted to only assignments for the Customer Request work type This worklist is displayed by a standard list view rule named Data-Assignment-Summary.WorkList_CustomerRequest.
To customize the display for one work type::
1. Copy and update (override) the standard Rule-Obj-MapValue named Data-Assignment-.getWorkListVName to map a Work Type Class to a specific list view rule to run. Specify only the middle key part of the list view. For example, in the standard map value rule, the work type row input PegaSample-CustomerRequest maps to the list view Data-Assignment-Summary. WorkList_CustomerRequest.ALL.
The bottom row — the default, or none-of-the-above case —of the standard map value returns blank.. In this case, the class of the view is Assign-Worklist. This is the default setting, for backwards compatibility.
NOTE: If you need to have the class of this default view be Data-Assignment-Summary rather than Assign-Worklist, you can create and use a user-defined gadget in place of the standard 'My Work in Progress' gadget.
Now copy and override standard the list view rule named Data-Assignment-Summary.WorkList_CustomerRequest. (If you are using a work type for which no standard list view rule exists, create a new list view with a different middle key part, following this example list view.)
2. Next, you need to add a property such as pyAgeFromDate that is not defined in the database view to this view above as the Age From Date column seen in the example.
As in the image below, update your list view WorkList_CustomerRequest to display the property pyWorkListDateTime1 as a displayed column with the title Age From Date.
3. Create a Rule-Declare-Expression PegaSample-CustomerRequest with target property pyWorkListDateTime1 and sets its value to property pyAgeFromDate. This copying is necessary because the property pyAgeFromDate is not defined and not exposed in the database view or tables.
4. Test the configuration. Access the worklist, and select the work type Customer Request.
The worklist display now presents assignments of work type Customer Request with the extra Age From Date column listing the values of property pyWorkListDateTime1 defined in the database view with values from property pyAgeFromDate.