Uses of Interface
org.camunda.bpm.engine.history.HistoricProcessInstanceReport

Packages that use HistoricProcessInstanceReport
org.camunda.bpm.engine Public API of the camunda BPM engine.

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 Deployments
RuntimeService: For starting and searching ProcessInstances
TaskService: Exposes operations to manage human (standalone) Tasks, such as claiming, completing and assigning tasks
IdentityService: Used for managing Users, Groups and the relations between them
ManagementService: Exposes engine admin and maintenance operations, which have no relation to the runtime execution of business processes
HistoryService: Exposes information about ongoing and past process instances.
FormService: Access to form data and rendered forms for starting new process instances and completing tasks.
 
org.camunda.bpm.engine.history Classes related to the HistoryService
org.camunda.bpm.engine.impl 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 HistoricProcessInstanceReport
 HistoricProcessInstanceReport HistoryService.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 HistoricProcessInstanceReport
 HistoricProcessInstanceReport HistoricProcessInstanceReport.processDefinitionIdIn(String... processDefinitionIds)
          Only takes historic process instances into account for the given process definition ids.
 HistoricProcessInstanceReport HistoricProcessInstanceReport.processDefinitionKeyIn(String... processDefinitionKeys)
          Only takes historic process instances into account for the given process definition keys.
 HistoricProcessInstanceReport HistoricProcessInstanceReport.startedAfter(Date startedAfter)
          Only takes historic process instances into account that were started after the given date.
 HistoricProcessInstanceReport 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 HistoricProcessInstanceReport
 class HistoricProcessInstanceReportImpl
           
 

Methods in org.camunda.bpm.engine.impl that return HistoricProcessInstanceReport
 HistoricProcessInstanceReport HistoryServiceImpl.createHistoricProcessInstanceReport()
           
 HistoricProcessInstanceReport HistoricProcessInstanceReportImpl.processDefinitionIdIn(String... processDefinitionIds)
           
 HistoricProcessInstanceReport HistoricProcessInstanceReportImpl.processDefinitionKeyIn(String... processDefinitionKeys)
           
 HistoricProcessInstanceReport HistoricProcessInstanceReportImpl.startedAfter(Date startedAfter)
           
 HistoricProcessInstanceReport HistoricProcessInstanceReportImpl.startedBefore(Date startedBefore)
           
 



Copyright © 2016 camunda services GmbH. All rights reserved.