Skip to main content

​
What is Caseflow?

Caseflow is the object-data layer in Nobly Insight used for case and process-driven business data. It is organized around:
  • Applications — high-level functional domains
  • Classes — object types inside each application
  • Attributes — fields on each class, including relations
  • Objects — individual records
  • Filters — reusable query definitions used in list views
  • Templates — UI definitions for create, update, and preview experiences

​
User surfaces

Caseflow is exposed through four major user surfaces:

Landing page

Application selector, filter bar tree, search parameter controls, and result table with advanced interactions.

Object page

Full object rendering through an Update template.

Create page

Class-based object creation through a Create template.

Search preview pane

Uses a Preview Pane template when available. Falls back to a simple open-object action if not configured.

​
Core behavior model

Caseflow behaves as a metadata-driven system:
  • Class and attribute metadata drives type behavior, search resolution, and validation
  • Templates define layout and interaction
  • Actions define side effects and automation
  • The script engine extends behavior beyond declarative actions

​
Runtime architecture

The runtime is composed of five major layers:
The state store for primary, related, search-loaded, and create-mode objects. It provides:
  • Name-to-ID resolution utilities
  • Save, create, relation fetch, aliasing, and validation orchestration
Parses HTML-like templates and supports:
  • Variables, conditionals, loops, and custom components
  • Template variable resolution from a computed scope
See Templates and syntax for full details.
Maps template component names to their React implementations. Includes Caseflow-specific components and shared utility components.See Form components and Data and action components for the full reference.
Runs on event hooks (onChanged, onCreated, save hooks) and supports conditions, runtime variables, query refresh, create/set actions, and script calls.See Actions and scripting for full details.
Provides three integration paths:
  • Explicit button-based execution (ScriptButton)
  • Action-chain execution (callScript action)
  • Field-triggered autofill scripts
See Actions and scripting for full details.

​
Data and UI flow

At a high level, the runtime follows this sequence:
  1. Load object and class metadata
  2. Select template by class and type (or explicit template name)
  3. Build runtime scope — attributes, stock values, user info, aliases
  4. Render template into components
  5. Components read and write shared object context state
  6. Save operations persist only valid, non-transient attribute updates