Uses of Package
org.flowable.validation
Packages that use org.flowable.validation
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 Deployments.RuntimeService: For starting and searching ProcessInstances.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.
-
Classes in org.flowable.validation used by org.flowable.engine
-
Classes in org.flowable.validation used by org.flowable.engine.impl
-
Classes in org.flowable.validation used by org.flowable.engine.impl.cfgClassDescriptionValidates a process definition against the rules of the Flowable engine to be executable
-
Classes in org.flowable.validation used by org.flowable.engine.impl.cmd
-
Classes in org.flowable.validation used by org.flowable.validationClassDescriptionValidates a process definition against the rules of the Flowable engine to be executable
-
Classes in org.flowable.validation used by org.flowable.validation.validator
-
Classes in org.flowable.validation used by org.flowable.validation.validator.impl