| 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 DeploymentsRuntimeService:
    For starting and searching ProcessInstancesTaskService:
    Exposes operations to manage human (standalone) Tasks,
    such as claiming, completing and assigning tasksIdentityService:
    Used for managing Users,
    Groups and the relations between themManagementService:
    Exposes engine admin and maintenance operations,
    which have no relation to the runtime execution of business processesHistoryService:
    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.impl | 
 API implementation classes, which shouldn't directly be used by end-users. 
 | 
| org.camunda.bpm.engine.impl.cmd | |
| org.camunda.bpm.engine.impl.persistence.entity | 
| Modifier and Type | Method and Description | 
|---|---|
List<Event> | 
TaskService.getTaskEvents(String taskId)
Deprecated. 
 
This method has been deprecated as of camunda BPM 7.1. It has been replaced with
 the operation log. See  
UserOperationLogEntry and UserOperationLogQuery. | 
| Modifier and Type | Method and Description | 
|---|---|
List<Event> | 
TaskServiceImpl.getTaskEvents(String taskId)  | 
| Modifier and Type | Method and Description | 
|---|---|
List<Event> | 
GetTaskEventsCmd.execute(CommandContext commandContext)  | 
| Modifier and Type | Class and Description | 
|---|---|
class  | 
CommentEntity  | 
| Modifier and Type | Method and Description | 
|---|---|
List<Event> | 
CommentManager.findEventsByTaskId(String taskId)  | 
Copyright © 2019. All rights reserved.