...
- The Service List panel supports pagination, which will be controlled by the Navigation buttons.
- Queries a service list from the SO Request DB through the Monitoring REST APIs.
- Action buttons are enabled/disabled based on data population and/or context.
...
- Capabilities
- After the user fills up the desired search crtieria fields, and click the Search button.
- Capabilities
...
- use Camunda REST API, get/process-defintion/{id}xml
- Get the state of a process instance from the activity-instances
- Use Camunda REST API, get/process-instance/{id}/activity-instances
- Render the BPMN XML with bpmn.io and places markers on top of it, and provide Service instance detail views.
- Rendering code example
- Import BPMN XML string through Camunda REST APIs and render the BPMN workflow.
- Attache overlay events on the Call Activities for drilling down and display details.
...
- Task Drill-Down/Drill-Up and Detail View
- Support Task (CAll Activity) drill-down/drill-up capabilties.
- When a call activity task is selected, the Drill-Down button will be enabled.
- Provide detail views for the selected Task.
- When a task is selected including the call activity, the Detail view panel will display details for the selected task.
- Task Drill-Down/Drill-Up and Detail View
- Sub-Service Instance Rendering and Detail View
- Get a sub process defintion XML through the Service Id and Process Instance association.
- Use Camunda REST API, get/process-definition/{sub-id}/xml
- Get the state of a sub-process instance from the activity-instances.
- Use Camunda REST API, get/process-instance/{sub-id}/activity-instances
- Render the BPMN XML with bpmn.io and places markers on top of it, and provides service instance detail views.
- This widget uses the same code of the Service Instance Rendering and Detail View with the sub-process instance id.
- The Drill-Up button will be enabled.
- Sub-Service Instance Rendering and Detail View
- 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
- Create a REST API, getServiceList with search criteria
- invoke getInfraRequest(...) to collect service list data based on search criteria.
- Custom History Event Producer
- Populate additional data in history with extensibility
...