Uses of Class
org.camunda.bpm.engine.impl.HistoryLevelSetupCommand
Packages that use HistoryLevelSetupCommand
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 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.- 
Uses of HistoryLevelSetupCommand in org.camunda.bpm.engineFields in org.camunda.bpm.engine declared as HistoryLevelSetupCommandModifier and TypeFieldDescriptionprotected HistoryLevelSetupCommandProcessEngineConfiguration.historyLevelCommandMethods in org.camunda.bpm.engine that return HistoryLevelSetupCommandMethods in org.camunda.bpm.engine with parameters of type HistoryLevelSetupCommandModifier and TypeMethodDescriptionvoidProcessEngineConfiguration.setHistoryLevelCommand(HistoryLevelSetupCommand historyLevelCommand)