Uses of Interface
Packages that use NativeHistoricDecisionInstanceQuery Package Description org.camunda.bpm.enginePublic API of the Camunda Platform engine.
Typical usage of the API starts by the creation of a
ProcessEngineConfiguration(typically based on a configuration file), from which a
ProcessEnginecan be obtained.
Through the services obtained from such a
ProcessEngine, BPM and workflow operation can be executed:
RuntimeService: For starting and searching
TaskService: Exposes operations to manage human (standalone)
Tasks, such as claiming, completing and assigning tasks
IdentityService: Used for managing
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.implAPI implementation classes, which shouldn't directly be used by end-users.
Methods in org.camunda.bpm.engine that return NativeHistoricDecisionInstanceQuery Modifier and Type Method Description
createNativeHistoricDecisionInstanceQuery()creates a native query to search for
HistoricDecisionInstances via SQL
Classes in org.camunda.bpm.engine.impl that implement NativeHistoricDecisionInstanceQuery Modifier and Type Class Description
Methods in org.camunda.bpm.engine.impl that return NativeHistoricDecisionInstanceQuery Modifier and Type Method Description