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