From 66084386471d751eb69dad27ec7ab12246c77c7b Mon Sep 17 00:00:00 2001 From: Filip Hrisafov Date: Thu, 21 Sep 2023 08:57:53 +0200 Subject: [PATCH] Small doc changes for Flowable 7 release --- docs/docusaurus/docs/bpmn/ch03-Configuration.md | 7 ------- docs/docusaurus/docs/bpmn/ch13-Applications.md | 2 +- docs/docusaurus/docs/oss-introduction.md | 2 +- 3 files changed, 2 insertions(+), 9 deletions(-) diff --git a/docs/docusaurus/docs/bpmn/ch03-Configuration.md b/docs/docusaurus/docs/bpmn/ch03-Configuration.md index 5102fab842e..cd7965bb664 100644 --- a/docs/docusaurus/docs/bpmn/ch03-Configuration.md +++ b/docs/docusaurus/docs/bpmn/ch03-Configuration.md @@ -374,13 +374,6 @@ Customizing the configuration of history storage is optional. This allows you to -## 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. - - - ## 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. diff --git a/docs/docusaurus/docs/bpmn/ch13-Applications.md b/docs/docusaurus/docs/bpmn/ch13-Applications.md index f9b0b3aedb1..9e4ae9c8fb7 100644 --- a/docs/docusaurus/docs/bpmn/ch13-Applications.md +++ b/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). diff --git a/docs/docusaurus/docs/oss-introduction.md b/docs/docusaurus/docs/oss-introduction.md index 5ccb0b79ab0..fb727ab3f77 100644 --- a/docs/docusaurus/docs/oss-introduction.md +++ b/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