Persistence
4 requirements
·
6 scenarios
Tenant Persistence Configuration
JR-persistence-001
The system SHALL support per-tenant server-side persistence configuration that determines which features (chats, documents, workflow history, reports) are stored server-side for a given domain.
3 test scenarios
- Tenant with persistence enabled stores workflow results JR-persistence-001.1
- Tenant without persistence defaults to no server-side storage JR-persistence-001.2
- Unknown domain defaults to no persistence JR-persistence-001.3
Disconnection-Safe Workflow Saving
JR-persistence-002
The system SHALL save workflow-generated attachments at pipeline completion (server-side), not at response delivery, so results persist even if the user's browser disconnects mid-workflow.
1 test scenario
- Browser disconnects during workflow JR-persistence-002.1
Chat History Persistence
JR-persistence-003
The system SHALL persist chat session history server-side for tenants with chat persistence enabled, so users can view prior conversation context on subsequent logins.
1 test scenario
- Chat history retained across sessions JR-persistence-003.1
Reports Feature Flag
JR-persistence-004
The system SHALL include a
reports feature flag in the per-tenant persistence configuration, governing whether generated report attachments are retained server-side.
1 test scenario
- Reports feature check JR-persistence-004.1