Current Release Notes (Taskana)

Next Version:

v5.7.0

Breaking

• TSK-1957: This TASKANA version requires a database schema update (which is backwards compatible)

• TSK-1965: until now the REST endpoint to delete a Task: DELETE Request on /api/v1/tasks/{taskId} has used the forceDelete method of the TaskService. This is now split into two endpoints:

  • DELETE Request on /api/v1/tasks/{taskId} to delete a Task normally

  • DELETE Request on /api/v1/tasks/{taskId}/force to force delete a Task

Database Schema Update

• TSK-1957: The new TASKANA version requieres a schema update (which is backwards compatible).

Major Version Updates

Deprecations

• TSK-1957: WorkbasketQuery#accessIdsHavePermission(workbasketPermission, String...) --> WorkbasketQuery#accessIdsHavePermissions(List<WorkbasketPermission>, String...) (old method will be removed in next release)

• TSK-1957: WorkbasketQuery#callerHasPermission(WorkbasketPermission) --> WorkbasketQuery#callerHasPermissions(WorkbasketPermission...) (old method will be removed in next release)

New

• TSK-1957: UserService#getUser() now sets the new attribute domains dynamically. It is aggregated by specific permissions for workbaskets which is configured by a new property: taskana.user.minimalPermissionsToAssignDomains.
  If this property is not set the domains attribute will not be set.

• TSK-1957: user model now has 'groups' attribute, which are included in the domain aggregation when getting a user

• TSK-1965: Added the following REST endpoints:

  • /api/v1/tasks/{taskId}/claim/force

  • /api/v1/tasks/{taskId}/complete/force

  • /api/v1/tasks/{taskId}/terminate

  • /api/v1/tasks/{taskId}/set-read

  • /api/v1/tasks/{taskId}/delete/force

Improvements

• TSK-1967: setting the owner of a Task now works when the TaskState is READY_FOR_REVIEW