Sample data
Sample Data
Section titled “Sample Data”Sample Data (Admin → Data) seeds realistic sample content into your instance so you can explore, test, or showcase RezolveApp without hand-building records. It shows the status of the currently active batch (if any), lets you choose which modules to seed, and lets you remove exactly what it created.
Modules
Section titled “Modules”Sample data is organized into 14 modules, each seeding a related set of tables:
| Module | Seeds |
|---|---|
| Users & Groups | Users, groups, group members, roles |
| Configuration Management DB | Configuration items, companies |
| Incidents | Incidents and related approvals, SLAs, alerts |
| Catalog Requests | Requested items and approvals |
| Problems | Problem records |
| Changes | Change requests and approvals |
| Knowledge | Knowledge articles |
| HR Cases | HR service cases |
| Customer Service | Customer service cases |
| Portfolio & Projects | Portfolio/project records |
| Source-to-Pay | Procurement records |
| Workflow Runs | Flow execution history |
| AI & Analytics | AI usage/analytics sample data |
| Security & Audit | Security event and audit sample data |
Users & Groups, Configuration Management DB, Incidents, Catalog Requests, and Knowledge are selected by default. Some modules depend on others — for example, Incidents depends on Users and Configuration Management DB — and toggling a module on automatically pulls in what it needs; toggling one off only drops a dependency if nothing else selected still needs it.
Options
Section titled “Options”Before seeding, you can set:
- Volume — Minimal, Realistic, or Stress. Each module shows an estimated row count per preset, and the console totals the estimate live as you change your selection.
- Locale — English, Hebrew, or a mixed set of sample records.
- State mix — Fresh, Balanced, or Aged, controlling how far along (in states and dates) the seeded records are.
Scenarios
Section titled “Scenarios”Scenarios are storylines layered on top of your module selection — turning one on auto-includes whatever modules it needs:
| Scenario | What it creates |
|---|---|
| Major incident in flight | One promoted P1 major incident with 3 linked child incidents and a stakeholder alert. |
| SLA breach imminent | 3 open, high-priority incidents whose SLA is due to breach within a few hours. |
| VIP escalation | A VIP caller with an escalated customer-service case and a linked P1/P2 incident. |
| New-hire onboarding wave | 5 new hires with HR onboarding cases plus linked laptop/badge/access catalog requests. |
| Change freeze weekend | 6 scheduled changes colliding with next weekend’s freeze window, awaiting CAB approval. |
| Knowledge gap | 6 incidents on one recurring topic with no matching KB article, plus 2 flagged low-rated articles. |
Turning a scenario off doesn’t remove the modules it added — you may still want that data for other reasons.
Seeding and removing
Section titled “Seeding and removing”- Choose your modules, options and scenarios.
- Select Seed sample data. Progress is reported per module as it runs.
- The console tracks the resulting batch — its status and row count show at the top.
- To remove what you seeded, use Remove, then confirm. This deletes exactly the rows from that batch, so it’s safe to seed, explore, and clean up without leaving stray records behind.
Only one sample-data batch is tracked as active at a time.