Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

intro changes for smooth migration zeebe user tasks next #4723

Open
wants to merge 15 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions api/tasklist/tasklist-openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -725,7 +725,7 @@ components:
- JOB_WORKER
- ZEEBE_USER_TASK
priority:
description: Rules to filter out tasks by their priority. Applicable only for Zeebe user tasks.
description: Rules to filter out tasks by their priority. Applicable only for job worker-based user tasks managed by Camunda.
type: object
properties:
eq:
Expand Down Expand Up @@ -859,7 +859,7 @@ components:
- JOB_WORKER
- ZEEBE_USER_TASK
priority:
description: The priority of a user task. The higher the value the higher the priority. Applicable only for Zeebe user tasks.
description: The priority of a user task. The higher the value the higher the priority. Applicable only for job worker-based user tasks managed by Camunda.
type: integer
minimum: 0
maximum: 100
Expand Down Expand Up @@ -957,7 +957,7 @@ components:
- JOB_WORKER
- ZEEBE_USER_TASK
priority:
description: The priority of a user task. The higher the value the higher the priority. Applicable only for Zeebe user tasks.
description: The priority of a user task. The higher the value the higher the priority. Applicable only for job worker-based user tasks managed by Camunda.
type: integer
minimum: 0
maximum: 100
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: camunda-api-rest-overview
title: "Overview"
description: "Interact with Camunda 8 clusters. Activate jobs and run user task state operations for Zeebe user tasks."
description: "Interact with Camunda 8 clusters. Activate jobs and run user task state operations for Camunda user tasks."
---

The Camunda 8 REST API is a REST API designed to interact with a Camunda 8 cluster.
Expand All @@ -10,6 +10,10 @@ The Camunda 8 REST API is a REST API designed to interact with a Camunda 8 clust
Ensure you [authenticate](./camunda-api-rest-authentication.md) before accessing the Camunda 8 REST API.
:::

:::note
The Camunda 8 REST API only supports user tasks managed by Camunda (formerly known as [Zeebe user tasks](/apis-tools/migration-manuals/migrate-to-camunda-user-tasks.md), which may still appear as such in your XML content).
:::

## Context paths

For SaaS: `https://${REGION}.zeebe.camunda.io:443/${CLUSTER_ID}/v2/`, and for Self-Managed installations: `http://localhost:8080/v2/`.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -76,15 +76,23 @@ Our best practices, as implemented in Tasklist, are as follows:

Make sure that you create your own validation logic that matches your use case.

## Implement the life cycle with the task API
## Implement task life cycle with the Camunda 8 API

To implement task life cycle operations with the task API, call the respective endpoints:
Use the Camunda 8 REST API to implement task life cycle operations. You can find the API specifications [here](/apis-tools/camunda-api-rest/camunda-api-rest-overview.md).

Task life cycle events can be tracked via the following API endpoints:

- [`POST /user-tasks/:userTaskKey/assignment`](/apis-tools/camunda-api-rest/specifications/assign-user-task.api.mdx) or [`DELETE /user-tasks/:userTaskKey/assignee`](/apis-tools/camunda-api-rest/specifications/unassign-user-task.api.mdx) to change task assignment.
- [`PATCH /user-tasks/:userTaskKey`](/apis-tools/camunda-api-rest/specifications/update-user-task.api.mdx) to update a task.
- [`POST /user-tasks/:userTaskKey/completion`](/apis-tools/camunda-api-rest/specifications/complete-user-task.api.mdx) to complete a task.

All these endpoints (except `DELETE`) allow you to send a custom `action` attribute via the payload. The `action` attribute carries any arbitrary string and can be used to track any life cycle event, including those mentioned above.
- Assign user task:
- [`POST /user-tasks/:userTaskKey/assignment`](/apis-tools/camunda-api-rest/specifications/assign-user-task.api.mdx)
- [`DELETE /user-tasks/:userTaskKey/assignee`](/apis-tools/camunda-api-rest/specifications/unassign-user-task.api.mdx) is used to unassing a user task.
- Update user task:
- [`PATCH /user-tasks/:taskKey`](/apis-tools/camunda-api-rest/specifications/update-user-task.api.mdx)
- Complete user task:
- [`POST /user-tasks/:taskKey/completion`](/apis-tools/camunda-api-rest/specifications/complete-user-task.api.mdx)

#### [`POST /user-tasks/:userTaskKey/assignment`](/apis-tools/camunda-api-rest/specifications/assign-user-task.api.mdx)

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,10 @@ description: "Understand and decide on the architecture of your task application

A typical task application architecture consists of a task application frontend, a backend-for-frontend, and one or more data sources or services that contain business data relevant for the application users to perform their work. The backend implements Camunda Zeebe and Tasklist clients to retrieve and interact with tasks via Camunda APIs. For historical process instance data, Operate is also required.

Depending on the user task implementation type (job worker-based vs Zeebe user task) you use in your processes, you need to run either the Tasklist or Zeebe client to run operations on task. Task, form, and variable retrieval happens via the API. Learn more about the differences of the task implementation types in the [migration guide for Zeebe user tasks](/apis-tools/migration-manuals/migrate-to-zeebe-user-tasks.md).
Depending on the user task implementation type (job worker-based vs Camunda user task) you use in your processes, you need to run either the Tasklist or Zeebe client to run operations on tasks. Task, form, and variable retrieval happens via the API. Learn more about the differences of the task implementation types in the [migration guide for Camunda user tasks](/apis-tools/migration-manuals/migrate-to-camunda-user-tasks.md).

:::tip
Starting a new project? Use Zeebe user tasks to simplify your implementation.
Starting a new project? Use Camunda user tasks to simplify your implementation.
:::

Click on any element of this diagram to jump to the documentation page for the respective component:
Expand Down Expand Up @@ -72,14 +72,14 @@ style Tasklist stroke:#10c95d,color:#000

click Forms "../../forms/introduction-to-forms"
click Rest "../../../tasklist-api-rest/tasklist-api-rest-overview"
click Job "../../../migration-manuals/migrate-to-zeebe-user-tasks"
click ZeebeTasks "../../../migration-manuals/migrate-to-zeebe-user-tasks"
click Job "../../../migration-manuals/migrate-to-camunda-user-tasks"
click ZeebeTasks "../../../migration-manuals/migrate-to-camunda-user-tasks"
click ZeebeRest "../../../zeebe-api-rest/zeebe-api-rest-overview"
```

Follow these resources to learn more about the individual components:

- Learn how to use the [Camunda 8 API](/apis-tools/camunda-api-rest/specifications/assign-user-task.api.mdx) for task, variable, and form retrieval, and to run operations on Zeebe user tasks.
- Familiarize yourself with the [Tasklist API](/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md) to run operations on job worker-based user tasks.
- Learn how to use the [Camunda 8 API](/apis-tools/camunda-api-rest/specifications/assign-user-task.api.mdx) for task, variable, and form retrieval, and to run operations on Camunda user tasks.
- Familiarize yourself with the [Tasklist API](/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md) to run operations on Job worker-based user tasks.
- Understand how to design, embed, and customize [forms](/apis-tools/frontend-development/03-forms/01-introduction-to-forms.md).
- Understand how this architecture fits into the overall Camunda architecture with the [Java greenfield stack](/components/best-practices/architecture/deciding-about-your-stack.md).
2 changes: 1 addition & 1 deletion docs/apis-tools/java-client/zeebe-process-test.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ processes. It will start a lightweight in-memory Zeebe engine and provide you wi
verify your process behaves as expected.

:::note
As of 8.5.0, Zeebe Process Test does not support the new REST API and related features (e.g. Zeebe user tasks).
As of 8.5.0, Zeebe Process Test does not support the new REST API and related features (for example, Camunda user tasks).
:::

## Prerequisites
Expand Down
Loading
Loading