Manage the Hub

The Hub is the asset workspace for the selected solution. It contains folders, Data Models, executable decision logic, reusable integrations, versions, tests, templates, history, and environment-aware variables.

Choose the correct HubItem

HubItem	Best suited to	Example
Folder	Organizing related assets	Lending / Personal Loans
Data Model	Defining JSON contracts	LoanApplication
Decision Table	Condition/result matrices	Eligibility policy
Ruleset	Ordered conditions and mutations	Validation and reason collection
Scorecard	Weighted points	Application risk score
Workflow	Multi-step orchestration	End-to-end loan decision
HTTP Client	Reusable web request	Retrieve customer profile
Coding	Reusable JavaScript calculation	Affordability calculation

Folders and Data Models do not execute. The other six types can run after a version is deployed to an environment.

Create an item

Select New, choose the type, enter a clear name, and save. Names should describe business purpose rather than implementation. Prefer Personal loan eligibility over Rules v2.

After creation, complete Settings before designing logic:

• Name is the display name visible to authors.
• Identifier is the stable technical/business identifier used in references.
• Description should state purpose, inputs, owner, and important policy boundaries.
• Input and output models define the executable contract.
• Auto-map Input to Output copies compatible input fields into the initial response.
• Analytics controls supported execution-data persistence when organization analytics is also enabled.
• Retention applies execution-history rules where available.
• Environment progression shows where versions are deployed.
• Event log records changes to the asset.

Organize with folders

Folders are HubItems used for hierarchy and bulk management. A domain-oriented structure is easier to navigate than organizing by technical type:

Lending
  Shared Models
    Applicant
    Loan Application
    Loan Decision
  Personal Loans
    Eligibility
    Risk Score
    Decision Workflow
    Tests and Samples
  Business Loans
Collections
Customer Onboarding

Moving an item changes its location, not its solution security scope. Search filters the tree; expand/collapse and refresh help when many authors are working.

Folder export includes the hierarchy. Folder deletion analyzes contained and external dependencies. Review the warning carefully: a dependency inside the same folder may be removed together, while an external dependant can block deletion.

Versions

A version is a deployable snapshot of a HubItem. Use New Version when beginning a change that must be reviewed and promoted independently. Selecting an older version is useful for comparison and audit, but it does not change which version an environment executes.

A safe sequence is:

1. Open the currently approved version.
2. Create a new version.
3. Make and save changes.
4. Run saved tests against the appropriate environment/version workflow.
5. Update parent Workflows to reference new dependency versions.
6. Create a deployment request and review dependencies.

Clone, share, import, and export

Clone creates a starting copy in the current workspace. Change the name and review all model/dependency references before treating it as independent logic.

Share → Solution makes the asset available in another solution you can access. Access does not transfer between solutions, and dependencies may also need to be shared or recreated.

Export produces a portable representation for review or transfer. Remove environment secrets and inspect imported definitions before saving. An imported asset can contain references that do not exist in the destination solution.

Collaborative editing

Where check-in/check-out controls are enabled, use them to signal edit ownership. Check-in does not replace versioning, testing, or deployment approval; it prevents authors from unintentionally editing the same definition at once.

Templates

Templates provide pre-built structures. Open the Templates view, inspect the purpose and generated assets, then create a copy. A template is a starting point—not proof that its rules, models, thresholds, or connectors match your organization. Rename, review, test, and version the created items.

Global Variables

Global Variables store non-secret runtime configuration by environment. Each variable has a key and one value per environment. A blank environment value means the variable is absent there.

Example:

Key	Development	Test	Production
manualReviewThreshold	40	45	50
supportEmail	dev-support@example.com	test-support@example.com	support@example.com

Use Global Variables for thresholds, feature behavior, or non-secret labels that genuinely vary by environment. Do not store passwords, tokens, or private keys; use connector authentication fields or an approved secret-management process.

Permissions can differ by environment. Deleting a value from one environment does not necessarily delete the variable elsewhere.

History and execution records

History shows changes across Hub assets. An individual HubItem's event log narrows the view to that asset. These audit records differ from Execution History, which shows runtime inputs, outputs, timing, correlation IDs, and optional debug information.

Delete safely

The item menu can offer Delete Last Version and Delete All Versions. Before confirming:

1. Read the dependency analysis.
2. Check deployed environments.
3. Confirm API consumers no longer call the item.
4. Export a recoverable copy if policy permits.
5. Verify saved tests or parent Workflows do not depend on the version.

Deletion is not a substitute for retiring access or creating a replacement version.