| Package | Description |
|---|---|
| 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 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. |
| 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.
|
| Modifier and Type | Method and Description |
|---|---|
CleanableHistoricBatchReport |
HistoryService.createCleanableHistoricBatchReport()
Creates a new programmatic query to create a cleanable historic batch report.
|
| Modifier and Type | Method and Description |
|---|---|
CleanableHistoricBatchReport |
CleanableHistoricBatchReport.orderByFinishedBatchOperation()
Order by finished batch operations amount (needs to be followed by
Query.asc() or Query.desc()). |
| Modifier and Type | Class and Description |
|---|---|
class |
CleanableHistoricBatchReportImpl |
| Modifier and Type | Method and Description |
|---|---|
CleanableHistoricBatchReport |
HistoryServiceImpl.createCleanableHistoricBatchReport() |
CleanableHistoricBatchReport |
CleanableHistoricBatchReportImpl.orderByFinishedBatchOperation() |
Copyright © 2018 camunda services GmbH. All rights reserved.