2. Getting started - Module structure

Module structure for a process solution

This chapter is written to describe what is necessary to create a solution for Dynamic Case Management (DCM). A DCM solution is built using at least five modules listed below:

• Dashboard 
• Widget_Execution
• Case_Model
• Task_Execution
• Mapping

Dashboard

This module is a standard interaction module which will function as the entry-module of a DCM solution. The dashboard will display a collection of information from different sources. The dashboard should be a lean module with the dashboard pages containing flow widgets. The real information can be found inside the widgets which are modeled in other modules.

Items listed below are expected in this module:

• Dashboard pages
• Flows for dashboard pages
• Widget containers
• Containers for the layout of the dashboard

Widget_Execution

One or more widget execution modules will contain all the flows and other elements which are needed to execute the content for the widgets in the widget dashboard. These modules are created using an interaction module.

Items listed below are expected in this module:

• Work and case lists 
• Flows to start case instances
• Flows, pages, containers, services, to create the content for the widgets  

Case_model

The Case_Model module is an essential part of the DCM solution. It is used to manage the tasks which belong to a case. The ability to use ad-hoc tasks, a case context, an inference engine and events offer the possibility to make a case really dynamic. This module is a process module.

The process module offers the functionality below:

• Creating case and task instances
• Storing the data connected to the task and case instances
• Storing of the case profile
• Evaluation if a task can be executed
• Authorization, routing and priority of tasks

Mapping

The mapping offers functionality to create mappings between two modules. Two types of mappings are available, task and data mapping.

Task mapping

The task mapping is used to make a connection between tasks in a process module and flows in a task_execution module. Using the mapping you can model which flow will be started when a task is executed. The end event of the flow and task could be mapped as well. In Blueriq Encore, it is possible to manually select a data mapping that is executed between the process module and implementation module. 

Data mapping

The data mapping is used to enter values in the profile of a session to a profile of another session. This mapping functions between two interaction modules or between a process and interaction module.

Task_Execution module

The execution of tasks is done using flows in one or more Task_Execution modules. These implementation modules are the default Blueriq modules and offer the same functionality. All exposed flows in these modules will be available in the task mapping to create a connection to a task.

Items listed below are expected in this module:

• Flows, pages, containers, services, for the flows to execute tasks

The functionality of this module is standard Blueriq functionality and will not be explained further in this document.

An example of the structure for the interaction modules.