Uses of Class
org.camunda.bpm.engine.impl.HistoryLevelSetupCommand

Packages that use HistoryLevelSetupCommand
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.
 
 

Uses of HistoryLevelSetupCommand in org.camunda.bpm.engine
 

Fields in org.camunda.bpm.engine declared as HistoryLevelSetupCommand
protected  HistoryLevelSetupCommand ProcessEngineConfiguration.historyLevelCommand
           
 

Methods in org.camunda.bpm.engine that return HistoryLevelSetupCommand
 HistoryLevelSetupCommand ProcessEngineConfiguration.getHistoryLevelCommand()
           
 

Methods in org.camunda.bpm.engine with parameters of type HistoryLevelSetupCommand
 void ProcessEngineConfiguration.setHistoryLevelCommand(HistoryLevelSetupCommand historyLevelCommand)
           
 



Copyright © 2017 camunda services GmbH. All rights reserved.