Uses of Interface
org.flowable.common.engine.api.Engine
Packages that use Engine
Package
Description
Public API of the Flowable 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 Deployment
s.RuntimeService
: For starting and searching ProcessInstance
s.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.-
Uses of Engine in org.flowable.common.engine.api.engine
Methods in org.flowable.common.engine.api.engine with parameters of type EngineModifier and TypeMethodDescriptionvoid
EngineLifecycleListener.onEngineBuilt
(Engine engine) Called right after the engine has been built.void
EngineLifecycleListener.onEngineClosed
(Engine engine) Called right after the engine has been closed. -
Uses of Engine in org.flowable.engine
Subinterfaces of Engine in org.flowable.engineModifier and TypeInterfaceDescriptioninterface
Provides access to all the services that expose the BPM and workflow operations.Methods in org.flowable.engine with parameters of type EngineModifier and TypeMethodDescriptiondefault void
ProcessEngineLifecycleListener.onEngineBuilt
(Engine engine) default void
ProcessEngineLifecycleListener.onEngineClosed
(Engine engine)