Contracts before configuration
Declare typed Inputs and Outputs for each asset. Use Flow Variables for intermediate values, with field selection informed by upstream steps.
Define your dataSROTAX STUDIO A closer look at SrotaX Build and test business rules.
Build and test business rules.
Call them from your app.
Design the logic behind your APIs and AI tools.
Bring rules, request transformations, and reusable decisions
into one visual workspace.
Order subtotal in. Shipping fee out.
A browser demonstration of a two-row shipping policy. This runs locally in this page; it does not call your workspace or the SrotaX runtime.
Shipping rule
Subtotal ≥ 100 → fee 0
Otherwise → fee 9
Method: Standard
Response
Enter a subtotal and run the example.
ONE REQUEST.
A DEFINED DECISION PATH.
01 Shape the data
→02 Apply your policies
→03 Define the response
THE DECISION WORKSPACEChoose the right shape
Choose the right shape
for your business logic.
From a simple policy table to a complete request-processing flow. Edit assets together in a change set, review them, and merge immutable versions into Main.
The whole request.
One connected canvas.
Prepare data, transform nested lists, look up reference values, and invoke reusable decision assets. Connect each step to a defined response.
- Validate, Set Fields, and Choose Fields
- Map, filter, flatten, sort, trim, and aggregate lists
- Pin published Table, Tree, and dataset versions
- Inspect Test Input, Result, Trace, and Issues
Make policy rules
easy to review.
Bind condition columns to typed Inputs and result columns to Outputs. Rows run from top to bottom; the first matching row determines the outcome.
- Conditions and results in a readable grid
- Type-aware fields and condition operators
- Fixed values and copied fields for results
- Published snapshots with explicit draft editing
Give every condition
a visible outcome.
Lay out decisions as a tree of conditions and result leaves. Use nested AND / OR groups to express policy, then assign the declared output values.
- Explicit Yes and No paths
- Shared, type-aware condition authoring
- Fixed-value and field-copy assignments
- Validation linked to affected nodes
A SHARED FOUNDATION
Clarity at every boundary.
The rules are only part of the picture. Define what comes in, what can change, and exactly which version a Flow uses.
Reference data with a version
Import an Excel worksheet, define its primary key, and merge the dataset through a change set. Configure lookups against a specific snapshot and choose how to handle no match.
Manage lookup dataDeliberate change management
Save and test related drafts in a change set. An Admin merges them into Main; create a release from Main and activate it in an environment.
Understand the lifecycleBEYOND THE EDITORA workspace for
Explore integration options
A workspace for
the whole decision lifecycle.
Find assets in Catalog. Manage shared reference datasets. Keep workspace administration and organisation membership in their own clearly defined scopes.
One catalog for all asset typesSearch assets and distinguish drafts from published versions.
Organisation and workspace structureInvite organisation members, then assign Reader, Editor, or Admin workspace access.
Operational views in StudioOverview, Execution History, Activity, API Keys, and Members.
WHAT CAN YOU BUILD?Business rules for
Business rules for
everyday decisions.
From campaign eligibility to fulfillment policies, return consistent decisions your applications can act on.
Campaigns & Outreach
Determine campaign eligibility, contact channel, reminder eligibility, and when to suppress outreach.
Explore use case →Pricing & Promotions
Calculate customer prices, discounts, coupon eligibility, and permitted promotion combinations.
Explore use case →Shipping & Fulfillment
Calculate shipping fees, select eligible carriers and delivery options, and flag orders for review.
Explore use case →Eligibility & Approvals
Evaluate requirements and return an approval, decline, or manual-review decision with reasons.
Explore use case →