Uses of Interface
Packages that use Model Package Description org.flowable.enginePublic 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
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 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.implAPI implementation classes, which shouldn't directly be used by end-users.
Uses of Model in org.flowable.engine
Methods in org.flowable.engine that return Model Modifier and Type Method Description
getModel(String modelId)Returns the
newModel()Creates a new model.
Methods in org.flowable.engine with parameters of type Model Modifier and Type Method Description
saveModel(Model model)Saves the model.
Uses of Model in org.flowable.engine.impl
Methods in org.flowable.engine.impl that return Model Modifier and Type Method Description
Methods in org.flowable.engine.impl that return types with arguments of type Model Modifier and Type Method Description
executeList(org.flowable.common.engine.impl.interceptor.CommandContext commandContext, Map<String,Object> parameterMap)
Methods in org.flowable.engine.impl with parameters of type Model Modifier and Type Method Description