Skip to content

Commit

Permalink
docs(migration): add information about set variables async api changes
Browse files Browse the repository at this point in the history
  • Loading branch information
joaquinfelici committed Nov 21, 2024
1 parent df10e1c commit 923ebfa
Show file tree
Hide file tree
Showing 2 changed files with 36 additions and 0 deletions.
28 changes: 28 additions & 0 deletions content/update/minor/722-to-723/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---

title: "Update from 7.22 to 7.23"
weight: 1
layout: "single"

menu:
main:
name: "7.22 to 7.23"
identifier: "migration-guide-723"
parent: "migration-guide-minor"
pre: "Update from `7.22.x` to `7.23.0`."

---

This document guides you through the update from Camunda `7.22.x` to `7.23.0` and covers the following use cases:

1. For developers: [Set Variables Async API](#Set Variables Async API)

This guide covers mandatory migration steps and optional considerations for the initial configuration of new functionality included in Camunda 7.23.

# Set Variables Async API

Before version 7.22.1, the Set Variables Async API failed whenever at least one of the process instances did not exist.

Starting with version 7.22.1, the behavior has changed: if any of the process instances was deleted or completed, the call will still succeed. As a consequence, the Set Variables Batch Operation will also succeed in this case.

Please note that this does not apply to the Sync API, which keeps its behavior and fails if the process instance does not exist.
8 changes: 8 additions & 0 deletions content/update/patch-level.md
Original file line number Diff line number Diff line change
Expand Up @@ -530,6 +530,14 @@ With this patch release, we lifted this limitation by opting for a different sol

[process-instance-modification]: {{< ref "/webapps/cockpit/bpmn/process-instance-modification.md#perform-a-batch-modification" >}}

### Set Variables Async API

Before version 7.22.1, the Set Variables Async API failed whenever at least one of the process instances did not exist.

Starting with version 7.22.1, the behavior has changed: if any of the process instances was deleted or completed, the call will still succeed. As a consequence, the Set Variables Batch Operation will also succeed in this case.

Please note that this does not apply to the Sync API, which keeps its behavior and fails if the process instance does not exist.

# Full Distribution

This section is applicable if you installed the [Full Distribution]({{< ref "/introduction/downloading-camunda.md#full-distribution" >}}) with a **shared process engine**. In this case you need to update the libraries and applications installed inside the application server.
Expand Down

0 comments on commit 923ebfa

Please sign in to comment.