Merge branch 'main' into nloding-ai-agent-event-handling-link

Author: nloding

.github/workflows/build-docs.yaml

@@ -9,7 +9,7 @@ jobs:
       temporary_link_path: .github/workflows/validate-links
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-node@v5
+      - uses: actions/setup-node@v6
         with:
           node-version: 22
       - name: Install Dependencies

.github/workflows/check-format.yaml

@@ -6,7 +6,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-node@v5
+      - uses: actions/setup-node@v6
         with:
           node-version: 22
       - name: Install Dependencies

.github/workflows/preview-env-deploy.yml

@@ -15,7 +15,7 @@ jobs:
     name: deploy-preview-env
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-node@v5
+      - uses: actions/setup-node@v6
         with:
           node-version: 22
 

.github/workflows/publish-prod.yaml

@@ -25,7 +25,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-node@v5
+      - uses: actions/setup-node@v6
         with:
           node-version: 22
       - name: Install Dependencies

.github/workflows/publish-stage.yaml

@@ -15,7 +15,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-node@v5
+      - uses: actions/setup-node@v6
         with:
           node-version: 22
       - name: Install Dependencies

.github/workflows/test.yaml

@@ -15,7 +15,7 @@ jobs:
         uses: actions/checkout@v5
 
       - name: Setup Node.js
-        uses: actions/setup-node@v5
+        uses: actions/setup-node@v6
         with:
           node-version-file: ".nvmrc"
           cache: "npm"

.github/workflows/update-release-links.yml

@@ -19,7 +19,7 @@ jobs:
         uses: actions/checkout@v5
 
       - name: Setup Node.js
-        uses: actions/setup-node@v5
+        uses: actions/setup-node@v6
         with:
           node-version: "22"
           cache: "npm"

connectors-element-template-links.txt

@@ -95,8 +95,6 @@ https://docs.camunda.io/docs/components/connectors/out-of-the-box-connectors/mic
 https://docs.camunda.io/docs/components/connectors/out-of-the-box-connectors/microsoft-teams
 https://docs.camunda.io/docs/components/connectors/out-of-the-box-connectors/openai
 https://docs.camunda.io/docs/components/connectors/out-of-the-box-connectors/operate
-https://docs.camunda.io/docs/components/connectors/out-of-the-box-connectors/power-automate
-https://docs.camunda.io/docs/components/connectors/out-of-the-box-connectors/power-automate/#oauth-token-endpoint
 https://docs.camunda.io/docs/components/connectors/out-of-the-box-connectors/rabbitmq
 https://docs.camunda.io/docs/components/connectors/out-of-the-box-connectors/rabbitmq-inbound
 https://docs.camunda.io/docs/components/connectors/out-of-the-box-connectors/rabbitmq/#routing-data

docs/apis-tools/frontend-development/01-task-applications/01-introduction-to-task-applications.md

@@ -61,7 +61,7 @@ Typically, a task application utilizes forms to capture information from the use
 
 However, a [user task](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms) is not limited to forms. A user task could also represent navigating to an external desktop or web application, where a task is to be performed, such as updating a record in a CRM. You can even use them to track physical work or actions using sensors, IoT devices, or any interface that can talk to the web, by using the [APIs](/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md) or registering a [job worker](/components/concepts/job-workers.md) to the job type `io.camunda.zeebe:userTask` (compatible with [job worker-based user tasks](/components/modeler/bpmn/user-tasks/user-tasks.md) only).
 
-For these cases, utilize the flexible [custom form key](/components/modeler/web-modeler/advanced-modeling/form-linking.md#custom-form-key).
+For these cases, utilize the flexible [custom form key](/components/modeler/web-modeler/modeling/advanced-modeling/form-linking.md#custom-form-key).
 :::
 
 On the top of the form, a header shows the title of the task to work on, and the current assignee. Depending on the status of the assignment, a button allows you to assign the task to yourself or release it to the queue.

docs/apis-tools/frontend-development/03-forms/01-introduction-to-forms.md

@@ -9,7 +9,7 @@ import GHIcon from "@site/src/mdx/GitHubInlineIcon";
 
 Forms play a key role in giving work instructions, collecting information and making decisions within human task orchestration. Forms are lightweight user interfaces, tailored for focused data input in specific steps of a process, rendering the orchestration of human tasks more efficient than simply routing users to the applications that are orchestrated.
 
-Forms are commonly used in [user tasks](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms), but also as [start forms](/components/tasklist/userguide/starting-processes.md) to start a new process instance, or even as [public forms](/components/modeler/web-modeler/advanced-modeling/publish-public-processes.md), e.g. to capture user input at scale or to allow your customers to trigger a self-service process.
+Forms are commonly used in [user tasks](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-forms), but also as [start forms](/components/tasklist/userguide/starting-processes.md) to start a new process instance, or even as [public forms](/components/modeler/web-modeler/modeling/advanced-modeling/publish-public-processes.md), e.g. to capture user input at scale or to allow your customers to trigger a self-service process.
 
 ## Camunda Forms