You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docusaurus/docs/bpmn/ch03-Configuration.md
-7Lines changed: 0 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -374,13 +374,6 @@ Customizing the configuration of history storage is optional. This allows you to
374
374
375
375
<property name="history" value="audit" />
376
376
377
-
## Async history configuration
378
-
379
-
\[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.
380
-
See [async history configuration](bpmn/ch10-History.md#async-history-configuration) for more details.
## Exposing configuration beans in expressions and scripts
385
378
386
379
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.
Copy file name to clipboardExpand all lines: docs/docusaurus/docs/bpmn/ch05a-Spring-Boot.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -540,7 +540,7 @@ Here is a list of configuration properties that the Flowable Spring Boot support
540
540
541
541
# 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
542
542
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).
543
-
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.
543
+
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.
544
544
flowable.process.servlet.load-on-startup=-1 # Load on startup of the Process dispatcher servlet.
545
545
flowable.process.servlet.name=Flowable BPMN Rest API # The name of the Process servlet.
546
546
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
flowable.cmmn.deploy-resources=true # Whether to perform deployment of resources, default is 'true'.
560
560
flowable.cmmn.deployment-name=SpringBootAutoDeployment # The name of the deployment for the CMMN resources.
561
-
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.
561
+
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.
562
562
flowable.cmmn.enabled=true # Whether the CMMN engine needs to be started.
563
563
flowable.cmmn.resource-location=classpath*:/cases/ # The location where the CMMN resources are located.
564
564
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
flowable.dmn.deploy-resources=true # Whether to perform deployment of resources, default is 'true'.
580
580
flowable.dmn.deployment-name=SpringBootAutoDeployment # The name of the deployment for the dmn resources.
581
-
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.
581
+
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.
582
582
flowable.dmn.enabled=true # Whether the dmn engine needs to be started.
583
583
flowable.dmn.history-enabled=true # Whether the history for the DMN engine should be enabled.
584
584
flowable.dmn.resource-location=classpath*:/dmn/ # The location where the dmn resources are located.
Copy file name to clipboardExpand all lines: docs/docusaurus/docs/bpmn/ch13-Applications.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ See [The Executable Jar Format](https://docs.spring.io/spring-boot/docs/current/
13
13
14
14
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.
15
15
16
-
1. Download a recent stable version of [Apache Tomcat](http://tomcat.apache.org). It has to be Jakarta Servlet 6 compliant
16
+
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)
17
17
18
18
2. Download the latest stable [Flowable 7 version](http://www.flowable.org/downloads.html).
Copy file name to clipboardExpand all lines: docs/docusaurus/docs/oss-introduction.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ The distribution contains most of the sources as JAR files. The source code for
21
21
22
22
### JDK 17+
23
23
24
-
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.
24
+
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.
0 commit comments