Function as a Service API

[StephenOTT]

Building on the scenarios discussed with

Replacing Http-Connector with Jsoup usage

Here is another interesting use case where you could use Jsoup + variablesInResult parameter of the /start process-definition endpoint to provide a validations workflow. Example: you submit a form, and you need to have server side validations with other systems. [FaaS] Could also be 4 sequential scripts. The performance was the same. So your setup would look something like: [function-internal] [function-external] [postman-request] [postman-response] The function.js looks like this: i…

This came to mind today:

Where the Confirm Link Process. With the ability to simply control the Body, status code, and headers response, and the ability to do GET with query params that are translated into the /start camunda endpoint, we end up with a REALLY flexible solution for all sort of different callback scenarios that are routed with camunda.

This scenario only becomes interesting (at least to me) because of the ability to control the JSON response. In all our scenarios Camunda is never exposed to the outside (its always proxied by another security/transformation layer. So the ability to have a flexible return opens up a lot of options for technical users to deploy workflows without the need to bring it lots of heavy layers or lots of staff/knowledge.