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
You can now configure Optimize data filters directly in Console cluster settings, without editing Helm values or configuration files.
323
-
324
-
The **Data filters** section in cluster settings lets you:
325
-
326
-
- Enable or disable Optimize export filtering per cluster.
327
-
- Include or exclude process definitions by exact `bpmnProcessId`.
328
-
- Include or exclude variable names by prefix — for example, `business_` includes all variables whose names start with `business_`.
329
-
- Exclusion takes precedence over inclusion when both are configured.
330
-
331
-
New SaaS clusters include a default `business_` variable include filter, which limits Optimize to variables starting with `business_` to reduce Elasticsearch storage and shard usage. Existing clusters show data filters disabled with a one-click opt-in — no automatic migration occurs.
332
-
333
-
Saving filter changes triggers a rolling restart of the Orchestration Cluster; the cluster is briefly unavailable while it restarts.
334
-
335
-
:::warning
336
-
Filtered records are permanently excluded from Optimize and cannot be recovered even if you relax the filters later.
337
-
:::
338
-
339
-
<pclass="link-arrow">[Configure Optimize data filters](/components/hub/organization/manage-clusters/settings.md#data-filters)</p>
@@ -348,18 +327,12 @@ Filtered records are permanently excluded from Optimize and cannot be recovered
348
327
349
328
Use the new App Integrations connector to send and receive messages in Microsoft Teams and Slack.
350
329
351
-
#### Send Microsoft Teams and Slack messages without managing credentials
330
+
**Send messages**: You can send Microsoft Teams and Slack messages without managing credentials. The connector sends messages to Microsoft Teams and Slack, and creates channels, through your organization's Camunda app integrations. The connection is configured once for the environment, so no endpoint or credentials appear in the process model.
352
331
353
-
The App Integrations connector sends messages to Microsoft Teams and Slack, and creates channels, through your organization's Camunda app integrations. The connection is configured once for the environment, so no endpoint or credentials appear in the process model.
332
+
**Receive messages**: You can receive Microsoft Teams and Slack messages in a process. A process can start from a message someone writes to the Camunda app in Microsoft Teams or Slack, and a process that is already holding a conversation receives the reply, so an approval, a choice, or a correction can be collected in the chat people are already in rather than in a separate form.
#### Receive Microsoft Teams and Slack messages in a process
358
-
359
-
The App Integrations connector receives messages as well as sending them. A process can start from a message someone writes to the Camunda app in Microsoft Teams or Slack, and a process that is already holding a conversation receives the reply, so an approval, a choice, or a correction can be collected in the chat people are already in rather than in a separate form.
360
-
361
-
<pclass="link-arrow">[Receive a chat message](/components/connectors/out-of-the-box-connectors/app-integrations.md#receive-a-chat-message)</p>
You can now configure Optimize data filters directly in cluster settings, without editing Helm values or configuration files.
801
+
802
+
The **Data filters** section in cluster settings lets you:
803
+
804
+
- Enable or disable Optimize export filtering per cluster.
805
+
- Include or exclude process definitions by exact `bpmnProcessId`.
806
+
- Include or exclude variable names by prefix — for example, `business_` includes all variables whose names start with `business_`.
807
+
- Exclusion takes precedence over inclusion when both are configured.
808
+
809
+
New SaaS clusters include a default `business_` variable include filter, which limits Optimize to variables starting with `business_` to reduce Elasticsearch storage and shard usage. Existing clusters show data filters disabled with a one-click opt-in — no automatic migration occurs.
810
+
811
+
Saving filter changes triggers a rolling restart of the Orchestration Cluster; the cluster is briefly unavailable while it restarts.
812
+
813
+
:::warning
814
+
Filtered records are permanently excluded from Optimize and cannot be recovered even if you relax the filters later.
815
+
:::
816
+
817
+
<p class="link-arrow">[Configure Optimize data filters](/components/hub/organization/manage-clusters/settings.md#data-filters)</p>
818
+
823
819
### Object variables no longer flattened by default in Self-Managed
0 commit comments