Uses of Class
org.flowable.engine.impl.persistence.AbstractManager

Packages that use AbstractManager

Package	Description
org.flowable.engine	Public API of the Flowable 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 administration and maintenance operations, which have no relation to the runtime exection 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.flowable.engine.impl.history
org.flowable.engine.impl.history.async

Uses of AbstractManager in org.flowable.engine

Subclasses of AbstractManager in org.flowable.engine

Modifier and Type	Class	Description
class	DefaultCandidateManager

Uses of AbstractManager in org.flowable.engine.impl.history

Subclasses of AbstractManager in org.flowable.engine.impl.history

Modifier and Type	Class	Description
class	AbstractHistoryManager
class	DefaultHistoryManager	Manager class that centralises recording of all history-related operations that are originated from inside the engine.

Uses of AbstractManager in org.flowable.engine.impl.history.async

Subclasses of AbstractManager in org.flowable.engine.impl.history.async

Modifier and Type	Class	Description
class	AbstractAsyncHistoryManager
class	AsyncHistoryManager