Uses of Package
org.flowable.engine.delegate
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.Interfaces used to include Java code in a process as the behavior of an activity
or as a listener to process events with
JavaDelegate
s.API implementation classes, which shouldn't directly be used by end-users.
-
-
ClassDescriptionSpecial exception that can be used to throw a BPMN Error from
JavaDelegate
s and expressions.Execution used inJavaDelegate
s andExecutionListener
s. -
-
ClassDescriptionCallback interface to be notified of execution events like starting a process instance, ending an activity instance or taking a transition.Execution used in
JavaDelegate
s andExecutionListener
s.Convenience class which always uses theAsyncTaskInvoker
to execute the async data.Convenience class that should be used when a Java delegation in a BPMN 2.0 process is required (for example, to call custom business logic). -
-
-
-
-