DecisionHub documentation
DecisionHub lets teams model data, author decision logic, connect systems, test changes, promote approved versions through environments, and execute them through an API.
Start here
- Quick start: create, test, and deploy a decision table.
- Key concepts: organizations, solutions, HubItems, versions, and environments.
- The Hub: folders, templates, history, global variables, and every HubItem type.
- Testing and debugging: ad-hoc payloads, saved tests, assertions, mocks, and traces.
- Environments and deployment: promotion requests, approval, and execution endpoints.
- Permissions: organization and solution access.
HubItem types
| HubItem | Use it for |
|---|---|
| Folder | Organizing and moving related assets |
| Data Model | Defining reusable input, output, payload, and response schemas |
| Decision Table | Expressing rows of conditions and results |
| Ruleset | Running prioritized WHEN/THEN rules and data mutations |
| Scorecard | Calculating an explainable score from weighted inputs |
| Workflow | Orchestrating rules, transformations, collections, APIs, and events |
| HTTP Client | Defining a reusable outbound HTTP request |
| Coding | Running reusable JavaScript logic |
Folders and Data Models are design assets. Decision Tables, Rulesets, Scorecards, Workflows, HTTP Clients, and Coding HubItems can be executed when a version is deployed to the selected environment.
UI and permissions
The interface hides or disables actions that your organization role, solution role, environment permission, plan, or current selection does not allow. If a documented control is missing, first confirm the active organization, solution, environment, and your assigned policies.