Decision Table
Map conditions to outcomes in rows. Useful for shipping fees, discounts, and eligibility policies.
Build a Table →Define a decision.
Test it. Put it to work.
Build business rules visually, test them with your data, and release a stable version for your application to call.
Build your first shipping decision →Choose the right shape for your rules.
Make the inputs and outputs explicit.
A Data Contract describes the request and response. Edit the same schema using Fields or JSON, and reference reusable Models for shared structures such as an address or order item.
In Flows, input.* preserves the original request, local.* holds working values, and output.* defines the response.
Start with one shipping policy.
A two-row Table returns free Standard shipping for subtotals of 100 or more, and a fee of 9 otherwise.
| Order subtotal | Shipping fee | Method |
|---|---|---|
| ≥ 100 | 0 | Standard |
| < 100 | 9 | Standard |
Test {"subtotal":85} to get fee 9, then test {"subtotal":100} to check the boundary and get fee 0.
Tables, Trees, and Flows share a Test Panel. Result shows the output; Trace shows the matched row, executed branch, or Flow steps; Issues explains failures.
Follow the shipping quickstart → · Understand test results →Connect decisions with reusable subflows.
The order fulfillment walkthrough combines a main Flow, a charges subflow, a shipping Table, a review Tree, and regional handling reference data.
The main Flow prepares items and calculates the subtotal. Call Flow invokes Calculate Order Charges, which looks up handling fees and calls the shipping Table. The main Flow then calls the review Tree and returns the appropriate response.
This is a worked example you can follow in your own workspace.
Follow order fulfillment with subflows →Review changes. Release a stable version.
Work in a change set, save and test your drafts, then review and merge them into Main. Merging does not deploy the changes.
Change set→ Review & merge →Main→ Create release →Activate
Create a release from Main and activate it in an environment. Your application calls the runtime API using an environment-scoped workspace API key. Keep keys on your server.
For Java applications, the documentation includes an HTTP client example for calling the Runtime API.
Release and activate → · Call the runtime API → · Integrate with Java →