From d49c1701fbca85a95c1e97b28faaf30b002e3966 Mon Sep 17 00:00:00 2001 From: Amara Date: Tue, 12 Mar 2024 11:37:17 -0500 Subject: [PATCH] backport --- .../best-practices/modeling/choosing-the-dmn-hit-policy.md | 2 +- .../best-practices/modeling/choosing-the-dmn-hit-policy.md | 2 +- .../best-practices/modeling/choosing-the-dmn-hit-policy.md | 2 +- .../best-practices/modeling/choosing-the-dmn-hit-policy.md | 2 +- .../best-practices/modeling/choosing-the-dmn-hit-policy.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/components/best-practices/modeling/choosing-the-dmn-hit-policy.md b/docs/components/best-practices/modeling/choosing-the-dmn-hit-policy.md index 3d9597545d..fe191a5fdb 100644 --- a/docs/components/best-practices/modeling/choosing-the-dmn-hit-policy.md +++ b/docs/components/best-practices/modeling/choosing-the-dmn-hit-policy.md @@ -45,7 +45,7 @@ Such tables either return the output of only one rule or aggregate the output of Camunda does not yet support the hit policy **priority**. In essence, priorities are specified as an ordered list of output values in decreasing order of priority. Such priorities are therefore independent from rule sequence! Though not yet supported, you can mimic that behavior using hit policy "(**C**)ollect" and determining a priority yourself; for example, by means of an execution listener attached to the end of your business rule task. ::: -- `**A**`**ny**: Multiple matching rules must not make a difference: all matching rules must lead to the same output. +- `A`**ny**: Multiple matching rules must not make a difference: all matching rules must lead to the same output. **Collect** and **aggregate**: The output of all matching rules is aggregated by means of an operator: diff --git a/versioned_docs/version-1.3/components/best-practices/modeling/choosing-the-dmn-hit-policy.md b/versioned_docs/version-1.3/components/best-practices/modeling/choosing-the-dmn-hit-policy.md index e4ee46aaf9..970fce42bd 100644 --- a/versioned_docs/version-1.3/components/best-practices/modeling/choosing-the-dmn-hit-policy.md +++ b/versioned_docs/version-1.3/components/best-practices/modeling/choosing-the-dmn-hit-policy.md @@ -45,7 +45,7 @@ Such tables either return the output of only one rule or aggregate the output of Camunda does not yet support the hit policy **priority**. In essence, priorities are specified as an ordered list of output values in decreasing order of priority. Such priorities are therefore independent from rule sequence! Though not yet supported, you can mimic that behavior using hit policy "(**C**)ollect" and determining a priority yourself; for example, by means of an execution listener attached to the end of your business rule task. ::: -* `**A**`**ny**: Multiple matching rules must not make a difference: all matching rules must lead to the same output. +* `A`**ny**: Multiple matching rules must not make a difference: all matching rules must lead to the same output. **Collect** and **aggregate**: The output of all matching rules is aggregated by means of an operator: diff --git a/versioned_docs/version-8.1/components/best-practices/modeling/choosing-the-dmn-hit-policy.md b/versioned_docs/version-8.1/components/best-practices/modeling/choosing-the-dmn-hit-policy.md index 50d201ac31..1daea7852a 100644 --- a/versioned_docs/version-8.1/components/best-practices/modeling/choosing-the-dmn-hit-policy.md +++ b/versioned_docs/version-8.1/components/best-practices/modeling/choosing-the-dmn-hit-policy.md @@ -45,7 +45,7 @@ Such tables either return the output of only one rule or aggregate the output of Camunda does not yet support the hit policy **priority**. In essence, priorities are specified as an ordered list of output values in decreasing order of priority. Such priorities are therefore independent from rule sequence! Though not yet supported, you can mimic that behavior using hit policy "(**C**)ollect" and determining a priority yourself; for example, by means of an execution listener attached to the end of your business rule task. ::: -- `**A**`**ny**: Multiple matching rules must not make a difference: all matching rules must lead to the same output. +- `A`**ny**: Multiple matching rules must not make a difference: all matching rules must lead to the same output. **Collect** and **aggregate**: The output of all matching rules is aggregated by means of an operator: diff --git a/versioned_docs/version-8.2/components/best-practices/modeling/choosing-the-dmn-hit-policy.md b/versioned_docs/version-8.2/components/best-practices/modeling/choosing-the-dmn-hit-policy.md index 50d201ac31..1daea7852a 100644 --- a/versioned_docs/version-8.2/components/best-practices/modeling/choosing-the-dmn-hit-policy.md +++ b/versioned_docs/version-8.2/components/best-practices/modeling/choosing-the-dmn-hit-policy.md @@ -45,7 +45,7 @@ Such tables either return the output of only one rule or aggregate the output of Camunda does not yet support the hit policy **priority**. In essence, priorities are specified as an ordered list of output values in decreasing order of priority. Such priorities are therefore independent from rule sequence! Though not yet supported, you can mimic that behavior using hit policy "(**C**)ollect" and determining a priority yourself; for example, by means of an execution listener attached to the end of your business rule task. ::: -- `**A**`**ny**: Multiple matching rules must not make a difference: all matching rules must lead to the same output. +- `A`**ny**: Multiple matching rules must not make a difference: all matching rules must lead to the same output. **Collect** and **aggregate**: The output of all matching rules is aggregated by means of an operator: diff --git a/versioned_docs/version-8.3/components/best-practices/modeling/choosing-the-dmn-hit-policy.md b/versioned_docs/version-8.3/components/best-practices/modeling/choosing-the-dmn-hit-policy.md index 3d9597545d..fe191a5fdb 100644 --- a/versioned_docs/version-8.3/components/best-practices/modeling/choosing-the-dmn-hit-policy.md +++ b/versioned_docs/version-8.3/components/best-practices/modeling/choosing-the-dmn-hit-policy.md @@ -45,7 +45,7 @@ Such tables either return the output of only one rule or aggregate the output of Camunda does not yet support the hit policy **priority**. In essence, priorities are specified as an ordered list of output values in decreasing order of priority. Such priorities are therefore independent from rule sequence! Though not yet supported, you can mimic that behavior using hit policy "(**C**)ollect" and determining a priority yourself; for example, by means of an execution listener attached to the end of your business rule task. ::: -- `**A**`**ny**: Multiple matching rules must not make a difference: all matching rules must lead to the same output. +- `A`**ny**: Multiple matching rules must not make a difference: all matching rules must lead to the same output. **Collect** and **aggregate**: The output of all matching rules is aggregated by means of an operator: