Uses of Interface
org.flowable.engine.RuntimeService
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.API implementation classes, which shouldn't directly be used by end-users.
Helper classes for testing processes.
-
Uses of RuntimeService in org.flowable.engine
Modifier and TypeMethodDescriptionProcessEngine.getRuntimeService()
abstract RuntimeService
ProcessEngineConfiguration.getRuntimeService()
-
Uses of RuntimeService in org.flowable.engine.impl
-
Uses of RuntimeService in org.flowable.engine.test
Modifier and TypeFieldDescriptionprotected RuntimeService
FlowableRule.runtimeService
protected RuntimeService
FlowableTestCase.runtimeService
Modifier and TypeMethodDescriptionvoid
FlowableRule.setRuntimeService
(RuntimeService runtimeService)