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

Available from Blueriq 12.4

The AQ_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 AQ_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'.

For the first version, the Studio screen for an AQ_TaskList is the same as the screen for AQ_WorkList. Some features, however, are ignored:

  • The 'Group by case' attribute
  • 'Data' columns
  • The 'Mask' property for Task List columns

Some features in the Studio screen are not supported yet, but will be in a future release:

  • Default filters
  • Default sort order
  • Presentation Style when locked


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. For now, 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 AQ_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.