Page History
...
Close your project to edit your project structure, and add a new interaction module. Now make this new module your entry point, instead of the web service module. Open your project again and go to this new module, and create a domain model, the required logic elements and optionally a flow Flow. In the WebCalculator example, this could be as simple as one Input entity with two attributes to hold the input values, one Output entity with an attribute to hold the result, and a Decision table to do the appropriate calculations.
Your new module typically has no pages for user interaction, and even a flow is Flow is not always needed. If you create a flow at all, it should be exposed, and it will just contain service calls to create instances and/or set attribute values and/or relations. In other words, to create all that is necessary to fill the response.
...
The web service in the configuration module determines which operations you expose. Each operation can refer to a data mapping and optionally trigger a flow Flow. You can only select a flow from the entry point module, and the flow should be exposed and automated (i.e. contain no pages).
When you have the data mapping in place (and used by the Web service!), you can test if the BaaS works by calling it from SoapUI, as described in the visual Call to BAAS.
Overview
Content Tools