You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/components/modeler/web-modeler/process-application-versioning.md
+4
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,10 @@ title: Process application versioning
4
4
description: Process applications allow you to deploy multiple related files together in a single bundle.
5
5
---
6
6
7
+
:::note
8
+
With 8.7, "milestone" has been renamed to "version". To learn more about this change, see [the related announcement](/reference/announcements/870.md##web-modeler-milestones-renamed-to-versions).
9
+
:::
10
+
7
11
Although you cannot version a process application itself, you can use [bulk version creation](versions.md#bulk-version-creation) and version tags to save a single snapshot of all the process application files in one action, instead of having to create separate versions for every file.
8
12
9
13
- When you create a version in any process application file, a version is also created with the same name (version tag) for all files currently available in the process application.
With 8.7, "milestone" has been renamed to "version". To learn more about this change, see [the related announcement](/reference/announcements/870.md##web-modeler-milestones-renamed-to-versions).
11
+
:::
12
+
9
13
You can create a version at any time to save a snapshot of your BPMN or DMN diagram.
10
14
11
15
You can restore a version to revert to a previous snapshot of your diagram, for example if you make a mistake while modeling. You can also compare two versions to see the differences between them.
-[Milestones renamed to versions {#web-modeler-milestones-renamed-to-versions}](#milestones-renamed-to-versions-web-modeler-milestones-renamed-to-versions)
24
+
-[Southeast Asia region for SaaS customers SaaS](#southeast-asia-region-for-saas-customers-saas)
With this version, we ship a breaking change to how Web Modeler **Deploy diagram** modals work. Clusters must now be proactively [configured](/docs/self-managed/modeler/web-modeler/configuration/configuration.md#clusters) to be able to deploy from Web Modeler.
27
31
@@ -31,6 +35,17 @@ With this version, we ship a breaking change to how Web Modeler **Deploy diagram
31
35
- In 8.7, you can no longer configure cluster details on the **Deploy diagram** modal. You must [configure the cluster](/docs/self-managed/modeler/web-modeler/configuration/configuration.md#clusters) to be able to deploy from this modal.
32
36
- Note that you must also be assigned the `Zeebe`[Identity role](/docs/self-managed/identity/user-guide/roles/add-assign-role.md) to be able to deploy.
33
37
38
+
### Milestones renamed to versions {#web-modeler-milestones-renamed-to-versions}
39
+
40
+
The term "milestones" has been renamed to ["versions"](/components/modeler/web-modeler/versions.md) in Web Modeler for clarity and consistency with other Camunda 8 components. The renaming is implemented across the Web Modeler user interface and the API.
41
+
42
+
In [the API](/apis-tools/web-modeler-api/index.md), new endpoints starting with `/api/v1/versions` have been introduced, while the previous `/api/v1/milestones` endpoints are now deprecated.
43
+
Further details can be found in [Web Modeler's OpenAPI documentation](https://modeler.camunda.io/swagger-ui/index.html).
44
+
45
+
:::note
46
+
This is a nominal update and the functionality of versions and milestones is equivalent.
47
+
:::
48
+
34
49
## Southeast Asia region for SaaS customers <spanclass="badge badge--long"title="This feature affects SaaS">SaaS</span>
35
50
36
51
SaaS customers can now create orchestration clusters in the [Singapore (asia-southeast1) region](/reference/regions.md), ensuring lower latency and improved processing speed for organizations operating in southeast Asian countries.
0 commit comments