Input
input.* preserves the original request in a Flow. Steps read it without changing it.
Send your data.
Get a decision.
Call a released Table, Tree, or Flow through the Runtime API. Your application supplies the request and uses the result to decide what happens next.
Read the Runtime API guide →01 / RUNTIME APIOne JSON request.
One JSON request.
A result your app can use.
Execute a decision using its stable ID. The runtime API key selects the organisation, workspace, and environment; the active release supplies the decision version.
Send the input document directly. For the shipping example, a subtotal of 75 produces a fee of 9 and method Standard in the response’s data field.
Check both HTTP status and the response’s success value before using data. Keep runId for troubleshooting, and keep API keys in server-side configuration.
HTTP REQUEST
POST /api/runtime/decisions/{decisionId}/execute
Authorization: Bearer <runtime-api-key>
Content-Type: application/json
{"subtotal":75}02 / JAVA APPLICATIONS
Call from your existing Java service.
Use Java’s HTTP client to send a request to the Runtime API. The documentation includes a downloadable Java 17+ example with authentication, connection and request timeouts, and HTTP status handling.
Parse the JSON response using your application’s JSON library and check execution success before consuming the result. This integration calls the runtime service over HTTP.
Use the Java integration example →Clear boundaries for your data.
Local
local.* holds calculations and working lists. Steps can reuse and replace these values.
Output
output.* holds the response fields defined by the decision’s contract.
Data Contracts define the expected structure. Reusable Models let contracts reference shared objects such as addresses and order items.
Data Contracts → · Reusable Models →From authoring to execution
Studio→Validation & compiler→Java engine
The engine evaluates supported Mongo-style expressions in memory. A MongoDB database is not required for decision evaluation.
Supported operators and behavior →04 / REUSABLE DECISIONS
Compose logic through explicit contracts.
A Flow can call a Decision Table, Decision Tree, or another Flow. Map the called asset’s inputs and store its returned result in the caller’s working data.
Choose a published dependency or a saved draft in the same change set. Draft dependencies are resolved and pinned during merge. Shared Model references provide reusable data definitions without making called assets share execution state.
The fulfillment example calls a charges subflow that combines a shipping Table and regional handling lookup, then uses a review Tree to choose the final response.
Explore the connected fulfillment example →Separate authoring from activation.
Change set→ Merge →Main→ Create release →Activate
Save and test drafts in a change set, then review and merge them into Main. Create a release and activate it in Development or Production. Merging alone does not change the active release.
Releases preserve the model definitions and decision dependencies they use. Later authoring changes do not rewrite an existing release.
Create and activate a release →