/v1/juel
in the modeling back end. This feature uses the JuelExpressionResolver and needs authentication. The endpoint receives two inputs variables:expression
: String containing the JUEL expression.variables
: Map with the names and values of the variables used in the expression (Expression context). Example: org.activiti.cloud:activiti-cloud-starter-juel:${activiti-cloud.version}
@EnableActivitiJuel
annotation${assignee}
that is available out of the box.GET /query/v1/tasks/{taskId}
returns one extra property (permissions
) that identifies which are the permissions the current user has on the given task:VIEW
: the user can view the taskCLAIM
: the user can assign the task to himselfRELEASE
: the user can release the task that it's currently assigned to himUPDATE
: the user can update information related to the task7.x.y
was used for internal releases (created every time a new commit is merged on the develop
branch). For instance, 7.1.364
is an internal release. In addition to the internal releases, intermediate milestones were published on regular bases, (e.g. 7.1.0-M17
), and eventually, a general availability (GA) version would be released (e.g. 7.1.0-GA
). -alpha
(7.2.0-alpha.1
, 7.2.0-alpha.2
). In addition to that, milestones releases will no longer be published and will be replaced by a new minor version that will be released more often. It has also been decided that the version 7.1.0-GA
will be skipped and the project will go straight to the version 7.2.0
.GET /query/v1/task/{taskId}
has changed allowing a user to retrieve by id all the tasks where he is the initiator of the process or he is involved in at least 1 task of the process (he is a candidate, the assignee, in a candidate group). Previously only the tasks for which the user was the assignee or a candidate were returned. GET /query/v1/process-instance/{process-id}/tasks
has changed allowing a user to retrieve only the tasks where he is the initiator of the process or he is involved in at least 1 task of the process (he is a candidate, the assignee, in a candidate group). Previously all the tasks were returned.GET query/admin/v1/process-instance/{process-id}/tasks
allowing an admin to retrieve all the tasks in the scope of a given process instance.GET /query/v1/process-instances
will return only the instances started by the current user. Use the admin API in the case where all the process instances should be returned.GET /query/v1/process-instances/{processInstanceId}
. Only the initiator and users involved in the process will be able to to retrieve the process by id.POST /rb/v1/process-instances/{processInstanceId}/suspend.
Only the initiator can suspend the process.POST /rb/v1/process-instances/{processInstanceId}/resume.
Only the initiator can resume the process.PUT /rb/v1/process-instances/{processInstanceId}
. Only the initiator can update the properties of a process instance.GET
, POST /rb/v1/process-instances/{processInstanceId}/variables
. Only the initiator can retrieve and update process variables.GET /rb/admin/v1/process-instances/{processInstanceId}/variables
to list all the variables of a process instance as admin
.