Uses of Class
org.camunda.bpm.engine.BadUserRequestException

Packages that use BadUserRequestException

Package	Description
org.camunda.bpm.engine	Public API of the camunda BPM engine. 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 admin and maintenance operations, which have no relation to the runtime execution 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.camunda.bpm.engine.exception

Uses of BadUserRequestException in org.camunda.bpm.engine

Subclasses of BadUserRequestException in org.camunda.bpm.engine

Modifier and Type	Class and Description
class	SuspendedEntityInteractionException This exception is thrown, if an operation that requires a non-suspended entity (execution, task, process definition) is executed on a suspended one.

Uses of BadUserRequestException in org.camunda.bpm.engine.exception

Subclasses of BadUserRequestException in org.camunda.bpm.engine.exception

Modifier and Type	Class and Description
class	NotAllowedException This exception is thrown, if an operation is not allowed to be executed.
class	NotFoundException This exception is thrown, if an entity (case execution, case definition) is not found.
class	NotValidException This exception is thrown, if a given value is not valid.