Uses of Interface
org.camunda.bpm.engine.history.HistoricProcessInstanceReport
Packages that use 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 DeploymentsRuntimeService:
For starting and searching ProcessInstancesTaskService:
Exposes operations to manage human (standalone) Tasks,
such as claiming, completing and assigning tasksIdentityService:
Used for managing Users,
Groups 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
Methods in org.camunda.bpm.engine that return HistoricProcessInstanceReportModifier and TypeMethodDescriptionHistoryService.createHistoricProcessInstanceReport()Creates a new programmatic query to create a historic process instance report. -
Uses of HistoricProcessInstanceReport in org.camunda.bpm.engine.history
Methods in org.camunda.bpm.engine.history that return HistoricProcessInstanceReportModifier 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
Classes in org.camunda.bpm.engine.impl that implement HistoricProcessInstanceReportMethods in org.camunda.bpm.engine.impl that return HistoricProcessInstanceReportModifier 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
Methods in org.camunda.bpm.engine.rest.dto.history that return HistoricProcessInstanceReportModifier and TypeMethodDescriptionprotected HistoricProcessInstanceReportHistoricProcessInstanceReportDto.createNewReportQuery(ProcessEngine engine) Methods in org.camunda.bpm.engine.rest.dto.history with parameters of type HistoricProcessInstanceReportModifier and TypeMethodDescriptionprotected voidHistoricProcessInstanceReportDto.applyFilters(HistoricProcessInstanceReport reportQuery)