Microservices within FlowWright was a huge hit with some of our customers, especially the customer who processes real-time workflows, how the cook is it to design a workflow graphically and turn it into a simple to call REST API. But also, most appreciate the high-speed execution of these workflows in memory.

We have made several new enhancements to the FlowWright’s Microservices.  We heard from our customers and we have implemented support GET and POST HTTP calls.

FlowWright Microservices using HTTP GET or POST calls

With the support of HTTP POST, now you can also pass more complex objects as inputs to the call. When defining input parameters, there’s a new checkbox that you can check to say to pass the value using the HTTP request body.

Using the form of the body, complex objects in JSON format can be passed.  The rendered REST API call will look as follows:

As you can see from the above graphic, the documentation for the API call shows that the “value2” parameter will be passed using the body of the request.

One of the other enhancements that were made is to the listing view of Microservices.

The first navigate icon will render the workflow definition being used by the Microservice. The last icon will navigate directly to the REST API call, we have improved the navigate to the REST API call.

When it comes to security, Microservices supported basic authentication, it is still supported.  But with the introduction of OAuth token authentication, now Microservices support token authentication. When calling a Microservices, instead of sending basic authentication credentials, send a bearer token as authentication. The Microservice will validate the token against FlowWright security infrastructure and perform the call. Using OAuth tokens with Microservices is a lot more secure than using basic authentication.