Uses of Interface
Packages that use HistoryService 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. org.flowable.engine.testHelper classes for testing processes.
Uses of HistoryService in org.flowable.engine
Methods in org.flowable.engine that return HistoryService Modifier and Type Method Description
Uses of HistoryService in org.flowable.engine.impl
Classes in org.flowable.engine.impl that implement HistoryService Modifier and Type Class Description
Fields in org.flowable.engine.impl declared as HistoryService Modifier and Type Field Description
Methods in org.flowable.engine.impl that return HistoryService Modifier and Type Method Description
Uses of HistoryService in org.flowable.engine.test
Fields in org.flowable.engine.test declared as HistoryService Modifier and Type Field Description
Methods in org.flowable.engine.test that return HistoryService Modifier and Type Method Description
Methods in org.flowable.engine.test with parameters of type HistoryService Modifier and Type Method Description