Details
-
Type:
Task
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.0.0, CP-5.0.0
-
Fix Version/s: 5.1.0
-
Component/s: Components
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | ||||
|---|---|---|---|---|
|
||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Description |
Following the major event about *Activiti* project occurring in October 2016, the creation of fork *Flowable*, we decides to join this new project *Flowable* migrating our BPMN 2.0 service engine to this branch.
So, a the new SE "Flowable" will replace the SE "Activiti" in the Petals Enterprise Edition. The SE "Activiti" will be moved in the community edition, and will be maintained to run as-is on next few versions of Petals container. In the same time, we move to the version 6 of Flowable. |
Following the major event about *Activiti* project occurring in October 2016, the creation of fork *Flowable*, we decides to join this new project *Flowable* migrating our BPMN 2.0 service engine to this branch.
So, a the new SE "Flowable" will replace the SE "Activiti" in the Petals Enterprise Edition. The SE "Activiti" will be moved in the community edition, and will be maintained to run as-is on next few versions of Petals container. In the same time, we move to the version 6 of Flowable. |
| Link |
This issue depends on |
| Description |
Following the major event about *Activiti* project occurring in October 2016, the creation of fork *Flowable*, we decides to join this new project *Flowable* migrating our BPMN 2.0 service engine to this branch.
So, a the new SE "Flowable" will replace the SE "Activiti" in the Petals Enterprise Edition. The SE "Activiti" will be moved in the community edition, and will be maintained to run as-is on next few versions of Petals container. In the same time, we move to the version 6 of Flowable. |
Following the major event about *Activiti* project occurring in October 2016, the creation of fork *Flowable*, we decides to join this new project *Flowable* migrating our BPMN 2.0 service engine to this branch.
So, a the new SE "Flowable" will replace the SE "Activiti" in the Petals Enterprise Edition. The SE "Activiti" will be moved in the community edition, and will be maintained to run as-is on next few versions of Petals container. In the same time, we move to the version 6 of Flowable that have following improvements: Abstract persistence layer, enabling use of relational or non-relational data sources: http://www.jorambarrez.be/blog/2016/11/02/running-flowable-on-cockroachdb/ * 1-to-1 mapping of BPMN model to executable instruction set * Simplified execution tree, enabling easier analysis and manipulation of in-flight processes * Single agenda for process execution plans * Queue-based job execution: http://www.jorambarrez.be/blog/2016/07/20/message-queue-async-executor-benchmark/ * Ad hoc Sub Processes: http://bpmn20inaction.blogspot.co.uk/2016/02/activiti-6-adds-ad-hoc-sub-process.html |
| Description |
Following the major event about *Activiti* project occurring in October 2016, the creation of fork *Flowable*, we decides to join this new project *Flowable* migrating our BPMN 2.0 service engine to this branch.
So, a the new SE "Flowable" will replace the SE "Activiti" in the Petals Enterprise Edition. The SE "Activiti" will be moved in the community edition, and will be maintained to run as-is on next few versions of Petals container. In the same time, we move to the version 6 of Flowable that have following improvements: Abstract persistence layer, enabling use of relational or non-relational data sources: http://www.jorambarrez.be/blog/2016/11/02/running-flowable-on-cockroachdb/ * 1-to-1 mapping of BPMN model to executable instruction set * Simplified execution tree, enabling easier analysis and manipulation of in-flight processes * Single agenda for process execution plans * Queue-based job execution: http://www.jorambarrez.be/blog/2016/07/20/message-queue-async-executor-benchmark/ * Ad hoc Sub Processes: http://bpmn20inaction.blogspot.co.uk/2016/02/activiti-6-adds-ad-hoc-sub-process.html |
Following the major event about *Activiti* project occurring in October 2016, the creation of fork *Flowable*, we decides to join this new project *Flowable* migrating our BPMN 2.0 service engine to this branch.
So, a the new SE "Flowable" will replace the SE "Activiti" in the Petals Enterprise Edition. The SE "Activiti" will be moved in the community edition, and will be maintained to run as-is on next few versions of Petals container. In the same time, we move to the version 6 of Flowable that have following improvements: * Abstract persistence layer, enabling use of relational or non-relational data sources: http://www.jorambarrez.be/blog/2016/11/02/running-flowable-on-cockroachdb/ * 1-to-1 mapping of BPMN model to executable instruction set * Simplified execution tree, enabling easier analysis and manipulation of in-flight processes * Single agenda for process execution plans * Queue-based job execution: http://www.jorambarrez.be/blog/2016/07/20/message-queue-async-executor-benchmark/ * Ad hoc Sub Processes: http://bpmn20inaction.blogspot.co.uk/2016/02/activiti-6-adds-ad-hoc-sub-process.html |
| Link |
This issue depends on |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.1.0 [ 10699 ] | |
| Resolution | Fixed [ 1 ] |
| Description |
Following the major event about *Activiti* project occurring in October 2016, the creation of fork *Flowable*, we decides to join this new project *Flowable* migrating our BPMN 2.0 service engine to this branch.
So, a the new SE "Flowable" will replace the SE "Activiti" in the Petals Enterprise Edition. The SE "Activiti" will be moved in the community edition, and will be maintained to run as-is on next few versions of Petals container. In the same time, we move to the version 6 of Flowable that have following improvements: * Abstract persistence layer, enabling use of relational or non-relational data sources: http://www.jorambarrez.be/blog/2016/11/02/running-flowable-on-cockroachdb/ * 1-to-1 mapping of BPMN model to executable instruction set * Simplified execution tree, enabling easier analysis and manipulation of in-flight processes * Single agenda for process execution plans * Queue-based job execution: http://www.jorambarrez.be/blog/2016/07/20/message-queue-async-executor-benchmark/ * Ad hoc Sub Processes: http://bpmn20inaction.blogspot.co.uk/2016/02/activiti-6-adds-ad-hoc-sub-process.html |
Following the major event about *Activiti* project occurring in October 2016, the creation of fork *Flowable*, we decides to join this new project *Flowable* migrating our BPMN 2.0 service engine to this branch.
So, the new SE "Flowable" will replace the SE "Activiti" in the Petals Enterprise Edition. The SE "Activiti" will be moved in the community edition, and will be maintained to run as-is on next few versions of Petals container. In the same time, we move to the version 6 of Flowable that have following improvements: * Abstract persistence layer, enabling use of relational or non-relational data sources: http://www.jorambarrez.be/blog/2016/11/02/running-flowable-on-cockroachdb/ * 1-to-1 mapping of BPMN model to executable instruction set * Simplified execution tree, enabling easier analysis and manipulation of in-flight processes * Single agenda for process execution plans * Queue-based job execution: http://www.jorambarrez.be/blog/2016/07/20/message-queue-async-executor-benchmark/ * Ad hoc Sub Processes: http://bpmn20inaction.blogspot.co.uk/2016/02/activiti-6-adds-ad-hoc-sub-process.html |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Replaced in trunk