Uses of Interface
Packages that use Account 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. org.camunda.bpm.engine.impl.cmd org.camunda.bpm.engine.impl.persistence.entity
Uses of Account in org.camunda.bpm.engine
Methods in org.camunda.bpm.engine that return Account Modifier and Type Method Description
getUserAccount(java.lang.String userId, java.lang.String userPassword, java.lang.String accountName)Deprecated.
Uses of Account in org.camunda.bpm.engine.impl
Methods in org.camunda.bpm.engine.impl that return Account Modifier and Type Method Description
getUserAccount(java.lang.String userId, java.lang.String userPassword, java.lang.String accountName)
Uses of Account in org.camunda.bpm.engine.impl.cmd
Methods in org.camunda.bpm.engine.impl.cmd that return Account Modifier and Type Method Description
Classes in org.camunda.bpm.engine.impl.persistence.entity that implement Account Modifier and Type Class Description