merge in main

docs/apis-tools/operate-api/overview.md

@@ -10,6 +10,10 @@ Requests and responses are in JSON notation. Some objects have additional endpoi
 For example, `process-definitions` has an endpoint to get the process-definition as XML representation.
 In case of errors, Operate API returns an error object.
 
+:::note
+Work with this API in our [Postman collection](https://www.postman.com/camundateam/workspace/camunda-8-postman/collection/20317927-9d9314a2-4cff-40ab-90ea-98e28ca1f81c?action=share&creator=11465105), and check it out in [GitHub](https://github.com/camunda-community-hub/camunda-8-api-postman-collection).
+:::
+
 ## API documentation as Swagger
 
 A detailed API description is also available as Swagger UI at `https://${base-url}/swagger-ui/index.html`.

docs/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md

@@ -24,6 +24,10 @@ For SaaS: `https://${REGION}.tasklist.camunda.io:443/${CLUSTER_ID}/swagger-ui/in
 Find your region and cluster id under connection information in your client credentials.
 :::
 
+## API in Postman
+
+Work with this API in our [Postman collection](https://www.postman.com/camundateam/workspace/camunda-8-postman/collection/26079299-f0db0193-0557-4acd-8e94-ecdaeffbaa5d?action=share&creator=11465105), and check it out in [GitHub](https://github.com/camunda-community-hub/camunda-8-api-postman-collection).
+
 ## Endpoints
 
 | Endpoint (HTTP verb + URL path)                                                                                                                                 |                                                                       Description |

docs/apis-tools/tasklist-api/tasklist-api-overview.md

@@ -24,7 +24,9 @@ For SaaS: `https://${REGION}.tasklist.camunda.io:443/${CLUSTER_ID}/graphql`, and
 
 ## Obtaining the Tasklist schema
 
-To obtain the Tasklist GraphQL schema, send a request to the endpoint with a GraphQL introspection query as described [here](https://graphql.org/learn/introspection/), or use the [generated API documentation](/docs/apis-tools/tasklist-api/generated.md).
+To obtain the Tasklist GraphQL schema, check out the API collection in [GitHub](https://github.com/camunda-community-hub/camunda-8-api-postman-collection), which is fully functioning in [Postman](https://www.postman.com/camundateam/workspace/camunda-8-postman/collection/20317927-6394943f-b57c-4c04-acf9-391a8614103b?action=share&creator=11465105).
+
+Alternatively, send a request to the endpoint with a GraphQL introspection query as described [here](https://graphql.org/learn/introspection/), or use the [generated API documentation](/docs/apis-tools/tasklist-api/generated.md).
 
 There are also several [tools to explore GraphQL APIs](https://altair.sirmuel.design).
 

docs/apis-tools/web-modeler-api/index.md

@@ -18,6 +18,10 @@ A detailed API description is available as [OpenAPI](https://www.openapis.org/)
 for SaaS and at [http://localhost:8070/swagger-ui.html](http://localhost:8070/swagger-ui.html) for Self-Managed
 installations.
 
+## API in Postman
+
+Work with this API in our [Postman collection](https://www.postman.com/camundateam/workspace/camunda-8-postman/collection/26079299-0bb668f4-af6a-4ab0-88a3-c78b900125ed?action=share&creator=11465105).
+
 ## Limitations
 
 When using Web Modeler API:

docs/components/modeler/forms/configuration/forms-config-data-binding.md

@@ -66,3 +66,29 @@ If the above group has a path set to `user.info`, and if each field's key matche
   }
 }
 ```
+
+Group paths can be shared by multiple groups, as long as fields themselves do not conflict. However, depending on your use case, it might make sense for your visual and data structure to match.
+
+### Path configuration for dynamic lists
+
+While dynamic lists share similarities with groups in form structuring, they differ slightly in terms of path configuration. Since dynamic lists are bound to arrays, they cannot share paths with other dynamic lists or groups.
+
+In this instance, consider a dynamic list with the path `contacts`. Each entry in the list might contain fields like `name` and `phone`. The dynamic list directly outputs an array of objects under its own path, and the key of those child variables is used in the creation of the individual objects. The resulting data structure would resemble:
+
+```
+{
+  "contacts": [
+    {
+      "name": "John Doe",
+      "phone": "123-456-7890"
+    },
+    {
+      "name": "Jane Smith",
+      "phone": "098-765-4321"
+    }
+    // Additional objects for each item in the list
+  ]
+}
+```
+
+This structure is maintained when binding to input data as well. You can programmatically control how many list items are rendered from the number of elements in the array at the binding path, whether individual element data is provided or not.

docs/components/modeler/forms/form-element-library/forms-element-library-dynamiclist.md

@@ -0,0 +1,24 @@
+---
+id: forms-element-library-dynamiclist
+title: Dynamic list
+description: Learn about the dynamic list form element to dynamically manage a list of form elements.
+---
+
+The **dynamic list** element is designed to dynamically manage a list of form elements. It enables users to add or remove items from the list and is particularly useful in scenarios where the number of items in a list is not fixed.
+
+![Dynamic List Symbol](/img/form-icons/form-dynamiclist.svg)
+
+## Configurable properties
+
+- **Group label**: Label displayed on top of the dynamic list. Can either be an [expression](../../feel/language-guide/feel-expressions-introduction.md), plain text, or [templating syntax](../configuration/forms-config-templating-syntax.md).
+- **Path**: Assigns a path that maps its children into a data object, defined as a variable name or a dot separated variable accessor. See the [data binding docs](../configuration/forms-config-data-binding.md) for more details.
+- **Default number of items**: Specifies the default number of items rendered when no input data is provided.
+- **Allow add/delete items**: Enables users to add new items to or delete existing items from the list.
+- **Disable collapse**: Prevents items in the list from being collapsed.
+- **Number of non-collapsing items**: Defines the number of items in the list that will not collapse.
+- **Vertical alignment**: Determines the alignment of items in the list.
+- **Hide if**: [Expression](../../feel/language-guide/feel-expressions-introduction.md) to hide the dynamic list.
+
+## Usage
+
+The dynamic list element facilitates the management of data lists in forms. It is highly adaptable, with features like default item count, add/delete capabilities, and control over item collapse. It's the ideal component for scenarios where users need to input a variable number of items, such as adding multiple contacts or entries in a form.

docs/components/modeler/forms/form-element-library/forms-element-library-group.md

@@ -13,6 +13,7 @@ The group element serves as a container to group various form elements together.
 - **Group label**: Label displayed on top of the group. Can either be an [expression](../../feel/language-guide/feel-expressions-introduction.md), plain text, or [templating syntax](../configuration/forms-config-templating-syntax.md).
 - **Path**: Assigns a path that maps its children into a data object, may be left empty, defined as a variable name or a dot separated variable accessor. See the [data binding docs](../configuration/forms-config-data-binding.md) for more details.
 - **Show outline**: Can be toggled on and off to display a separating outline around the group
+- **Vertical alignment**: Determines the alignment of items in the list.
 - **Hide if**: [Expression](../../feel/language-guide/feel-expressions-introduction.md) to hide the group.
 - **Columns**: Space the field will use inside its row. **Auto** means it will automatically adjust to available space in the row. Read more about the underlying grid layout in the [Carbon Grid documentation](https://carbondesignsystem.com/guidelines/2x-grid/overview).
 

docs/components/modeler/forms/form-element-library/forms-element-library-iframe.md

@@ -7,7 +7,10 @@ description: Learn about the iFrame form element to embed external content.
 This is an element allowing the user to embed external content via an iFrame.
 
 :::note
-Every iFrame component is a sandbox. This means that the content of the iFrame is not able to access the parent page, cookies, browser storage, and others.[Learn more about sandbox iFrames](https://www.w3schools.com/tags/att_iframe_sandbox.asp).
+
+Every iFrame component is a sandbox. This means that the content of the iFrame is not able to access the parent page, cookies, browser storage, and others. [Learn more about sandbox iFrames](https://www.w3schools.com/tags/att_iframe_sandbox.asp).
+
+:::
 
 ![Form iFrame Symbol](/img/form-icons/form-iframe.svg)
 

docs/components/modeler/forms/form-element-library/forms-element-library.md

@@ -85,6 +85,12 @@ The following form elements are currently available within Camunda Forms:
     <td>Group multiple form elements</td>
   </tr>
 
+  <tr>
+    <td><img src="/img/form-icons/form-dynamiclist.svg" alt="Dynamic List Symbol" height="60"></img></td>
+    <td><a href="../forms-element-library-dynamiclist">Dynamic list</a></td>
+    <td>And and remove variable-length entries</td>
+  </tr>
+
   <tr>
     <td><img src="/img/form-icons/form-iframe.svg" alt="iFrame Symbol" height="60"></img></td>
     <td><a href="../forms-element-library-iframe">iFrame</a></td>

docs/components/modeler/forms/sidebar-schema.js

@@ -19,6 +19,7 @@ module.exports = {
         lib_dir + "forms-element-library-checklist",
         lib_dir + "forms-element-library-taglist",
         lib_dir + "forms-element-library-group",
+        lib_dir + "forms-element-library-dynamiclist",
         lib_dir + "forms-element-library-iframe",
         lib_dir + "forms-element-library-image",
         lib_dir + "forms-element-library-spacer",

docs/guides/improve-processes-with-optimize.md

@@ -105,11 +105,11 @@ Within the **Data Sources** tab, review and add source(s) of your data to create
 
 Now that we’ve created data sets within the **Home** page, let’s shift into the **Analysis** tab.
 
-Inside this tab, you’ll notice **Outlier Analysis** and **Branch Analysis**.
+Inside this tab, you’ll notice **Task Analysis** and **Branch Analysis**.
 
-### Outlier analysis
+### Task analysis
 
-Inside **Outlier Analysis**, we utilize heatmap displays. Click **Select Process**, choose your process, and choose your version.
+Inside **Task Analysis**, we utilize heatmap displays. Click **Select Process**, choose your process, and choose your version.
 
 ![heatmap example](./assets/heatmap.png)
 

docs/reference/announcements.md

@@ -8,7 +8,18 @@ description: "Important announcements including deprecation & removal notices"
 
 Release date: 9th of January 2024
 
-End of maintenance: 9th of July, 2025
+End of maintenance: 9th of July 2025
+
+### Versioning changes in Helm chart
+
+As of the 8.4 release, the Camunda 8 **Helm chart** version is decoupled from the version of the application. The Helm chart release still follows the applications release cycle, but it has an independent version. (e.g., in the application release cycle 8.4, the chart version is 9.0.0).
+
+For more details about the applications version included in the Helm chart, check out the [full version matrix](https://helm.camunda.io/camunda-platform/version-matrix/).
+
+### Dockerfile numeric ID
+
+The Dockerfile now uses a numeric user ID instead of a non-numeric user.
+This will allow the Helm users to use `runAsNonRoot=true` without the need to explicitly set the ID in the Helm `values.yaml` file.
 
 ### Deprecated in 8.4