Fix docs link checks and enforce quality gates

docs/documentation/installation/operaton-bpm-run.md

@@ -24,7 +24,7 @@ java -version
 If you need to install Java Runtime Environment, you can [find the download from Oracle here](https://www.oracle.com/java/technologies/javase-downloads.html).
 
 ## Installation Procedure
-1. Download the pre-packed distribution of  [Operaton here](tbd).
+1. Download the pre-packed [Operaton Run distribution](https://github.com/operaton/operaton/releases/latest).
 1. Unpack the distro to a directory.
 1. Configure the distro as described in the [User Guide](../user-guide/operaton-bpm-run.md).
 1. Start Operaton Run by executing the start script (start.bat for Windows, start.sh for Linux/Mac).

docs/documentation/introduction/implemented-standards.md

@@ -21,8 +21,8 @@ Business Process Model and Notation (BPMN) is a standard for Workflow and Proces
 Operaton supports the 2.0 version of BPMN.
 
 * Getting started implementing BPMN Processes: [Quick Start (Java / JS)]
-* Getting to Know BPMN as a Modeling Language: [BPMN Modeling Tutorial]
-* Modeling BPMN: [BPMN Modeling Reference]
+* Getting to Know BPMN as a Modeling Language: [Quick Start (Java / JS)]
+* Modeling BPMN: [BPMN Implementation Reference]
 * Tool for modeling BPMN: [BPMN Modeler][modelers]
 * Implementing BPMN Processes: [BPMN Implementation Reference]
 * Executing BPMN: [Process Engine]
@@ -49,13 +49,11 @@ Operaton supports the 1.1 version of DMN.
 
 [OMG]: http://www.omg.org/
 [modelers]: ../modeling-bpmn/index.md
-[BPMN Modeling Tutorial]: https://operaton.org/bpmn/tutorial/
-[BPMN Modeling Reference]: https://operaton.org/bpmn/reference/
-[Quick Start (Java / JS)]: /get-started/quick-start/
+[Quick Start (Java / JS)]: /docs/get-started/quick-start/
 [BPMN Implementation Reference]: ../reference/bpmn20/index.md
 [CMMN Implementation Reference]: ../reference/cmmn11/index.md
-[DMN Getting Started]: /get-started/dmn/
+[DMN Getting Started]: /docs/get-started/dmn/
 [DMN Implementation Reference]: ../reference/dmn/index.md
-[DMN Modeling Tutorial]: https://operaton.org/dmn/tutorial/
+[DMN Modeling Tutorial]: /docs/get-started/dmn/
 [Process Engine]: ../user-guide/process-engine/index.md
 [DMN Engine]: ../user-guide/dmn-engine/index.md

docs/documentation/introduction/supported-environments.md

@@ -14,7 +14,7 @@ menu:
 Run Operaton in every Java-runnable environment. Operaton is supported with our QA infrastructure in the following environments.
 
 :::note[Supported Environments]
-  Please note that the environments listed in this section depend on the version of Operaton. Please select the corresponding version of this documentation to see the environment that fits to your version of Operaton. e.g., [supported environments for version 7.15](http://docs.operaton.org/7.15/guides/user-guide/#introduction-supported-environments)
+  Please note that the environments listed in this section depend on the version of Operaton. Select the corresponding version of this documentation to see the environment that fits your Operaton version.
 :::
 
 

docs/documentation/reference/bpmn20/events/bpmn/event-error.bpmn

@@ -28,7 +28,7 @@
     </bpmn2:userTask>
     <bpmn2:sequenceFlow id="SequenceFlow_3" sourceRef="UserTask_1" targetRef="EndEvent_1"/>
   </bpmn2:process>
-  <bpmn2:error id="Error_1" errorCode="ERROR-OCCURED" name="ERROR-OCCURED"/>
+  <bpmn2:error id="Error_1" errorCode="ERROR-OCCURRED" name="ERROR-OCCURRED"/>
   <bpmndi:BPMNDiagram id="BPMNDiagram_1">
     <bpmndi:BPMNPlane id="BPMNPlane_1" bpmnElement="Process_1">
       <bpmndi:BPMNShape id="_BPMNShape_StartEvent_30" bpmnElement="StartEvent_1">
@@ -86,4 +86,4 @@
       </bpmndi:BPMNEdge>
     </bpmndi:BPMNPlane>
   </bpmndi:BPMNDiagram>
-</bpmn2:definitions>
+</bpmn2:definitions>

docs/documentation/reference/bpmn20/events/cancel-and-compensation-events.md

@@ -185,4 +185,4 @@ The XML representation of a compensation start event is the normal start event d
 ### Additional Resources
 
 * [Transaction subprocess](../subprocesses/transaction-subprocess.md)
-* [Compensation Events](http://operaton.org/bpmn/reference.html#events-compensation) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+* [Events](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)

docs/documentation/reference/bpmn20/events/conditional-events.md

@@ -266,4 +266,4 @@ If a variable is set in the context of the `SubProcess` instance, then only the
 
 ## Additional Resources
 
-* [Conditional Events](http://operaton.org/bpmn/reference.html#events-conditional) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+* [Events](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)

docs/documentation/reference/bpmn20/events/error-events.md

@@ -28,7 +28,7 @@ An error event definition references an error element. The following is an examp
 
 ```xml
 <definitions>
-  <error id="myError" errorCode="ERROR-OCCURED" name="ERROR-OCCURED"/>
+  <error id="myError" errorCode="ERROR-OCCURRED" name="ERROR-OCCURRED"/>
   <!-- ... -->
   <process>
     <!-- ... -->
@@ -67,7 +67,7 @@ The referencing error event definition must specify <a href="../custom-extension
 
 ```xml
 <definitions>
-  <error id="myError" errorCode="ERROR-OCCURED" name="ERROR-OCCURED"
+  <error id="myError" errorCode="ERROR-OCCURRED" name="ERROR-OCCURRED"
       operaton:errorMessage="Something went wrong: ```${errorCause}" />
   <!-- ... -->
   <process>
@@ -192,7 +192,7 @@ A error boundary event is defined as a typical boundary event. As with the other
 
 ```xml
 <definitions>
-  <error id="myError" errorCode="ERROR-OCCURED" name="name of error"/>
+  <error id="myError" errorCode="ERROR-OCCURRED" name="name of error"/>
   <!-- ... -->
   <process>
     <!-- ... -->
@@ -230,5 +230,5 @@ An error can be handled by the error start event in the event sub process and th
 
 ### Additional Resources
 
-*   [Error Events](http://operaton.org/bpmn/reference.html#events-error) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+*   [Events](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)
 *   [Incidents](../../../user-guide/process-engine/incidents.md) in the [User Guide](../../../user-guide/index.md)

docs/documentation/reference/bpmn20/events/signal-events.md

@@ -313,4 +313,4 @@ The following extensions are supported for the Signal Intermediate and End Throw
 
 ## Additional Resources
 
-*   [Signal Events](http://operaton.org/bpmn/reference.html#events-signal) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+*   [Events](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)

docs/documentation/reference/bpmn20/events/terminate-event.md

@@ -61,4 +61,4 @@ A terminate event is modeled as an end event with an additional definition eleme
 
 ### Additional Resources
 
-* [Terminate Events](http://operaton.org/bpmn/reference.html#events-termination) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+* [Events](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)

docs/documentation/reference/bpmn20/gateways/event-based-gateway.md

@@ -95,4 +95,4 @@ The corresponding xml looks like this:
 
 ## Additional Resources
 
-*   [Event-based Gateways](http://operaton.org/bpmn/reference.html#gateways-event-based-gateways) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+*   [Gateways](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)

docs/documentation/reference/bpmn20/gateways/exclusive-gateway.md

@@ -75,4 +75,4 @@ The XML representation of an exclusive gateway is straightforward: one line defi
 ## Additional Resources
 
 *   [Conditional and Default Sequence Flows](../gateways/sequence-flow.md)
-*   [Exclusive Gateways](http://operaton.org/bpmn/reference.html#gateways-data-based-exclusive-gateways) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+*   [Gateways](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)

docs/documentation/reference/bpmn20/gateways/inclusive-gateway.md

@@ -162,5 +162,5 @@ The following examples show under which conditions an inclusive gateway will tri
 
 ## Additional Resources
 
-*   [Inclusive Gateways](http://operaton.org/bpmn/reference.html#gateways-data-based-inclusive-gateways) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+*   [Gateways](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)
 *   [Conditional and Default Sequence Flows](../gateways/sequence-flow.md)

docs/documentation/reference/bpmn20/gateways/parallel-gateway.md

@@ -118,4 +118,4 @@ Note that a parallel gateway does not need to be 'balanced' (i.e., a matching nu
 
 ## Additional Resources
 
-*   [Parallel Gateways](http://operaton.org/bpmn/reference.html#gateways-parallel-gateways) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+*   [Gateways](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)

docs/documentation/reference/bpmn20/index.md

@@ -9,7 +9,7 @@ This page gives you an overview of the BPMN 2.0 elements and the current coverag
 
 :::note[BPMN - Business Process Model and Notation]
 If you are unfamiliar with BPMN 2.0, you might want to check out the
-<a href="http://operaton.org/bpmn/tutorial.html">BPMN Tutorial</a> first.
+<a href="/docs/get-started/quick-start/">BPMN Quick Start</a> first.
 :::
 
 ## Coverage
@@ -181,8 +181,7 @@ In BPMN there are start events, intermediate events and end events. These three
 
 :::note[Understanding BPMN Events]
 To help understand the principle behavior of events in BPMN, we recommend to check the
-[Events: Basic Concepts](http://operaton.org/bpmn/reference.html#events-basic-concepts)
-chapter of the [BPMN Modeling Reference](http://operaton.org/bpmn/reference.html).
+[Events](./events/index.md) section of this BPMN 2.0 implementation reference.
 :::
 
 <table class="table table-responsive table-bordered bpmn-events" style={{width: '100%', fontSize:'13px'}}>
@@ -483,4 +482,4 @@ chapter of the [BPMN Modeling Reference](http://operaton.org/bpmn/reference.html
       <td></td>
     </tr>    
   </tbody>
-</table>
+</table>

docs/documentation/reference/bpmn20/subprocesses/call-activity.md

@@ -402,4 +402,4 @@ An expression also allows using the tenant id of the calling process instance in
 
 ## Additional Resources
 
-*   [Call Activity](http://operaton.org/bpmn/reference.html#activities-call-activity) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+*   [Subprocesses](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)

docs/documentation/reference/bpmn20/subprocesses/embedded-subprocess.md

@@ -79,4 +79,4 @@ A subprocess is defined by the subprocess element. All activities, gateways, eve
 
 ### Additional Resources
 
-*   [Subprocesses](http://operaton.org/bpmn/reference.html#activities-subprocess) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+*   [Subprocesses](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)

docs/documentation/reference/bpmn20/subprocesses/event-subprocess.md

@@ -101,4 +101,4 @@ These two differences can help you decide whether a boundary event or an embedde
 
 ## Additional Resources
 
-*   [Event subprocess](http://operaton.org/bpmn/reference.html#activities-event-subprocess) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+*   [Subprocesses](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)

docs/documentation/reference/bpmn20/tasks/business-rule-task.md

@@ -202,5 +202,5 @@ In addition to the above, a Business Rule Task can be implemented via the [Exter
 
 * [Decisions](../../../user-guide/process-engine/decisions/index.md)
 * [Service Tasks](./service-task.md)
-* [Tasks](http://operaton.org/bpmn/reference.html#activities-task) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
-* [Demo using Drools on the Business Rule Task](https://github.com/operaton/operaton-consulting/tree/master/one-time-examples/order-confirmation-rules)
+* [Tasks](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)
+* [DMN decision example](https://github.com/operaton/operaton-examples/tree/main/examples/dmn-decision)

docs/documentation/reference/bpmn20/tasks/receive-task.md

@@ -95,5 +95,5 @@ runtimeService.signal(execution.getId());
 
 ## Additional Resources
 
-* [Tasks](http://operaton.org/bpmn/reference.html#activities-task) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+* [Tasks](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)
 * [Message Receive Events](../events/message-events.md)

docs/documentation/reference/bpmn20/tasks/service-task.md

@@ -163,5 +163,5 @@ To declare a Service Task to be handled externally, the attribute `operaton:type
 
 ## Additional Resources
 
-* [Tasks](http://operaton.org/bpmn/reference.html#activities-task) in the [BPMN Modeling Reference](http://operaton.org/bpmn/reference.html) section
+* [Tasks](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)
 * [How to call a Webservice from BPMN](http://www.bpm-guide.de/2010/12/09/how-to-call-a-webservice-from-bpmn/). Please note that this article is outdated. However, it is still valid regarding how you would call a Web Service using the process engine.

docs/documentation/reference/bpmn20/tasks/task-markers.md

@@ -204,5 +204,5 @@ To declare an activity to be a compensation handler, we need to set the attribut
 
 ## Additional Resources
 
-* [Tasks](http://operaton.org/bpmn/reference.html#activities-task) in the [BPMN 2.0 Modeling Reference](http://operaton.org/bpmn/reference.html)
+* [Tasks](./index.md) in the [BPMN 2.0 Implementation Reference](../index.md)
 * [Transaction Subprocess](../subprocesses/transaction-subprocess.md)

docs/documentation/reference/deployment-descriptors/processes-xml.md

@@ -24,7 +24,7 @@ The namespace for the processes.xml file is `http://www.operaton.org/schema/1.0/
 
 ## Empty processes.xml
 
-The `processes.xml` may be left blank (can be empty). In this case, default values are used. See the [Empty processes.xml](../../user-guide/process-applications/the-processes-xml-deployment-descriptor.md#empty-processesxml) section of the [User Guide](../../user-guide/index.md) for more details.
+The `processes.xml` may be left blank (can be empty). In this case, default values are used. See the [Empty processes.xml](../../user-guide/process-applications/the-processes-xml-deployment-descriptor.md#empty-processes-xml) section of the [User Guide](../../user-guide/index.md) for more details.
 
 
 ## Example

docs/documentation/reference/deployment-descriptors/tags/process-engine.mdx

@@ -5,6 +5,31 @@ sidebar_position: 50
 
 ---
 
+<RegisterAnchors ids={[
+  'enableXxeProcessing',
+  'ensureJobDueDateNotNull',
+  'enable-historic-instance-permissions',
+  'jdbcBatchProcessing',
+  'jobExecutorPriorityRangeMin',
+  'jobExecutorPriorityRangeMax',
+  'invocations-per-batch-job-by-batch-type',
+  'javaSerializationFormatEnabled',
+  'deserializationTypeValidationEnabled',
+  'webappsAuthenticationLoggingEnabled',
+  'queryMaxResultsLimit',
+  'dmnFeelEnableLegacyBehavior',
+  'dmnFeelCustomFunctionProviders',
+  'skipOutputMappingOnCanceledActivities',
+  'configureScriptEngineHostAccess',
+  'enableScriptEngineLoadExternalResources',
+  'enableScriptEngineNashornCompatibility',
+  'exception-codes',
+  'logEntriesPerSyncOperationLimit',
+  'historyTimeToLive',
+  'historytimetolive',
+  'enforceHistoryTimeToLive',
+]} />
+
 
 The process engine configuration can be placed in both [processes.xml](../processes-xml.md) and the [bpm-platform.xml](../bpm-platform-xml.md) files. If the process engine is configured in either or both of those files, it will be bootstrapped by the Operaton infrastructure and be made available through `BpmPlatform.getProcessEngineService().getProcessEngine("name of process engine")`.
 
@@ -367,8 +392,8 @@ The following is a list with the most commonly used process engine configuration
     </td>
   </tr>
 
-  <tr>
-      <td><code>enableXxeProcessing</code></td>
+  <tr id="enableXxeProcessing">
+    <td><code>enableXxeProcessing</code></td>
       <td>Boolean</td>
       <td>
         If set to <code>true</code>, enables XML eXternal Entity (XXE) Processing. When disabled, it provides protection against XXE Processing attacks.
@@ -844,7 +869,7 @@ The following is a list with the most commonly used process engine configuration
     <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.
+        Set to <code>true</code>, to enable a <a href="/docs/documentation/user-guide/process-engine/password-policy/">password policy</a> for users that are managed by the engine. If a <a href="/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="/docs/documentation/user-guide/process-engine/password-policy/#built-in-password-policy">built-in password policy</a> is activated.
     </td>
   </tr>
 
@@ -1221,8 +1246,8 @@ The following is a list with the most commonly used process engine configuration
         in the User Guide.
     </td>
   </tr>
-  <tr id="historytimetolive">
-    <td><code>historyTimeToLive</code></td>
+  <tr id="historyTimeToLive">
+    <td><a id="historytimetolive"></a><code>historyTimeToLive</code></td>
     <td>String</td>
     <td>
             Defines history time to live for process definitions and decision definitions if no other value is defined.

docs/documentation/reference/forms/embedded-forms/controls/bpmn-buttons.md

@@ -10,7 +10,7 @@ menu:
 
 ---
 
-These buttons can be used to trigger error and escalation events in user tasks. They will submit all entered values and activate the corresponding boundary event. To learn more about error and escalation events, see our section about [events](https://docs.operaton.org/docs/documentation/reference/bpmn20/events/).
+These buttons can be used to trigger error and escalation events in user tasks. They will submit all entered values and activate the corresponding boundary event. To learn more about error and escalation events, see our section about [events](/docs/documentation/reference/bpmn20/events/).
 
 ## Error
 
@@ -30,4 +30,4 @@ In a similar manner to the error button, an escalation button can be bound to an
 
 ```html
 <button cam-escalation-code="bpmn-escalation-123" />
-```
+```

docs/documentation/user-guide/model-api/bpmn-model-api/fluent-builder-api.md

@@ -336,4 +336,4 @@ overlapping elements in the diagram.
 
 Branches of gateways are placed one below the other. Auto layout is not provided, therefore the elements of different branches may overlap.
 
-[multi-instance]: ../../../../reference/bpmn20/tasks/task-markers/#multiple-instance
+[multi-instance]: ../../../reference/bpmn20/tasks/task-markers.md#multiple-instance

docs/documentation/user-guide/operaton-bpm-run.md

@@ -9,7 +9,7 @@ This guide gives an introduction to Operaton Run, a pre-packaged, lightweight di
 
 ## Prerequisites and audience
 
-To use this guide, you should at least know what Operaton is and what it does. Check out the [Get Started guides](https://docs.operaton.org/get-started/quick-start/) if you have never used Operaton before. The [Installation guide](../installation/operaton-bpm-run.md) is also worth looking at if you are completely new to Operaton.
+To use this guide, you should at least know what Operaton is and what it does. Check out the [Get Started guides](/docs/get-started/quick-start/) if you have never used Operaton before. The [Installation guide](../installation/operaton-bpm-run.md) is also worth looking at if you are completely new to Operaton.
 
 This guide will teach you about Operaton Run and how to configure it. It can serve as a reference page for configuration and operation options. It will not give you a step-by-step guide on how to install Operaton Run. Head over to the [Installation guide](../installation/operaton-bpm-run.md) for details on how to install and start Operaton Run.
 
@@ -26,7 +26,7 @@ Operaton Run is a full distribution of Operaton. It includes:
 
 ## Starting with Operaton Run
 
-To start with Operaton Run, download the [distribution](https://downloads.camunda.cloud/release/operaton-bpm/run/) and unpacking it. You will find the following structure:
+To start with Operaton Run, download the [distribution](https://github.com/operaton/operaton/releases/latest) and unpack it. You will find the following structure:
 
 ```
 operaton-bpm-run
@@ -323,7 +323,7 @@ Operaton Run also supports configuration options for customizing the deployment.
             <li>When set to <code>false</code>, all deployments will be deployed without filtering their resources.</li>
           </ul>
           The property can be useful for controlling the deployment behaviour of the engine in case of restarts, similar to the
-          <a href="..user-guide/spring-framework-integration/deployment">Spring Framework Integration</a>
+          <a href="./spring-framework-integration/deployment.md">Spring Framework Integration</a>
       </td>
       <td><code>true</code></td>
   </tr>