Skip to content

P6 Core 5.19.1

Release date: Thursday, 4th October, 2018

Improvements

  • When items are imported into a service, if they are unpackaged (ie: they have an empty application key), their application keys will be overridden with the application key selected by the user.
  • Documentation for Workflow step invocation has been updated to explain how to call a packaged workflow step.

Bug fixes

Web3j component

The web3j component has been upgraded to the 3.5.0 version to prevent the web3j component event listener to fail and throw exceptions if the Ethereum node is restarted.

Warning

It looks like the Java classes generated by web3j no longer compile after the upgrade! You must re-generate the classes with the new version of web3j.

Workflow routing

A script can now be executed by a workflow through a route.

See an example below:

from("direct:p6router.WFTest")
    .choice()
        .when(xpath("/MessageInfo/LastStatusCode='Awaiting Documents'"))
            .setHeader("platform6.request.action").constant("invoke")
            .setHeader("status").constant("TO_BE_REVIEWED")
            .setHeader("step").constant("ReviewInvoice")
            .setHeader("script").constant("WFStepBuilder_Generic_UBL")
            .to("p6route://workflowsteps")        
        .otherwise()
            .throwException(com.amalto.b2box.core.api.B2boxException, "No matching rule found for item!")
    .end()
    .routeId("WFTestRoute")

For more information about the parameters, have a look a the Workflow step invocation section.