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

The DCM_CaseList is only available when the dcm-lists-client is enabled.

This container displays a list of cases which are started (see Rich Containers for Lists). When a case is selected, the corresponding id is returned. The case selector container will function comparable to the current DCM_Worklist container: clicking a case on an action button will place the id in the selected target attribute for the case id.

The data which is shown in the case selector container is retrieved from the process engine database (like the current DCM_Worklist container). The data in the database is filled automatically by the process engine when storing the profile after mapping connected to a task.       

It is possible to filter and sort the case list.

Parameters

NameDescriptionTypeRequired
Display text when list is emptyThe text item showing when the list is empty.Text itemNo
Paging sizeIndicates the number of cases per page.IntegerNo
Group byGroup cases by the entity and attribute (defined in your process module) on which will be grouped.AttributeNo
Target attribute case IDSpecify the entity and attribute where the case is will be stored.StringNo
ElementsSpecify the columns of the table.ElementNo

You can add the following types of columns to the case list.

  • Data - Please see DCM_Worklist for documentation
  • Action - Please see DCM_Worklist for documentation
  • Case Data
  • Case Metadata

In the Case Data column standard metadata of a case can be selected. The options are:

  • Creation Date - The datetime when the case was created.
  • Display Name - The display name as defined in Encore.
  • Name - The technical name as defined in Encore.
  • Id - Case identifier (caseId) (Should not be made visisble as it is a technical Id)

The Case Data column has two more options, 'Order by', and 'Mask', which are documented at the DCM_Worklist.

In the Case Metadata column the metadata of the selected Case aggregate can be filled in.

There are quite a number of filter options which can be applied to the (meta)data columns:

Filter

Datatypes

Description

EqualsAll single-valued datatypesResults in true if the value of the task equals the filter value.
Not equalsAll single-valued datatypesResults in true if the value of the task is different to the filter value.
Less thanAll single-valued datatypesResults in true if the value of the task is less than the filter value.
Less than or equalsAll single-valued datatypesResults in true if the value of the task is less than or equal to the filter value.
Greater thanAll single-valued datatypesResults in true if the value of the task is greater than the filter value.
Greater than or equalsAll single-valued datatypesResults in true if the value of the task is greater than or equals the filter value.
LikeStringResults in true if the filter value is a substring of the value of the task.
Not likeStringResults in true if the filter value is not a substring of the value of the task
InMultivalued datatypesResults in true if there exists an attribute in the multivalued task value, which is also present in the multivalued filter value. If you use a single-valued attribute, this function behaves like equals.
Not inMultivalued datatypesResults in true if there exists an attribute in the multivalued task value, which is not present in the multivalued filter value. If you use a single-valued attribute, this function behaves like not equals.

How this container looks at runtime can be found here: Rich Containers for Lists