Item | Description |
|---|---|
Activity | The name within BPMN for a unit of action. The equivalent in Blueriq is a Process task. |
Ad-hoc node | A node which does not have an incoming sequence flow to open the task. These node can have an expression as precondition to make the node available. It is possible to flow from an adhoc node. |
Aggregate | A collection of information on one subject. |
BAM | BAM describes the processes and technologies that provide real-time situation awareness, as well as access to and analysis of critical business performance indicators, based on event-driven sources of data. |
Case | Is a specific instance of a Process. |
Catching | Catching is a term in BPMN to describe the direction of an event. Catching means that a event is received by an event node. |
Complex event handling | Using different types of events to influence the behavior of processes. The event types supported in the Blueriq process engine are: Message, Timer and Conditional. |
Connection | A connection specifies where a file stored. It consists of a name which can be used in the model. The connection is set in a property file stating whether it is in memory or on the file system (and at which path). |
Dashboard | A page which is used to display an overview of information on one entity, for example: a customer, a patient, a case, etc. |
End node | A node which is used to end a process or a flow. |
Event | An event is a process modeling element, representing something that “happens” during the course of a process. Events affect the flow of the process. |
Message | A set of data. |
MessageBus | A software solution which is used to transport messages from a sender to one or more receivers. |
Message event | A process modeling element which can carry data and can influence the behavior of processes. Within the Blueriq platform the Message event is used in the process module. |
Node | An element which can be used for modelling in the Blueriq platform |
PCA | Process Control Application: An implementation module which is used to create a dashboard. This module contains the functionality to steer the behavior of the process engine. The current term for the PCA is Dashboard. |
Process control flow | The flow which is used to start processes, and tasks. The process control flow can be found in the Dashboard/PCA. |
Portal | Within the Blueriq the term Dashboard is used instead of portal. |
Portlet | Portlets are pluggable software components that are managed and displayed in a web portal. Within Blueriq the term widget is preferred for this functionality. |
Prioritisation | The possibility to influence the sequence of tasks in a task list |
Process | Sequence of interdependent and linked procedures which, at every stage, consume one or more resources (employee time, energy, machines, money) to convert inputs (data, material, parts, etc.) into outputs. These outputs then serve as inputs for the next stage until a known goal or end result is reached. |
Process mining | Process mining is a process management technique that allows for the analysis of business processes based on event logs |
Reporting | Human readable reports from various datasources |
Roles | An aspect of a user which has a specific set of qualities connected to it. |
Routing | Directing a task to a user or a user group which is best suited to execute a task. |
Start node | A node which is used to start a flow or a process. |
Task | The smallest identifiable and essential piece of a job that serves as a unit of work. |
Throwing | Throwing is a term in BPMN to describe the direction of an event. Throwing means that an event is send from an event node. |
Timer event | An process modeling element which is triggered by reaching a specified moment. It is used to influence the behavior of a process. A timer event can be used in the process module. |
Widget | Is a stand alone set of information which can be displayed on a portal page. Within Blueriq a widget will be a container which displays the pages within a connected flow. |
Worklist | A list which shows the task a user can or must execute. |
Overview
Content Tools