Services

A service is an external process that connects to Requence. You create services in the UI and provide the implementation yourself.

On the planning side, each service is registered in the UI with one or more versions. A service version declares:

• An input schema — the data it expects to receive
• A configuration schema — static settings passed at design time
• One or more outputs — each with its own schema

When you drag a service node onto the canvas in the task template editor, you pick which service version to bind it to. Requence uses the version’s schemas to validate configuration at design time and input/output at execution time.