...
- REST APIs for providing data to UIs
- Provides REST services, by utilzing 1) Camunda REST APIs, such as BPMN XML string, process activity data, process variable, statistic, and 2) SO Request DB APIs for a service list.
- Consolidate data responses from multpile Camunda calls and feed them to UIs.
- Use of HistoryService APIs, example, processEngine.getHistoryService().createHistoricProcessVariableQuery().xyz
- Set a History level to ACTIVITY as a minimum; AUDIT (default) level for process variable tracing
- Provides workflow tracing (between parent-child workflows, interaction with other services; service task in and out); example,
- processEngine.getRuntimeService().createExecutionQuery().processVariableValueEquals("serviceInstanceId", serviceInstanceId).singleResult();
- Custom Query
- Custom Query against History ACT_HI_DETAIL database table, as needed
- Custom History Event Producer
- Populate additional data in history with extensibility
- Estimates
- Note:
- It is a rough estimate - to be refined
- Estimate includes development and unit testing time
Component | Development Estimate | Comments |
---|---|---|
SO Service List widget | 80 hours / UI developer |
|
Statistic Dashboard | 40 hours / UI developer |
|
Service Instance Rendering and Detail Panel | 120 hours / UI developer |
|
Rest APIs for supplying data | 80 hours / Java developer |
|
Custom History Producer | 40 hours / Java developer |
|