v5.4.1

CRITICAL BUG
This release introduced issue #306 which may cause OutOfMemory errors while fetching child workflow IDs. We recommend to update to 5.6.0 as soon as possible.

Highlights

• Introduce BulkWorkflow which can be used or extended to handle mass of child workflows without overloading the system.
• Introduce new workflow instance state type wait. Child workflow instances automatically wake up the parent when the parent is in a wait state and the child enters an end state.
• Allow creating workflows via REST API with null activation time (by setting activate = false).
• Allow creating child workflows via REST API (by setting parentWorkflowId).

Details

• See BulkWorkflowTest and DemoBulkWorkflow for examples on how to use bulk workflows
• Support boxed primitives (Integer, Float etc) with @StateVar
• nFlow Explorer: Library updates to lodash 4.17.11, moment 2.24.0 and extend 3.0.2
  Earlier lodash versions had this security vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2018-16487
• Use select distinct when getting preserved actions while cleaning workflow instance history
• Dependency and plugin updates:
  • slf4j 1.7.26
  • spring 5.1.5.RELEASE
  • hamcrest 2.1
  • reactor.netty 0.8.5.RELEASE
  • swagger 1.5.22
  • mockito 2.24.5
  • io.dropwizard.metrics 4.0.5
  • mysql-connector-java 8.0.15
  • mssql-jdbc 7.2.1.jre8
  • hikaricp 3.3.1
  • maven-surefire 2.22.1
  • jetty 9.4.15.v20190215
  • h2 1.4.199
• Fix workflow history cleanup to keep the actions that hold the latest values of state variables
• nFlow Explorer: Custom content to workflow definition and workflow instance pages.
• nFlow Explorer: Executors page to use standard time formatting in tooltips
• nFlow netty: Add support for registering Spring ApplicationListeners
• nFlow jetty: Replace deprecated NCSARequestLog with CustomRequestLog
• Fix WorkflowLifecycle.stop() blocking forever if nflow.autostart=false and WorkflowLifecycle.start() not called