Fundamentals overview
This section covers the core building blocks of the Casewhere platform. Whether you are a configurator designing solutions in Casewhere Admin or a developer writing scripts and plugins, these articles will help you understand how the platform works and how to use it effectively.
Core concepts
| Concept | Description |
|---|---|
| Product | The top-level container for organizing and managing Casewhere resources |
| Worker site | The front-end application that end-users interact with |
| Page and widget | UI building blocks for displaying data and collecting user input |
| Data class | Defines the data model — attributes, types, relationships, and validation |
| Data source | Custom data queries for widgets and scripting |
| Process | Business processes that group related cases |
| Rule | Reusable logic for access control, navigation, triggers, and more |
| Workflow | The execution engine — defines how data is created, updated, and processed |
| Plugin | Extend Casewhere with custom .NET code |
| CMS | Content management for widget templates and static content |
| Theme | Customize the look and feel of worker sites |
| Source Control | Version-control your configuration in a Git-tracked folder |
| AI Integration (MCP) | Build and maintain solutions with AI assistants through the MCP server |
Getting started
A typical Casewhere solution is built by:
- Modeling data — Create data classes to define your entities and their attributes
- Defining processes — Set up processes to represent your business workflows
- Building workflows — Design workflow definitions with forms and scripts to handle user interactions and automation
- Configuring rules — Use rules to control access, navigation, and triggered behavior
- Designing the UI — Create pages and widgets on worker sites for your end-users