operaton · sgort · Nov 28, 2025 · Nov 28, 2025 · Nov 28, 2025 · Nov 28, 2025
diff --git a/docs/documentation/reference/bpmn20/tasks/task-markers.md b/docs/documentation/reference/bpmn20/tasks/task-markers.md
@@ -79,7 +79,7 @@ Expressions that resolve to a positive number are also possible:
 Another way to define the number of instances is to specify the name of a process variable which is a collection using the `loopDataInputRef` child element. For each item in the collection, an instance will be created. Optionally, it is possible to set that specific item of the collection for the instance using the inputDataItem child element. This is shown in the following XML example:
 
 ```xml
-<userTask id="miTasks" name="My Task ```${loopCounter}" operaton:assignee="${assignee}">
+<userTask id="miTasks" name="My Task ${loopCounter}" operaton:assignee="${assignee}">
   <multiInstanceLoopCharacteristics isSequential="false">
     <loopDataInputRef>assigneeList</loopDataInputRef>
     <inputDataItem name="assignee" />

diff --git a/docs/documentation/reference/deployment-descriptors/bpm-platform-xml.md b/docs/documentation/reference/deployment-descriptors/bpm-platform-xml.md
@@ -80,7 +80,7 @@ The namespace for the `bpm-platform.xml` file is `http://www.operaton.org/schema
     <td><code>&lt;process-engine&gt;</code></td>
     <td><code>&lt;bpm-platform&gt;</code></td>
     <td>false</td>
-    <td>See <a href="../reference/deployment-descriptors/tags/process-engine.md">process-engine Reference</a></td>
+    <td>See <a href="../reference/deployment-descriptors/tags/process-engine.mdx">process-engine Reference</a></td>
   </tr>
 </table>
 

diff --git a/docs/documentation/reference/deployment-descriptors/processes-xml.md b/docs/documentation/reference/deployment-descriptors/processes-xml.md
@@ -65,7 +65,7 @@ The `processes.xml` may be left blank (can be empty). In this case, default valu
     <td><code>&lt;process-engine&gt;</code></td>
     <td><code>&lt;process-application&gt;</code></td>
     <td>false</td>
-    <td>See <a href="../reference/deployment-descriptors/tags/process-engine.md">process-engine Reference</a></td>
+    <td>See <a href="../reference/deployment-descriptors/tags/process-engine.mdx">process-engine Reference</a></td>
   </tr>
     <tr>
     <td><code>&lt;process-archive&gt;</code></td>

diff --git a/docs/documentation/reference/deployment-descriptors/tags/process-engine.mdx b/docs/documentation/reference/deployment-descriptors/tags/process-engine.mdx
@@ -297,7 +297,7 @@ The following is a list with the most commonly used process engine configuration
   </tr>
 
   <tr>
-    <td><a name="disabledPermissions"></a><code>disabledPermissions</code></td>
+    <td id="disabledPermissions"><code>disabledPermissions</code></td>
     <td>List</td>
     <td>Define a list of Permissions' names. These permissions will be not taken into account whenever authorization check is performed.</td>
   </tr>
@@ -483,7 +483,7 @@ The following is a list with the most commonly used process engine configuration
     <td>
       Controls if and when the <a href="../user-guide/process-engine/history/history-cleanup.md#instance-removal-time">removal time</a> of an historic instance is set.
       The default value is <code>end</code>.<br/>
-      Please also see the <a href="../reference/deployment-descriptors/tags/process-engine.md#historyCleanupStrategy"><code>historyCleanupStrategy</code></a>
+      Please also see the <a href="../reference/deployment-descriptors/tags/process-engine.mdx#historyCleanupStrategy"><code>historyCleanupStrategy</code></a>
       configuration parameter.<br/><br/>
       <strong>Values:</strong> <code>start</code>, <code>end</code>, <code>none</code> (String).
     </td>
@@ -559,7 +559,7 @@ The following is a list with the most commonly used process engine configuration
     </td>
   </tr>
   <tr>
-    <td><code>jdbcBatchProcessing</code></td>
+    <td id="jdbcBatchProcessing"><code>jdbcBatchProcessing</code></td>
     <td>Boolean</td>
     <td>
         Controls if the engine executes the jdbc statements as Batch or not.
@@ -809,15 +809,15 @@ The following is a list with the most commonly used process engine configuration
   </tr>
 
   <tr>
-    <td><a name="javaSerializationFormatEnabled"></a><code>javaSerializationFormatEnabled</code></td>
+    <td id="javaSerializationFormatEnabled"><code>javaSerializationFormatEnabled</code></td>
     <td>Boolean</td>
     <td>
         Sets if Java serialization format can be used, when <a href="../user-guide/process-engine/variables.md#object-values">setting variables by their serialized representation</a>. Default value: <code>false</code>
     </td>
   </tr>
 
   <tr>
-    <td><a name="deserializationTypeValidationEnabled"></a><code>deserializationTypeValidationEnabled</code></td>
+    <td id="deserializationTypeValidationEnabled"><code>deserializationTypeValidationEnabled</code></td>
     <td>Boolean</td>
     <td>
         Sets if validation of types should be performed before JSON and XML deserialization. See <a href="../user-guide/security.md#variable-values-from-untrusted-sources">Security Instructions</a> for further information. Default value: <code>false</code>
@@ -841,31 +841,31 @@ The following is a list with the most commonly used process engine configuration
   </tr>
 
   <tr>
-    <td><a name="enablePasswordPolicy"></a><code>enablePasswordPolicy</code></td>
+    <td id="enablePasswordPolicy"><code>enablePasswordPolicy</code></td>
     <td>Boolean</td>
     <td>
         Set to <code>true</code>, to enable a <a href="../user-guide/process-engine/password-policy">password policy</a> for users that are managed by the engine. If a <a href="https://docs.operaton.org/docs/documentation/user-guide/process-engine/password-policy/#customize-the-password-policy">custom password policy</a> is configured, it will be enabled. Otherwise the <a href="https://docs.operaton.org/docs/documentation/user-guide/process-engine/password-policy/#built-in-password-policy">built-in password policy</a> is activated.
     </td>
   </tr>
 
   <tr>
-    <td><a name="enableCmdExceptionLogging"></a><code>enableCmdExceptionLogging</code></td>
+    <td id="enableCmdExceptionLogging"><code>enableCmdExceptionLogging</code></td>
     <td>Boolean</td>
     <td>
         Set to <code>false</code>, to disable logging of unhandled exceptions that occur during command execution. The default setting for this flag is <code>true</code>. Note: There might be duplicate log entries for command exceptions (e.g. when a job fails).
     </td>
   </tr>
 
   <tr>
-    <td><a name="enableReducedJobExceptionLogging"></a><code>enableReducedJobExceptionLogging</code></td>
+    <td id="enableReducedJobExceptionLogging"><code>enableReducedJobExceptionLogging</code></td>
     <td>Boolean</td>
     <td>
         Set to <code>true</code>, to suppress logging of exceptions that occur during the execution of a job that has retries left. If the job does not have any retries left an exception will still be logged.
     </td>
   </tr>
 
   <tr id="webappsAuthenticationLoggingEnabled">
-    <td><a name="webappsAuthenticationLoggingEnabled"></a><code>webappsAuthenticationLoggingEnabled</code></td>
+    <td id="webappsAuthenticationLoggingEnabled"><code>webappsAuthenticationLoggingEnabled</code></td>
     <td>Boolean</td>
     <td>
         Set to <code>true</code> to enable authentication logging in the Operaton web apps (Cockpit, Tasklist, and Admin). When enabled, the Operaton web apps will produce log statements in the application log for each user initiated log in and log out event. The name of the logger is <code>org.operaton.bpm.webapp</code>.
@@ -1085,7 +1085,7 @@ The following is a list with the most commonly used process engine configuration
     <td>
       Controls which <a href="../user-guide/process-engine/history/history-cleanup.md">History cleanup</a> strategy is used.
       The default value is <code>removalTimeBased</code>.<br/>
-      Please also see the <a href="../reference/deployment-descriptors/tags/process-engine.md#historyRemovalTimeStrategy"><code>historyRemovalTimeStrategy</code></a> configuration parameter.<br/><br/>
+      Please also see the <a href="../reference/deployment-descriptors/tags/process-engine.mdx#historyRemovalTimeStrategy"><code>historyRemovalTimeStrategy</code></a> configuration parameter.<br/><br/>
       <strong>Values:</strong> <code>removalTimeBased</code>, <code>endTimeBased</code>.
     </td>
   </tr>

diff --git a/docs/documentation/user-guide/dmn-engine/expressions-and-scripts.md b/docs/documentation/user-guide/dmn-engine/expressions-and-scripts.md
@@ -134,7 +134,7 @@ DMN engine are as follows:
 
 :::note[Legacy Behavior]
 You can find how to go back to the legacy behavior, where `JUEL` was used for input expressions,
-output entries and literal expressions [here](../../reference/deployment-descriptors/tags/process-engine.md#dmnFeelEnableLegacyBehavior).
+output entries and literal expressions [here](../../reference/deployment-descriptors/tags/process-engine.mdx#dmnFeelEnableLegacyBehavior).
 :::
 
 The default language can be changed by setting it directly in the DMN 1.3 XML as global expression language with the `expressionLanguage` attribute of

diff --git a/docs/documentation/user-guide/dmn-engine/feel/custom-functions.md b/docs/documentation/user-guide/dmn-engine/feel/custom-functions.md
@@ -121,5 +121,5 @@ the types listed in the [FEEL Data Types] documentation can be returned by a Cus
 [FEEL Type Handling]: ../../../user-guide/dmn-engine/feel/type-handling.md#return-types
 [FEEL Data Types]: https://camunda.github.io/feel-scala/1.11/feel-data-types
 [Process Engine Plugin]: ../../../user-guide/process-engine/process-engine-plugins.md
-[dmnFeelCustomFunctionProviders]: ../../../reference/deployment-descriptors/tags/process-engine.md#dmnFeelCustomFunctionProviders
+[dmnFeelCustomFunctionProviders]: ../../../reference/deployment-descriptors/tags/process-engine.mdx#dmnFeelCustomFunctionProviders
 [Register Custom Function Providers]: #register-custom-function-providers
diff --git a/docs/documentation/user-guide/dmn-engine/feel/legacy-behavior.md b/docs/documentation/user-guide/dmn-engine/feel/legacy-behavior.md
@@ -31,6 +31,6 @@ By using the legacy FEEL Engine, the Operaton DMN Engine **only** supports `FEEL
 simple unary tests.
 :::
 
-[legacy behavior flag]: ../../../reference/deployment-descriptors/tags/process-engine.md#dmnFeelEnableLegacyBehavior
+[legacy behavior flag]: ../../../reference/deployment-descriptors/tags/process-engine.mdx#dmnFeelEnableLegacyBehavior
 [fluent feel flag setter]: https://docs.operaton.org/reference/latest/javadoc/org/operaton/bpm/dmn/engine/impl/DefaultDmnEngineConfiguration.html#enableFeelLegacyBehavior
 [feel flag setter](https://docs.operaton.org/reference/latest/javadoc/org/operaton/bpm/dmn/engine/impl/DefaultDmnEngineConfiguration.html#setEnableFeelLegacyBehavior)
diff --git a/docs/documentation/user-guide/logging.md b/docs/documentation/user-guide/logging.md
@@ -101,7 +101,7 @@ In case of arising exceptions upon execution, the data is kept in the MDC until
 i.e. the [JobExecutor](../user-guide/process-engine/the-job-executor.md) or the surrounding command, finished its logging.
 
 The keys at which the properties are accessible in the MDC can be defined in the
-[process engine configuration](../reference/deployment-descriptors/tags/process-engine.md#logging-context-parameters).
+[process engine configuration](../reference/deployment-descriptors/tags/process-engine.mdx#logging-context-parameters).
 
 In order to access the MDC data, you need to adjust the logging pattern of your logging configuration.
 An example using Logback could look as follows
@@ -176,7 +176,7 @@ The process engine logs on the following categories
     <td>
       command context logs including executing atomic operations and bpmn stack traces during exceptions<br/>
       You can override the default <code>DEBUG</code> log level for bpmn stack traces, see the
-      <a href="../reference/deployment-descriptors/tags/process-engine.md#logLevelBpmnStackTrace">Logging level parameters</a> section.
+      <a href="../reference/deployment-descriptors/tags/process-engine.mdx#logLevelBpmnStackTrace">Logging level parameters</a> section.
     </td>
   </tr>
   <tr>

diff --git a/docs/documentation/user-guide/operaton-bpm-run.md b/docs/documentation/user-guide/operaton-bpm-run.md
@@ -177,7 +177,7 @@ Just like all the other distros, you can tailor Operaton Run to your needs. To d
 
 :::note[Note:]
 Operaton Run is based on the [Operaton Spring Boot Starter](https://github.com/operaton/operaton/tree/master/spring-boot-starter).
-All [configuration properties](spring-boot-integration/configuration.md#operaton-engine-properties) from the operaton-spring-boot-starter are available to customize Operaton Run.
+All [configuration properties](spring-boot-integration/configuration.mdx#operaton-engine-properties) from the operaton-spring-boot-starter are available to customize Operaton Run.
 :::
 
 ### Database

diff --git a/docs/documentation/user-guide/process-engine/authorization-service.md b/docs/documentation/user-guide/process-engine/authorization-service.md
@@ -1037,5 +1037,5 @@ On these databases, revoke authorizations are effectively unusable.
 
 Also see the [Configuration Options](#check-revoke-authorizations) section on this page.
 
-[hist-inst-perm-config-flag]: ../../reference/deployment-descriptors/tags/process-engine.md#enable-historic-instance-permissions
+[hist-inst-perm-config-flag]: ../../reference/deployment-descriptors/tags/process-engine.mdx#enable-historic-instance-permissions
 [Removal-Time-based History Cleanup Strategy]: ../process-engine/history/history-cleanup.md#removal-time-based-strategy
diff --git a/docs/documentation/user-guide/process-engine/batch.md b/docs/documentation/user-guide/process-engine/batch.md
@@ -329,7 +329,7 @@ You can configure the property in three ways:
 [job prioritization]: ../process-engine/the-job-executor.md#job-prioritization
 [job-definition-priority]: ../process-engine/the-job-executor.md#override-priority-by-job-definition
 [job-priority]: ../process-engine/the-job-executor.md#set-job-priorities-via-managementservice-api
-[invoc-per-batch-job-batch-type]: ../../reference/deployment-descriptors/tags/process-engine.md#invocations-per-batch-job-by-batch-type
+[invoc-per-batch-job-batch-type]: ../../reference/deployment-descriptors/tags/process-engine.mdx#invocations-per-batch-job-by-batch-type
 [Process Engine Plugin]: ../process-engine/process-engine-plugins.md
 [spring-xml-config]: ../spring-framework-integration/configuration.md
-[spring-boot-config]: ../spring-boot-integration/configuration.md#operaton-engine-properties
+[spring-boot-config]: ../spring-boot-integration/configuration.mdx#operaton-engine-properties
diff --git a/docs/documentation/user-guide/process-engine/database/database-configuration.md b/docs/documentation/user-guide/process-engine/database/database-configuration.md
@@ -29,10 +29,9 @@ The data source that is constructed based on the provided JDBC properties will h
 
 ## Jdbc Batch Processing
 
-<a name="jdbcBatchProcessing"></a>Another configuration - `jdbcBatchProcessing` - sets if batch processing mode must be used when sending SQL statements to the database. When switched off, statements are executed one by one.
+Another configuration - [jdbcBatchProcessing](../../../../documentation/reference/deployment-descriptors/tags/process-engine.mdx#jdbcBatchProcessing) - sets if batch processing mode must be used when sending SQL statements to the database. When switched off, statements are executed one by one.
 Values: `true` (default), `false`.
 
-Known issues with batch processing:
 
 * batch processing is not working for Oracle versions earlier than 12.
 * when using batch processing on MariaDB and DB2, `jdbcStatementTimeout` is being ignored.
@@ -179,4 +178,4 @@ When initializing the engine, a check is performed in order to determine if the
 
 This behaviour can be disabled by setting the `skipIsolationLevelCheck` flag to `true`. Doing this will prevent an exception from being thrown and a warning message will be logged instead.
 
-[See here](../../../reference/deployment-descriptors/tags/process-engine.md#configuration-properties) for more details about this and other properties.
+[See here](../../../reference/deployment-descriptors/tags/process-engine.mdx#configuration-properties) for more details about this and other properties.
diff --git a/docs/documentation/user-guide/process-engine/database/performance.md b/docs/documentation/user-guide/process-engine/database/performance.md
@@ -19,4 +19,4 @@ The task query is one of the heaviest used and most powerful queries of the proc
 
 ### Disabling CMMN and Standalone Tasks
 
-To perform transparent access checks, the task query joins the authorization table (`ACT_RU_AUTHORIZATION`). For any kind of process-related filters, it joins the process definition table (`ACT_RE_PROCDEF`). By default, the query uses a left join for these operations. If CMMN and standalone tasks (tasks that are neither related to a BPMN process, nor a CMMN case) are not used, the engine configuration flags `cmmnEnabled` and `standaloneTasksEnabled` can be set to `false`. Then, the left joins are replaced by inner joins which perform better on some databases. See the [configuration properties reference](../../../reference/deployment-descriptors/tags/process-engine.md#configuration-properties) for details on these settings.
+To perform transparent access checks, the task query joins the authorization table (`ACT_RU_AUTHORIZATION`). For any kind of process-related filters, it joins the process definition table (`ACT_RE_PROCDEF`). By default, the query uses a left join for these operations. If CMMN and standalone tasks (tasks that are neither related to a BPMN process, nor a CMMN case) are not used, the engine configuration flags `cmmnEnabled` and `standaloneTasksEnabled` can be set to `false`. Then, the left joins are replaced by inner joins which perform better on some databases. See the [configuration properties reference](../../../reference/deployment-descriptors/tags/process-engine.mdx#configuration-properties) for details on these settings.
diff --git a/docs/documentation/user-guide/process-engine/error-handling.md b/docs/documentation/user-guide/process-engine/error-handling.md
@@ -143,7 +143,7 @@ Learn more on how to assign a custom error code to an exception in the documenta
 
 ### Configuration
 
-You can configure the exception error codes feature in your [process engine configuration](../../reference/deployment-descriptors/tags/process-engine.md#exception-codes):
+You can configure the exception error codes feature in your [process engine configuration](../../reference/deployment-descriptors/tags/process-engine.mdx#exception-codes):
 
 * To disable the exception codes feature entirely, set the flag <code>disableExceptionCode</code>
   in your process engine configuration to <code>true</code>.

diff --git a/docs/documentation/user-guide/process-engine/expression-language.md b/docs/documentation/user-guide/process-engine/expression-language.md
@@ -154,7 +154,7 @@ The following example shows usage of expression language as condition of a seque
 ```xml
   <sequenceFlow>
     <conditionExpression xsi:type="tFormalExpression">
-      ```${test == 'foo'}
+      ${test == 'foo'}
     </conditionExpression>
   </sequenceFlow>
 ```
@@ -185,7 +185,7 @@ a bean.
     <extensionElements>
       <operaton:inputOutput>
         <operaton:inputParameter name="x">
-          ```${myBean.calculateX()}
+          ${myBean.calculateX()}
         </operaton:inputParameter>
       </operaton:inputOutput>
     </extensionElements>
@@ -243,7 +243,7 @@ conditional sequence flow can directly check a variable value:
 ```xml
   <sequenceFlow>
     <conditionExpression xsi:type="tFormalExpression">
-      ```${test == 'start'}
+      ${test == 'start'}
     </conditionExpression>
   </sequenceFlow>
 ```
Original file line number	Diff line number	Diff line change
Expand Up		@@ -19,4 +19,4 @@ The task query is one of the heaviest used and most powerful queries of the proc

		### Disabling CMMN and Standalone Tasks

		To perform transparent access checks, the task query joins the authorization table (`ACT_RU_AUTHORIZATION`). For any kind of process-related filters, it joins the process definition table (`ACT_RE_PROCDEF`). By default, the query uses a left join for these operations. If CMMN and standalone tasks (tasks that are neither related to a BPMN process, nor a CMMN case) are not used, the engine configuration flags `cmmnEnabled` and `standaloneTasksEnabled` can be set to `false`. Then, the left joins are replaced by inner joins which perform better on some databases. See the [configuration properties reference](../../../reference/deployment-descriptors/tags/process-engine.md#configuration-properties) for details on these settings.
		To perform transparent access checks, the task query joins the authorization table (`ACT_RU_AUTHORIZATION`). For any kind of process-related filters, it joins the process definition table (`ACT_RE_PROCDEF`). By default, the query uses a left join for these operations. If CMMN and standalone tasks (tasks that are neither related to a BPMN process, nor a CMMN case) are not used, the engine configuration flags `cmmnEnabled` and `standaloneTasksEnabled` can be set to `false`. Then, the left joins are replaced by inner joins which perform better on some databases. See the [configuration properties reference](../../../reference/deployment-descriptors/tags/process-engine.mdx#configuration-properties) for details on these settings.