You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
Corresponding with release | 16.0 |
|---|
This library contains all elements for process modelling with Blueriq.
Changes in this version:
- added process type Process
- added service type AQ_AssignTask
- added service type AQ_ExecuteTask
- added service type AQ_GetCaseInfo
- added service type AQ_GetTaskInfo
- added service type AQ_NextTasksForCase
- added service type AQ_NextTasksForMessageEvent
- added service type AQ_TaskStatus
- added service type AQ_ThrowMessageEvent
- added container type AQ_CaseList
- added container type AQ_Dashboard_Comment
- added container type AQ_Dashboard_CommentList
- added container type AQ_Statistic_Process
- added container type AQ_Timeline
- added container type AQ_Worklist
- added content style timeline
Process types in this version
Name | Description |
|---|---|
| Process |
Container types in this version
Name | Description |
|---|---|
| AQ_CaseList | Use this container type to create a tabular overview of current cases. |
| AQ_Dashboard_Comment | This container shows comments from users. It contains a text area and a comment button. |
| AQ_Dashboard_CommentList | This container is able to present to you a list of placed comments on an item. It is able to filter on a certain user and only display comments within a certain time period. |
| AQ_Statistic_Process | A container that receives information from the process database to show in the AQ_Statistic_Visualization |
| AQ_Timeline | A container that is able to show you a timeline of past events. You can set a filter for a specific case and time period. |
| AQ_WorkList | This container creates a tabular overview of a person’s work- or caseload. |
Service types in this version
Name | Description |
|---|---|
| AQ_AssignTask | Use this type of service to assign the active task - either to a specific user - or to one or more teams or roles. |
| AQ_ExecuteTask | This type of service is used to execute the active task. A task will be active when a user starts a task via the workload container, via the AQ_NextTasksForCase service or via a custom service. |
| AQ_GetCaseInfo | This service retrieves case information. |
| AQ_GetTaskInfo | This type of service is used to retrieve information from the current task for displaying purposes. The attribute types that are used in the parameters should match the type of information returned by the service to avoid type conversion errors. |
| AQ_NextTasksForCase | This type of service is used to activate the next task when only one is available for the active case. Services of this type will return one of the following events: - "One" when the next task available is activated for the active case, - "None" when there is no task available for the active case, - "Multiple" when there are more than one tasks available for the active case. |
| AQ_NextTasksForMessageEvent | This type of service is used to activates the next task when only one new task is available after throwing a message event. Services of this type will return one of the following events: - "One" when the next task available is activated after the message event, - "None" when there is no task available after the message event, - "Multiple" when there are more than one tasks available after the message event. |
| AQ_TaskStatus | Use this type of service to determine the status of the active task. The status is returned in the form of an event, which can be used to direct the pageflow. |
| AQ_ThrowMessageEvent | This service can be used to throw a message event towards the process engine. You select a defined message event and fill the content of the message with expressions in the context of your current domain. |
Content styles in this version
Name | Description |
|---|---|
| timeline | This content style shows a time line of events. |
Overview
Content Tools