Uses of Interface
org.camunda.bpm.engine.history.HistoricProcessInstanceReport
Package
Description
Public API of the Camunda Platform engine.
Typical usage of the API starts by the creation of a
Through the services obtained from such a
Typical usage of the API starts by the creation of a
ProcessEngineConfiguration
(typically based on a configuration file), from which a ProcessEngine
can be obtained.Through the services obtained from such a
ProcessEngine
, BPM and workflow operation
can be executed:RepositoryService
:
Manages Deployment
sRuntimeService
:
For starting and searching ProcessInstance
sTaskService
:
Exposes operations to manage human (standalone) Task
s,
such as claiming, completing and assigning tasksIdentityService
:
Used for managing User
s,
Group
s and the relations between themManagementService
:
Exposes engine admin and maintenance operations,
which have no relation to the runtime execution of business processesHistoryService
:
Exposes information about ongoing and past process instances.FormService
:
Access to form data and rendered forms for starting new process instances and completing tasks.Classes related to the
HistoryService
.API implementation classes, which shouldn't directly be used by end-users.
-
Uses of HistoricProcessInstanceReport in org.camunda.bpm.engine
Modifier and TypeMethodDescriptionHistoryService.createHistoricProcessInstanceReport()
Creates a new programmatic query to create a historic process instance report. -
Uses of HistoricProcessInstanceReport in org.camunda.bpm.engine.history
Modifier and TypeMethodDescriptionHistoricProcessInstanceReport.processDefinitionIdIn
(String... processDefinitionIds) Only takes historic process instances into account for the given process definition ids.HistoricProcessInstanceReport.processDefinitionKeyIn
(String... processDefinitionKeys) Only takes historic process instances into account for the given process definition keys.HistoricProcessInstanceReport.startedAfter
(Date startedAfter) Only takes historic process instances into account that were started after the given date.HistoricProcessInstanceReport.startedBefore
(Date startedBefore) Only takes historic process instances into account that were started before the given date. -
Uses of HistoricProcessInstanceReport in org.camunda.bpm.engine.impl
Modifier and TypeMethodDescriptionHistoryServiceImpl.createHistoricProcessInstanceReport()
HistoricProcessInstanceReportImpl.processDefinitionIdIn
(String... processDefinitionIds) HistoricProcessInstanceReportImpl.processDefinitionKeyIn
(String... processDefinitionKeys) HistoricProcessInstanceReportImpl.startedAfter
(Date startedAfter) HistoricProcessInstanceReportImpl.startedBefore
(Date startedBefore) -
Uses of HistoricProcessInstanceReport in org.camunda.bpm.engine.rest.dto.history
Modifier and TypeMethodDescriptionprotected HistoricProcessInstanceReport
HistoricProcessInstanceReportDto.createNewReportQuery
(ProcessEngine engine) Modifier and TypeMethodDescriptionprotected void
HistoricProcessInstanceReportDto.applyFilters
(HistoricProcessInstanceReport reportQuery)