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

Packages that use HistoricActivityStatisticsQuery
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 HistoricActivityStatisticsQuery in org.camunda.bpm.engine
 

Methods in org.camunda.bpm.engine that return HistoricActivityStatisticsQuery
 HistoricActivityStatisticsQuery HistoryService.createHistoricActivityStatisticsQuery(String processDefinitionId)
          Query for the number of historic activity instances aggregated by activities of a single process definition.
 

Uses of HistoricActivityStatisticsQuery in org.camunda.bpm.engine.history
 

Methods in org.camunda.bpm.engine.history that return HistoricActivityStatisticsQuery
 HistoricActivityStatisticsQuery HistoricActivityStatisticsQuery.includeCanceled()
          Include an aggregation of canceled instances in the result.
 HistoricActivityStatisticsQuery HistoricActivityStatisticsQuery.includeCompleteScope()
          Include an aggregation of instances, which complete a scope (ie.
 HistoricActivityStatisticsQuery HistoricActivityStatisticsQuery.includeFinished()
          Include an aggregation of finished instances in the result.
 HistoricActivityStatisticsQuery HistoricActivityStatisticsQuery.orderByActivityId()
          Order by activity id (needs to be followed by Query.asc() or Query.desc()).
 

Uses of HistoricActivityStatisticsQuery in org.camunda.bpm.engine.impl
 

Classes in org.camunda.bpm.engine.impl that implement HistoricActivityStatisticsQuery
 class HistoricActivityStatisticsQueryImpl
           
 

Methods in org.camunda.bpm.engine.impl that return HistoricActivityStatisticsQuery
 HistoricActivityStatisticsQuery HistoryServiceImpl.createHistoricActivityStatisticsQuery(String processDefinitionId)
           
 HistoricActivityStatisticsQuery HistoricActivityStatisticsQueryImpl.includeCanceled()
           
 HistoricActivityStatisticsQuery HistoricActivityStatisticsQueryImpl.includeCompleteScope()
           
 HistoricActivityStatisticsQuery HistoricActivityStatisticsQueryImpl.includeFinished()
           
 HistoricActivityStatisticsQuery HistoricActivityStatisticsQueryImpl.orderByActivityId()
           
 



Copyright © 2017 camunda services GmbH. All rights reserved.