v5.3.3

Details

• Build using correct Java class version (was broken in 5.3.2)

v5.3.2

Highlights

Details

• Fix workflow history cleanup to work also with MySQL 5.7
• Upgraded Spring to version 5.1.4.RELEASE

v5.3.1

Details

• Expose workflow instance history cleanup delay in REST API and show it in Explorer (workflow definition -> settings)
• Preserve actions that are parent actions for child workflows in workflow history cleanup (otherwise cascade foreign key deletes also the children)

v5.3.0

Highlights

• Add experimental DB2 support

Breaking changes

• nFlow Datasource uses now underlying database specific Drivers instead of DataSources.
  Make a corresponding change, if you have customized nflow.db.*.driver parameters.

Details

• Popup notifications from workflow instance updates, network and authentication issues in Explorer
• Upgraded Spring to version 5.1.3.RELEASE
• Workflow instance history (actions, states) cleanup as part of state processing, configurable through WorkflowSettings

v5.2.0

Highlights

• Add stopped field to executor data. In database, REST API and nFlow Explorer. Requires database migration.
• Support Azure AD authentication in Explorer (see nflow-explorer/src/config.js for configuration options)

Details

• Travis CI no longer runs tests with Oracle JDK 10. Only oraclejdk8 and openjdk11 are currently running Travis CI tests.
• Upgraded Spring to version 5.1.2.RELEASE
• Explorer displays a link in the header based on returnUrl and returnUrlLabel parameters in the Explorer opening URL
• nflow-netty's StartNflow interface changed to match nflow-jetty's
• Automatic refresh for workflow instance page in Explorer
• Downgrade org.reclections:reflections to 0.9.10 due to excessive logging in nflow-jetty startup when using 0.9.11

v5.1.0

Highlights

• Multiple bug fixes to nFlow Explorer, including Google Chrome crash fix
• Merge nFlow Explorer to nFlow repository

Details

• nflow-engine
  • Allow non-final error states in workflow definitions
• nFlow Explorer
  • Fix Google Chrome crash on workflow graph visualization (e.g. switching between parent and child workflow instances crashed Chrome)
  • Fix interaction between selected workflow graph node, action history row and manage state selection
  • Fix execution phases -graph in radiator of workflow definition
  • Bar chart in active instances of workflow definition: vertical to horizontal orientation, removed filters and formatting options
  • Enable pan and zoom in workflow graphs
• Run tests in Travis CI also with OpenJDK 11
• Upgraded Spring to version 5.1.0.RELEASE

v5.0.1

Highlights

• Use nFlow Explorer version 1.2.8

v5.0.0

Highlights

• Fix to work with Spring Boot 2.x and Spring 5.x
• Support for MS SQL database
• Support REST API based on spring-web in addition to JAX-RS.
• Experimental support for the Netty server

Breaking changes

• Renamed JAX-RS REST API project from nflow-rest-api to nflow-rest-api-jax-rs.
  • By default, the JAX-RS paths were changed from /nflow/v1/* to /v1/*.
• nflow-jetty now serves all paths under /nflow/*. The new paths are as follows:
  • /nflow/api/v1 -> API v1 (was: /api/nflow/v1)
  • /nflow/api/swagger.json -> Swagger config (was: /api/swagger.json)
  • /nflow/ui -> nFlow statics assets
  • /nflow/ui/explorer -> nFlow UI (was: /explorer)
  • /nflow/ui/doc -> Swagger UI (was: /doc)
  • /nflow/metrics -> metrics and health checks (was: /metrics)
• Removed the following nflow-jetty configuration properties:
  • nflow.swagger.basepath
  • nflow.api.basepath
• nflow-jetty Swagger UI no longer by default searches the entire classpath for Swagger annotations.
  • The behaviour can be controlled via the parameter nflow.swagger.packages.

Details

• Split nflow-rest-api into nflow-rest-api-jax-rs and nflow-rest-api-spring-web to reflect the targeted framework
• Add configuration parameter nflow.autoinit (defaults to true) that can be used to prevent database access on Spring inialization.
• nflow-rest-api-jax-rs:
  • Change endpoint paths for workflow instance: /v1/workflow-instance/{id} -> /v1/workflow-instance/id/{id}
• nflow-server-common:
  • Use nFlow Explorer version 1.2.7 (nFlow REST API path changes)
• Experimental new module nflow-netty
  • Based on Spring WebFlux and Netty.
  • Serves a limited subset of nflow-jetty paths with REST API under /nflow/api/v1 and nflow explorer under /nflow/ui/explorer.
• nflow-jetty
  • Added configuration parameter nflow.swagger.packages (defaults to io.nflow.rest), that controls which packages are searched for Swagger annotations.
  • Removed parameters nflow.swagger.basepath and nflow.api.basepath as everything is now prefixed under /nflow/*, which should remove the need to control the basepaths.

v4.2.0

Highlights

• Set state variables when inserting or updating workflow instance via REST API
• Control which properties are loaded when getting workflow instance with WorkflowInstanceService

Details

• nflow-engine:
  • Control which properties are loaded when getting workflow instance with WorkflowInstanceService: workflow started timestamp, child workflow identifiers, current state variables, actions and action state variables.
• nflow-jetty:
  • Use nFlow Explorer version 1.2.5 (support for setting workflow instance state variables)
  • Fix #212: make JAXRS server address configurable
• nflow-rest-api:
  • Set state variables when inserting or updating workflow instance

v4.1.0

Highlights

• Support workflow instance signals (see details below)
• Make MAX_SUBSEQUENT_STATE_EXECUTIONS configurable per workflow definition and state
• Workflow instance builder now supports putting state variables with optional value
• Add typed getStateVariable methods to WorkflowInstance (similar to StateExecution.getStateVariable methods)
• Add method to get the (optional) parent workflow instance id to StateExecution
• Fix #217

Details

• nflow-engine:
  • Support for getting and setting workflow instance signal value. Signals may be used by workflow state implementations, for example for interrupting long running workflow state executions. Workflow definitions may document supported signal values. When an unsupported signal value is set, a warning is logged.
• nflow-jetty:
  • Use nFlow Explorer version 1.2.4 (support for workflow instance signals)
• nflow-rest-api:
  • Support for getting and setting workflow instance signal value
  • Support for getting supported signal values of workflow definition
  • When getting workflow actions, return empty array instead of null when instance has no actions