BPMN用户指南(9-18)
文章平均质量分 93
Flowable 6.6.0 BPMN用户指南 -9-18
月满闲庭
资深IT工作者
展开
-
Flowable 6.6.0 BPMN用户指南 -18 Tooling - 18.2 Maven原型(archetypes)
18.2 Maven原型(archetypes)18.2.1 创建测试用例During development, sometimes it is helpful to create a small test case to test an idea or a feature, before implementing it in the real application. This helps to isolate the subject under test. JUnit test cases are原创 2021-01-06 05:58:39 · 181 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 -18 Tooling - 18.1 JMX(3-5)
18.1.3 属性与操作Here is a list available attributes and operations at this moment. This list may extend in future releases based on needs.这里列出了目前可用的属性和操作。此列表可能会根据需要在将来的版本中扩展。MBean类型名称描述ProcessDefinitionsMBeanAttributeprocessDefinitions作为字符串列表原创 2021-01-06 05:58:17 · 141 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 -18 Tooling - 18.1 JMX(1,2)
18 Tooling18.1 JMX18.1.1 简介It is possible to connect to Flowable engine using standard Java Management Extensions (JMX) technology in order to get information or to change its behavior. Any standard JMX client can be used for that purpose. Enabling and原创 2021-01-05 06:42:09 · 283 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.13 日志记录会话[实验性]
17.13 日志记录会话[实验性]Added in 6.5.0, Logging sessions allow you to collect information about process execution even if an exception causes the transaction to be rolled back. This is enabled by providing a LoggingListener implementation to the engine configura原创 2021-01-05 06:41:32 · 306 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.12 安全脚本(Secure Scripting)
17.12 安全脚本(Secure Scripting)By default, when using a script task, the script that is executed has similar capabilities as a Java delegate. It has full access to the JVM, can run forever (due to infinite loops) or use up a lot of memory. However, Java dele原创 2021-01-05 06:40:56 · 406 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.10 事件日志记录 17.11 禁用批量插入
17.10 事件日志记录(Event logging)An event logging mechanism has been introduced. The logging mechanism builds upon the general-purpose event mechanism of the Flowable engine and is disabled by default. The idea is that the events originating from the engine are原创 2021-01-05 06:40:18 · 559 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.8、9
17.8 重写标准SessionFactory实现自定义身份管理If you do not want to use a full ProcessEngineConfigurator implementation like in the LDAP integration, but still want to plug in your custom identity management framework, then you can also override the IdmIdentityServiceI原创 2021-01-05 06:39:58 · 418 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.7 高级查询API:运行时和历史任务查询之间的无缝切换
17.7 高级查询API:运行时和历史任务查询之间的无缝切换One core component of any BPM user interface is the task list. Typically, end users work on open, runtime tasks, filtering their inbox with various setting. Often also the historic tasks need to be displayed in those lists, w原创 2021-01-05 06:39:21 · 533 阅读 · 2 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.6 采用ProcessEngineConfigurator 进行高级的流程引擎配置
17.6 采用ProcessEngineConfigurator 进行高级的流程引擎配置(Advanced Process Engine configuration with a ProcessEngineConfigurator)An advanced way of hooking into the process engine configuration is through the use of a ProcessEngineConfigurator. The idea is that an imp原创 2021-01-05 06:39:03 · 552 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.5 执行自定义SQL(Execute custom SQL)
17.5 执行自定义SQL(Execute custom SQL)The Flowable API allows for interacting with the database using a high level API. For example, for retrieving data the Query API and the Native Query API are powerful in its usage. However, for some use cases they might no原创 2021-01-05 06:38:12 · 1276 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.3、4
17.3 用于高并发的UUID ID生成器In some (very) high concurrency load cases, the default ID generator may cause exceptions due to not being able to fetch new ID blocks quickly enough. Every process engine has one ID generator. The default ID generator reserves a bloc原创 2021-01-05 06:37:40 · 540 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.2 与流程解析挂钩
17.2 与流程解析挂钩(Hooking into process parsing)A BPMN 2.0 XML needs to be parsed to the Flowable internal model to be executed on the Flowable engine. This parsing happens during a deployment of the process or when a process is not found in memory, and the XML原创 2021-01-05 06:37:16 · 380 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.1 异步执行器(3)
17.1.3 基于异步执行器的消息队列When reading the async executor design section, it becomes clear that the architecture is inspired by message queues. The async executor is designed in such a way that a message queue can easily be used to take over the job of the threa原创 2021-01-04 08:46:02 · 706 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.1 异步执行器(1)
17 高级用例The following sections cover advanced use cases of Flowable, that go beyond typical execution of BPMN 2.0 processes. As such, a certain proficiency and experience with Flowable is advised to understand the topics described here.下面几节介绍了Flowable的高级用原创 2021-01-04 08:45:46 · 1230 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 17 高级用例 - 17.1 异步执行器(2)
17.1.2 异步执行器配置The async executor is a highly configurable component. It’s always recommended to look into the default settings of the async executor and validate if they match the requirements of your processes.异步执行器是一个高度可配置的组件。始终建议查看异步执行器的默认设置,并验证它们是否符合原创 2021-01-04 08:45:27 · 538 阅读 · 0 评论 -
原创 Flowable 6.6.0 BPMN用户指南 - 16 LDAP集成
16 LDAP集成Companies often already have a user and group store in the form of an LDAP system. Flowable offers an out-of-the-box solution for easily configuring how Flowable should connect with an LDAP system.In earlier versions, it was already possible to原创 2021-01-04 08:45:11 · 667 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 15 CDI集成 - 15.2 使用CDI的上下文流程执行(5-7)
15.2.5 注入流程变量(Injecting Process Variables)Process variables are available for injection. flowable-cdi supportstype-safe injection of @BusinessProcessScoped beans using @Inject [additional qualifiers] Type fieldNameunsafe injection of other process vari原创 2021-01-04 08:44:54 · 832 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 15 CDI集成 - 15.2 使用CDI的上下文流程执行(2-4)
15.2.2 通过声明控制流程(Declaratively controlling the Process)Flowable-cdi allows declaratively starting process instances and completing tasks using annotations. The @org.flowable.cdi.annotation.StartProcess annotation allows to start a process instance either b原创 2021-01-04 08:44:35 · 282 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 15 CDI集成 - 15.2 使用CDI的上下文流程执行(1)
15.2 使用CDI的上下文流程执行(Contextual Process Execution with CDI)In this section we briefly look at the contextual process execution model used by the Flowable CDI extension. A BPMN business process is typically a long-running interaction, comprised of both user原创 2021-01-04 08:44:17 · 312 阅读 · 2 评论 -
Flowable 6.6.0 BPMN用户指南 - 15 CDI集成 - 15.1 设置flowable-cdi
15 CDI集成The flowable-cdi modules leverages both the configurability of Flowable and the extensibility of cdi. The most prominent features of flowable-cdi are:flowable-cdi模块充分利用了Flowable的可配置性和cdi的可扩展性。flowable-cdi最突出的特点是:Support for @BusinessProcessScop原创 2021-01-04 08:44:02 · 508 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 14 REST API
14 REST API14.1 Flowable REST通用原则14.1.1 安装和认证Flowable includes a REST API to the Flowable engine that can be installed by deploying the flowable-rest.war file to a servlet container like Apache Tomcat. However, it can also be used in another web-applica原创 2021-01-04 08:43:36 · 877 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 13 身份管理(Identity management)
13 身份管理(Identity management)Starting from Flowable V6, the identity management (IDM) component has been extracted from the flowable-engine module and the logic moved to several separate modules: flowable-idm-api, flowable-idm-engine, flowable-idm-spring a原创 2021-01-04 08:43:14 · 837 阅读 · 1 评论 -
Flowable 6.6.0 BPMN用户指南 - 12 历史(History)- 12.4 用于审计的历史、 12.5 历史清理
12.4 用于审计的历史When configuring at least audit level for configuration. Then all properties submitted through methods FormService.submitStartFormData(String processDefinitionId, Map<String, String> properties) and FormService.submitTaskFormData(String原创 2021-01-03 07:37:28 · 986 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 12 历史(History)- 12.2 历史配置、12.3 异步历史配置
12.2 历史配置The history level can be configured programmatically, using the enum org.flowable.engine.impl.history.HistoryLevel (or HISTORY constants defined on ProcessEngineConfiguration for versions prior to 5.11):可以以编程方式配置历史级别,即使用枚举org.flowable.engine.imp原创 2021-01-03 07:33:27 · 1390 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 12 历史(History)- 12.1 查询历史
12 历史(History)History is the component that captures what happened during process execution and stores it permanently. In contrast to the runtime data, the history data will remain present in the DB also after process instances have completed.There are 6原创 2021-01-03 07:30:03 · 1809 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 11 JPA - 11.2 配置
11.2 配置To be able to use JPA-entities, the engine must have a reference to an EntityManagerFactory. This can be done by configuring a reference or by supplying a persistence-unit name. JPA-entities used as variables will be detected automatically and will原创 2021-01-03 07:21:49 · 254 阅读 · 1 评论 -
Flowable 6.6.0 BPMN用户指南 - 11 JPA - 11.3 用法(1)
11.3 用法11.3.1 简单示例Examples for using JPA variables can be found in JPAVariableTest in the Flowable source code. We’ll explain JPAVariableTest.testUpdateJPAEntityValues step by step.First of all, we create an EntityManagerFactory for our persistence-unit原创 2021-01-03 07:21:36 · 152 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 11 JPA - 11.3 用法(2~3)
11.3.2 查询JPA流程变量You can query for ProcessInstances and Executions that have a certain JPA-entity as variable value. Note that only variableValueEquals(name, entity) is supported for JPA-Entities on ProcessInstanceQuery and ExecutionQuery. Methods variable原创 2021-01-03 07:21:22 · 226 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 - 11 JPA - 11.1 要求
11 JPAYou can use JPA-Entities as process variables, allowing you to:Updating existing JPA-entities based on process variables that can be filled in on a form in a userTask or generated in a serviceTask.Reusing existing domain model without having to w原创 2021-01-03 07:21:06 · 286 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 -10 流程实例迁移 -10.2~4
10.2 使用活动迁移映射进行迁移In the simple example user task 1 was automatically mapped to the same user task in the new process definition version. But in some cases the current activity of a running process instance doesn’t exist anymore in the new process definiti原创 2021-01-02 07:53:49 · 547 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 -10 流程实例迁移 - 10.1 简单示例
10 流程实例迁移When process definitions are updated with new versions, the question arises what should be done with already running process instances that are using older versions of the process definition. In case running process instances should be migrated t原创 2021-01-02 07:53:28 · 1183 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 -9 表单 - 9.3 外部表单渲染
9.3 外部表单渲染(External form rendering)The API also allows for you to perform your own task form rendering outside of the Flowable Engine. These steps explain the hooks that you can use to render your task forms yourself.Essentially, all the data that’s need原创 2021-01-02 07:53:14 · 1759 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 -9 表单 - 9.2 表单属性
9.2 表单属性All information relevant to a business process is either included in the process variables themselves or referenced through the process variables. Flowable supports complex Java objects to be stored as process variables like Serializable objects,原创 2021-01-02 07:52:55 · 1520 阅读 · 0 评论 -
Flowable 6.6.0 BPMN用户指南 -9 表单 - 9.1 表单定义
9 表单(Forms)Flowable provides a convenient and flexible way to add forms for the manual steps of your business processes. We support two strategies to work with forms: Built-in form rendering with a form definition (created with the form designer) and exte原创 2021-01-02 07:52:12 · 1804 阅读 · 0 评论