Persistence
4 requirements
·
6 scenarios
Tenant Data Persistence Configuration
JR-persistence-001
The system SHALL support per-tenant server-side persistence configuration that determines which features are stored server-side. Configurable features SHALL include chats, documents, workflow history, and reports. Tenants without explicit configuration SHALL default to no server-side storage.
3 test scenarios
- Enabled tenant stores workflow results JR-persistence-001.1
- Unconfigured tenant defaults to no storage JR-persistence-001.2
- Unknown domain defaults to no persistence JR-persistence-001.3
Disconnection-Safe Result Persistence
JR-persistence-002
The system SHALL save workflow-generated attachments at pipeline completion on the server side, not at response delivery. This ensures results persist even if the user's browser disconnects during a workflow.
1 test scenario
- Results persist after browser disconnection JR-persistence-002.1
Server-Side Chat History
JR-persistence-003
The system SHALL persist chat session history server-side for tenants with chat persistence enabled. Users SHALL be able to view prior conversation context on subsequent logins.
1 test scenario
- Chat history available across sessions JR-persistence-003.1
Reports Persistence Feature Flag
JR-persistence-004
The per-tenant persistence configuration SHALL include a reports feature flag governing whether generated report attachments are retained server-side.
1 test scenario
- Reports feature flag controls retention JR-persistence-004.1