P6 Core 6.0.0-alpha-5
Release date: Tuesday, 12th of July, 2019
Documentation can be found here.
This is a major release that introduces many breaking changes. It is highly recommended that you carefully read the migration guide.
Failover Mode for P6 Core¶
Starting this release, two P6 Core nodes can target the same database within a single instance in “active/passive” mode for failover. More information can be found here.
P6 Sync Endpoints & Documentation¶
P6 Sync was dramatically enhanced and is nearing the release of a
You can find the documentation of P6 Sync here.
Support for Ethereum was revamped and the underlying
Web3j library was upgraded from
Swagger support was upgraded to support the latest Open API spec and work with the latest version of Swagger UI. Therefore, the Swagger UI no longer ships with P6 Core. This effort also included upgrading to the latest version of Jetty.
Transaction DSL Simplified¶
To reduce the learning curve for newcomers, terms such as
project were replaced by
Also, the default data model is no longer
New JDBC Connection Pool¶
p6 DSL Binding Introduced¶
To avoid clashes between local variable names and DSL bindings, an all encompassing DSL binding
p6 was introduced.
Hence, you should prefix all your DSL calls with
Cluster and Concept Renamed, Item Table Partitioned¶
The notion of
cluster was renamed
concept was renamed
dataType to reduce the learning curve for newcomers.
In the database, the following tables were deleted:
item table was partitioned into 3 new tables:
transactionthat contains all transactions and workflows of all types.
table_datathat contains all reference table data.
logthat contains logs.
WFWorkItem Renamed to WorflowTask¶
This renaming applies everywhere.
Support for Old b2box Users Removed¶
B2BoxUserImpl class was deleted.
This release ports all bug fixes from the