Package | Description |
---|---|
org.flowable.engine |
Public API of the Activiti engine.
Typical usage of the API starts by the creation of a org.activiti.engine.ProcessEngineConfiguration
(typically based on a configuration file), from which a org.activiti.engine.ProcessEngine can be obtained.Through the services obtained from such a org.activiti.engine.ProcessEngine , BPM and workflow operation
can be executed:org.activiti.engine.RepositoryService : Manages org.activiti.engine.repository.Deployment s org.activiti.engine.RuntimeService : For starting and searching org.activiti.engine.runtime.ProcessInstance s org.activiti.engine.TaskService : Exposes operations to manage human (standalone) org.activiti.engine.task.Task s,
such as claiming, completing and assigning tasksorg.activiti.engine.IdentityService : Used for managing org.activiti.engine.identity.User s,
org.activiti.engine.identity.Group s and the relations between themorg.activiti.engine.ManagementService : Exposes engine admin and maintenance operations,
which have no relation to the runtime exection of business processesorg.activiti.engine.HistoryService : Exposes information about ongoing and past process instances.org.activiti.engine.FormService : Access to form data and rendered forms for starting new process instances and completing tasks. |
org.flowable.engine.impl.agenda | |
org.flowable.engine.runtime |
Classes related to the
org.activiti.engine.RuntimeService . |
Modifier and Type | Interface and Description |
---|---|
interface |
FlowableEngineAgenda
This interface exposes methods needed to manipulate the agenda implementation.
|
Modifier and Type | Class and Description |
---|---|
class |
DefaultFlowableEngineAgenda
For each API call (and thus
Command ) being executed, a new agenda instance is created. |
Modifier and Type | Method and Description |
---|---|
void |
Debugger.continueOperationExecution(CommandExecutor commandExecutor,
Agenda agenda)
Continue in the broken operation execution
|
Copyright © 2016 Flowable. All rights reserved.