You are viewing the documentation for Blueriq 13. Documentation for other versions is available in our documentation directory.
This datasheet contains a description of the aspects of the data solutions and gives a quick overview of the functionalities.
Who is this datasheet for?
This section is intended for modelers and developers who use or are intending to use Blueriq.
Organization of this datasheet
Business activity monitor data
Business activity monitor data in short BAM data is data that is used to support managers and/or team leaders in their daily work. BAM data is not domain specific but operational data that is available real time. Managers can use the data for example to distribute work across teams.
| Standard | |
|---|---|
| Data | Based on static metadata from aggregates or processes |
| Databases | Oracle, MSSQL, h2 (h2 only for development purpose) |
Customer data
Customer data is data that belongs to cases. Customer data is domain specific and is available real time.
| Standard | |
|---|---|
| Aggregate types | Types can be defined in Blueriq studio (Persistency Management guide#Aggregatedefinition) |
| Authorization | Role based and is set on aggregate type (Persistency Management guide#Authorization) |
| CRUD | CRUD services (Service call type: AQ_Aggregate_Create, Service call type: AQ_Aggregate_Read, Service call type: AQ_Aggregate_Update, Service call type: AQ_Aggregate_Delete) available in Blueriq studio |
| Databases | Oracle, MSSQL, h2 (h2 only for development purpose) |
| Deployment | OOTB deployment |
| External access | BAAS. Blueriq is responsible for the data so no direct access. Important for tracing |
| List | List containers (Container type: AQ_Aggregate_List) in Blueriq studio, including records with 'and' search statements on metadata |
| Maintenance | Custom screens and flows can be modelled in Blueriq studio for life events |
| Migrations | Micro migrations (Persistency Management guide#Migration) Lazy conversion API (How to lazily convert aggregates to a new version) |
| Performance | Runtime performance reports |
| Related data | Reference attributes (Persistency Management guide#Referencesbetweenaggregates) in Blueriq studio |
| Search | Search service (Service call type: AQ_Aggregate_Search) in Blueriq studio, including records with 'and' search statements on metadata |
| Transactional scope | Blueriq service |
| Update mechanism data | Full update of data |
| Versioning data | Versioning (Persistency Management guide#Versioning) is possible in update service (Service call type: AQ_Aggregate_Update) |
Comment data
Comment data is user data that contains comments of users.
| Standard | |
|---|---|
| Add | Container (Container type: AQ_Dashboard_Comment) in Blueriq studio |
| Databases | Oracle, MSSQL, h2 (h2 only for development purpose) |
| Filter | Based on reference id, userName and display period |
| List | Container (Container type: AQ_Dashboard_CommentList) in Blueriq studio |
Process data
Process data is system data that is used to store and show work and process lists.
| Standard | |
|---|---|
| Databases | Oracle, MSSQL, h2 (h2 only for development purpose) |
| Data access | Backend REST API |
| List | Container (Container type: AQ_WorkList, Container type: AQ_CaseList) in Blueriq studio |
| Performance | Runtime performance reports |
Reporting data
Reporting data is data that can be used as input for data warehouses.
| Standard | |
|---|---|
| Databases | Oracle |
| Export | Profile can be exported with Service call type: AQ_Report to an external system |
Trace data
Trace data is data that is used to store events.
| Standard | |
|---|---|
| Databases | Oracle, MSSQL, h2 (h2 only for development purpose) |
| Entries | Aggregate Traceability, Process traceability, Decision Requirements Graph or DRG in runtime |
| Performance | Runtime performance reports |
Overview
Content Tools