Merge branch 'main' of github.com:flowable/flowable-engine

.gitignore

@@ -9,15 +9,10 @@ target
 .DS_Store
 .vscode
 *.bpmn/
-/userguide/src/en/index.html
-userguide/src/en/output/
 migration.html
 /modules/**/bin
 modules/flowable-app-rest/.extract
 modules/flowable-app-rest/src/main/resources/static/docs/specfile
-userguide-dmn/src/en/output
-userguide-form/src/en/output
-userguide-cmmn/src/en/output
 docker/all-in-one/assets
 k8s/flowable/charts
 requirements.lock

docs/docusaurus/docs/bpmn/ch03-Configuration.md

@@ -374,13 +374,6 @@ Customizing the configuration of history storage is optional. This allows you to
 
     <property name="history" value="audit" />
 
-## Async history configuration
-
-\[Experimental\] Since Flowable 6.1.0 the async history feature has been added. When async history is enabled, the historic data will be persisted by a history job executor, instead of synchronous persistence as part of the runtime execution persistence.
-See [async history configuration](bpmn/ch10-History.md#async-history-configuration) for more details.
-
-    <property name="asyncHistoryEnabled" value="true" />
-
 ## Exposing configuration beans in expressions and scripts
 
 By default, all beans that you specify in the flowable.cfg.xml configuration or in your own Spring configuration file are available to expressions and scripts. If you want to limit the visibility of beans in your configuration file, you can configure a property called beans in your process engine configuration. The beans property in ProcessEngineConfiguration is a map. When you specify that property, only beans specified in that map will be visible to expressions and scripts. The exposed beans will be exposed with the names as you specify in the map.

docs/docusaurus/docs/bpmn/ch05a-Spring-Boot.md

@@ -540,7 +540,7 @@ Here is a list of configuration properties that the Flowable Spring Boot support
 
     # Process https://github.com/flowable/flowable-engine/tree/main/modules/flowable-spring-boot/flowable-spring-boot-starters/flowable-spring-boot-autoconfigure/src/main/java/org/flowable/spring/boot/process/FlowableProcessProperties.java
     flowable.process.definition-cache-limit=-1 # The maximum amount of process definitions available in the process definition cache. Per default it is -1 (all process definitions).
-    flowable.process.enable-safe-xml=true # Enables extra checks on the BPMN xml that is parsed. See https://www.flowable.org/docs/userguide/index.html#advanced.safe.bpmn.xml. Unfortunately, this feature is not available on some platforms (JDK 6, JBoss), hence you need to disable if your platform does not allow the use of StaxSource during XML parsing.
+    flowable.process.enable-safe-xml=true # Enables extra checks on the BPMN xml that is parsed. Unfortunately, this feature is not available on some platforms, hence you need to disable if your platform does not allow the use of StaxSource during XML parsing.
     flowable.process.servlet.load-on-startup=-1 # Load on startup of the Process dispatcher servlet.
     flowable.process.servlet.name=Flowable BPMN Rest API # The name of the Process servlet.
     flowable.process.servlet.path=/process-api # The context path for the Process rest servlet.
@@ -558,7 +558,7 @@ Here is a list of configuration properties that the Flowable Spring Boot support
     # CMMN https://github.com/flowable/flowable-engine/tree/main/modules/flowable-spring-boot/flowable-spring-boot-starters/flowable-spring-boot-autoconfigure/src/main/java/org/flowable/spring/boot/cmmn/FlowableCmmnProperties.java
     flowable.cmmn.deploy-resources=true # Whether to perform deployment of resources, default is 'true'.
     flowable.cmmn.deployment-name=SpringBootAutoDeployment # The name of the deployment for the CMMN resources.
-    flowable.cmmn.enable-safe-xml=true # Enables extra checks on the DMN xml that is parsed. See https://www.flowable.org/docs/userguide/index.html#advanced.safe.bpmn.xml. Unfortunately, this feature is not available on some platforms (JDK 6, JBoss), hence you need to disable if your platform does not allow the use of StaxSource during XML parsing.
+    flowable.cmmn.enable-safe-xml=true # Enables extra checks on the DMN xml that is parsed. Unfortunately, this feature is not available on some platforms, hence you need to disable if your platform does not allow the use of StaxSource during XML parsing.
     flowable.cmmn.enabled=true # Whether the CMMN engine needs to be started.
     flowable.cmmn.resource-location=classpath*:/cases/ # The location where the CMMN resources are located.
     flowable.cmmn.resource-suffixes=**.cmmn,**.cmmn11,**.cmmn.xml,**.cmmn11.xml # The suffixes for the resources that need to be scanned.
@@ -578,7 +578,7 @@ Here is a list of configuration properties that the Flowable Spring Boot support
     # DMN https://github.com/flowable/flowable-engine/tree/main/modules/flowable-spring-boot/flowable-spring-boot-starters/flowable-spring-boot-autoconfigure/src/main/java/org/flowable/spring/boot/dmn/FlowableDmnProperties.java
     flowable.dmn.deploy-resources=true # Whether to perform deployment of resources, default is 'true'.
     flowable.dmn.deployment-name=SpringBootAutoDeployment # The name of the deployment for the dmn resources.
-    flowable.dmn.enable-safe-xml=true # Enables extra checks on the DMN xml that is parsed. See https://www.flowable.org/docs/userguide/index.html#advanced.safe.bpmn.xml. Unfortunately, this feature is not available on some platforms (JDK 6, JBoss), hence you need to disable if your platform does not allow the use of StaxSource during XML parsing.
+    flowable.dmn.enable-safe-xml=true # Enables extra checks on the DMN xml that is parsed. Unfortunately, this feature is not available on some platforms, hence you need to disable if your platform does not allow the use of StaxSource during XML parsing.
     flowable.dmn.enabled=true # Whether the dmn engine needs to be started.
     flowable.dmn.history-enabled=true # Whether the history for the DMN engine should be enabled.
     flowable.dmn.resource-location=classpath*:/dmn/ # The location where the dmn resources are located.

docs/docusaurus/docs/bpmn/ch13-Applications.md

@@ -13,7 +13,7 @@ See [The Executable Jar Format](https://docs.spring.io/spring-boot/docs/current/
 
 As mentioned before, the application can be deployed on a Tomcat server, and to get started this is probably the easiest approach when additional configuration settings are used. For this installation guide we’ll describe the installation of the application in a Tomcat server.
 
-1.  Download a recent stable version of [Apache Tomcat](http://tomcat.apache.org). It has to be Jakarta Servlet 6 compliant
+1.  Download a recent stable version of [Apache Tomcat](http://tomcat.apache.org). It has to be Jakarta Servlet 6 compliant (Tomcat 10 or later)
 
 2.  Download the latest stable [Flowable 7 version](http://www.flowable.org/downloads.html).
 

docs/docusaurus/docs/oss-introduction.md

@@ -21,7 +21,7 @@ The distribution contains most of the sources as JAR files. The source code for
 
 ### JDK 17+
 
-Flowable runs on a JDK higher than or equal to version 8. Go to [Oracle Java SE downloads](http://www.oracle.com/technetwork/java/javase/downloads/index.html) and click on button "Download JDK". There are installation instructions on that page as well. To verify that your installation was successful, run java -version on the command line. That should print the installed version of your JDK.
+Flowable runs on a JDK higher than or equal to version 17. Go to [Oracle Java SE downloads](http://www.oracle.com/technetwork/java/javase/downloads/index.html) and click on button "Download JDK". There are installation instructions on that page as well. To verify that your installation was successful, run java -version on the command line. That should print the installed version of your JDK.
 
 ### Modeling