---
id: DFMOD-C2-EDGE-002
title: "Invalid or unsaved step handling during scoped save"
product: web
module: digital-form
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK141
  tsdSection: C2
  tsdScenario: C2.1
  prd: PK141
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK141 TSD C2.1 edge cases; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-DF-cp-editing-form
tags:
  - web
  - digital-form
  - form-modification
  - save-scope
  - edge-case
  - pk141
  - staging
---
## Objective
Verify scoped-save behavior when a step is partially edited/invalid or not yet committed.

## Preconditions
- See [[PRE-DF-cp-editing-form]]

## Steps
1. Partially edit Step 2 (not yet valid), then Save from Step 1
2. Leave Step 2 uncommitted at Step 4, then Save at Step 5

## Expected Result
- Then saving from Step 1 with an invalid Step 2 edit discards that Step 2 change
- And saving at Step 5 commits the previously uncommitted Step 2 change as a fallback

## Source Traceability
- TSD: PK141
- Section: C2 - Save Scope
- Scenario: C2.1 - Save scope (edge cases)
- Acceptance Criteria: PRD C.5 Scenario 1-4

## Evidence Required
- Backend diff for each path.

## Notes / Gaps
- Testing Concern TC-01 (High): the mixed-edit save contract across steps must be confirmed in implementation.