You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.

The DCM_TaskList was previously named AQ_TaskList. In our ongoing effort for DCM 2.0, we renamed this container and moved it from the AquimaLibrary to the DCM library.

The DCM_TaskList Container Type is meant for use with the DCM Lists component. To use it, a Blueriq DCM Lists Service should be running and the Runtime should be configured to locate it.


The DCM_TaskList container can be used to create a tabular overview of the tasks for a single case. Tasks will be displayed in a table that consists of columns which can contain ‘task data’ (task details), ‘actions’ (buttons and events) and 'custom fields'.

The Studio screen for a DCM_TaskList is the same as the screen for Container type: AQ_WorkList. Some features, however, are ignored:

  • The 'Group by case' attribute (the task list only shows tasks for one case)
  • 'Data' columns (this data is the same for all tasks)
  • The 'Mask' property for Task List columns
  • Presentation Style when locked
  • The "show all tasks" parameter (list always filters on role/team/assignee)
  • Sorting of tasks will be processed at the front-end, so pre-sorting on a column that is not visible will be ignored
  • Until Blueriq 14.8, the ordering feature was not passed to the frontend


How to use

A Task List can be placed in a container or directly on a page. The interaction between the task list container and relating service calls is modeled in a flow.

Because the list displays tasks for a case, the case ID needs to be specified for the container. This is achieved by adding a Task data column for the case ID, which is not visible and has a filter on it. The filter should result in a case ID at runtime.

If the case ID column does not exist or somehow the filter does not result in a valid case ID, the container will show an exception and will not be rendered.

Runtime behavior

The DCM_TaskList is only supported by the Material Theme. Sorting, paging and filtering are done on the client side, as all tasks are sent to the client. Additionally, the task list will connect to the runtime to retrieve events and update the list accordingly, in real time. If you experience problems with the real time updates, see Using a reverse proxy server.

Since Blueriq 13.3, started tasks are no longer shown by default. This behavior is now configurable for each Task List by checking the 'Show started tasks' checkbox in Studio.



Note that in the Material Theme, the used table implementation only supports sorting on one column at the same time. This means that the Material theme only uses the first column that has an ordering. All orderings are passed to the frontend, so if you have a custom implementation of a theme and the table implementation supports sorting on multiple columns at the same time, you can use the entire default ordering.

Didn't find the answer you were looking for? Try the advanced search!