---
id: DFMOD-C10-POS-004
title: "Activity log empty state and long-content handling stay usable"
product: web
module: digital-form
type: functional
priority: P3
risk: low
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK141
  tsdSection: C10
  tsdScenario: C10.4
  prd: PK141
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK141 TSD C10.4; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-DF-form-exists
tags:
  - web
  - digital-form
  - activity-log
  - see-more
  - pk141
  - staging
---
## Objective
Verify the activity log empty state and long/complex content remain usable and read-only.

## Preconditions
- See [[PRE-DF-form-exists]]
- And the activity log is empty in one case and has very long/complex config in another

## Steps
1. Open the activity log detail page in each case

## Expected Result
- Then an informative empty state shows when there is no activity
- And a see-more / expanded view is available for long content (large DB/filter config not truncated without an expand option)
- And all detail stays read-only and represents the snapshot at activity time
- And empty states are consistent between compound log and form log

## Source Traceability
- TSD: PK141
- Section: C10 - Activity Log
- Scenario: C10.4 - Empty state and long-content handling
- Acceptance Criteria: PRD C.37 Scenario 6,12,13; C.38 Scenario 15,17,18

## Evidence Required
- Empty state + expandable long content, both read-only.

## Notes / Gaps
- Testing Concern TC-08 (Medium): final "see more" behavior pending design.