月满闲庭的博客

Flowable 6.6.0 表单用户指南点击下载《Flowable 6.6.0 表单用户指南》精编中文版目录1 配置（Configuration） 51.1 创建一个表单引擎（Creating a Form Engine） 51.2 FormEngineConfiguration bean 61.3 插入流程引擎（Plug into Process Engine） 71.4 数据库配置（Database configuration） 81.5 JNDI数据源配置（JNDI Datasour

《Flowable 6.6.0表单用户指南（Forms User Guide）》1 表单配置（Configuration）1.1创建一个表单引擎（Creating a Form Engine）1.2 FormEngineConfiguration bean1.3 插入流程引擎（Plug into Process Engine）1.4 数据库配置（Database configuration）1.5 JNDI数据源配置（JNDI Datasource Configuration）1.6 数据库.

The Flowable Form engine is structured in a very similar way to the Flowable process engine. As a result parts of the documentation have a resemblance with their process engine counterpart.The Flowable Form engine is configured through an XML file named f

3.3 单元测试（Unit testing）When integrating with Spring, forms can be tested very easily using the standard Flowable testing facilities. The following examples show how a form is tested in a typical Spring-based JUnit 4 and 5 tests:当与Spring集成时，可以使用标准的Flowable

3.2 自动资源部署（Automatic resource deployment）Spring integration also has a special feature for deploying resources. In the Form engine configuration, you can specify a set of resources. When the Form engine is created, all those resources will be scanned and

Spring 集成（Spring integration）While you can definitely use Flowable Form without Spring, we’ve provided some very nice integration features that are explained in this chapter.虽然您肯定可以使用没有Spring的Flowable表单，但是我们提供了一些非常好的集成特性，这些特性将在本章中介绍。3.1 FormEngineFactor

Flowable 6.6.0表单用户指南（Forms User Guide）2 Flowable表单API（The Flowable Form API）2.5 Web应用程序中的表单引擎（The Form engine in a web application）The FormEngine is a thread-safe class and can easily be shared among multiple threads. In a web application, this means it

Flowable 6.6.0表单用户指南（Forms User Guide）2 Flowable表单API（The Flowable Form API）2.4 单元测试（Unit testing）As Flowable Form is an embeddable Java engine, writing unit tests for Form definitions is as simple as writing regular unit tests.Flowable supports JUnit

Flowable 6.6.0表单用户指南（Forms User Guide）2 Flowable表单API（The Flowable Form API）2.3 查询API（Query API）There are two ways of querying data from the engine: The query API and native queries. The Query API allows you to program completely typesafe queries with a

2 Flowable表单API（The Flowable Form API）2.1 表单引擎API及服务（The Form Engine API and services）The Form engine API is the most common way of interacting with Flowable Form. The central starting point is the FormEngine, which can be created in several ways as desc

Flowable 6.6.0表单用户指南（Forms User Guide）2 Flowable表单API（The Flowable Form API）2.2 异常策略（Exception strategy）The base exception in Flowable is the org.flowable.engine.FlowableException, an unchecked exception. This exception can be thrown at all times by the

Flowable 6.6.0表单用户指南（Forms User Guide）1 配置（Configuration）1.8 日志（Logging）All logging (flowable, spring, mybatis, …) is routed through SLF4J and allows the selection of the logging-implementation of your choice.所有日志记录（flowable、spring、mybatis等）都通过SLF4J路由，

Flowable 6.6.0表单用户指南（Forms User Guide）1 配置（Configuration）1.7 部署缓存配置（Deployment cache configuration）All definitions are cached (after they’re parsed) to avoid hitting the database every time a form is needed and because form data doesn’t change. By defau

Flowable 6.6.0表单用户指南（Forms User Guide）1 配置（Configuration）1.6 数据库相关（Database）1.6.1支持的数据库（Supported databases）Listed below are the types (case sensitive!) that Flowable uses to refer to databases.下面列出的是Flowable用于引用数据库类型（区分大小写！）。 Flowable Fo

By default, the database configuration for Flowable Form is contained within the db.properties files in the WEB-INF/classes of each web application. This isn’t always ideal because it requires users to either modify the db.properties in the Flowable source

There are two ways to configure the database that the Flowable Form engine will use. The first option is to define the JDBC properties of the database:有两种方法可以配置Flowable Form引擎将使用的数据库。第一个选项是定义数据库的JDBC属性：jdbcUrl: JDBC URL of the database.jdbcDriver: impl

In addition to running in standalone mode, it’s also possible to plug the Form engine into the Process engine. This makes the Process engine aware of it and other engines. This enables, for example, deploying artifacts containing not only BPMN models, but

The flowable.form.cfg.xml must contain a bean that has the id ‘formEngineConfiguration’.这个flowable.form.cfg.xml必须包含id为“formEngineConfiguration”的bean。 <bean id="formEngineConfiguration" class="org.flowable.form.engine.impl.cfg.StandaloneFormEngineConfi