Uses of Interface
org.camunda.bpm.engine.history.CleanableHistoricCaseInstanceReport
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 CleanableHistoricCaseInstanceReport in org.camunda.bpm.engine
Modifier and TypeMethodDescriptionHistoryService.createCleanableHistoricCaseInstanceReport()
Creates a new programmatic query to create a cleanable historic case instance report. -
Uses of CleanableHistoricCaseInstanceReport in org.camunda.bpm.engine.history
Modifier and TypeMethodDescriptionCleanableHistoricCaseInstanceReport.caseDefinitionIdIn
(String... caseDefinitionIds) Only takes historic case instances into account for the given case definition ids.CleanableHistoricCaseInstanceReport.caseDefinitionKeyIn
(String... caseDefinitionKeys) Only takes historic case instances into account for the given case definition keys.CleanableHistoricCaseInstanceReport.compact()
Only selects historic case instances which have more than zero finished instances.CleanableHistoricCaseInstanceReport.orderByFinished()
Order by finished case instances amount (needs to be followed byQuery.asc()
orQuery.desc()
).CleanableHistoricCaseInstanceReport.tenantIdIn
(String... tenantIds) Only select historic case instances with one of the given tenant ids.CleanableHistoricCaseInstanceReport.withoutTenantId()
Only selects historic case instances which have no tenant id. -
Uses of CleanableHistoricCaseInstanceReport in org.camunda.bpm.engine.impl
Modifier and TypeMethodDescriptionCleanableHistoricCaseInstanceReportImpl.caseDefinitionIdIn
(String... caseDefinitionIds) CleanableHistoricCaseInstanceReportImpl.caseDefinitionKeyIn
(String... caseDefinitionKeys) CleanableHistoricCaseInstanceReportImpl.compact()
HistoryServiceImpl.createCleanableHistoricCaseInstanceReport()
CleanableHistoricCaseInstanceReportImpl.orderByFinished()
CleanableHistoricCaseInstanceReportImpl.tenantIdIn
(String... tenantIds) CleanableHistoricCaseInstanceReportImpl.withoutTenantId()
-
Uses of CleanableHistoricCaseInstanceReport in org.camunda.bpm.engine.rest.dto.history
Modifier and TypeMethodDescriptionprotected CleanableHistoricCaseInstanceReport
CleanableHistoricCaseInstanceReportDto.createNewQuery
(ProcessEngine engine) Modifier and TypeMethodDescriptionprotected void
CleanableHistoricCaseInstanceReportDto.applyFilters
(CleanableHistoricCaseInstanceReport query) protected void
CleanableHistoricCaseInstanceReportDto.applySortBy
(CleanableHistoricCaseInstanceReport query, String sortBy, Map<String, Object> parameters, ProcessEngine engine)