---
id: DFMOD-C2-POS-003
title: "Step 1 changes keep version; structural Step 2/3 changes create one new version"
product: web
module: digital-form
type: functional
priority: P0
risk: critical
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK141
  tsdSection: C2
  tsdScenario: C2.2
  prd: PK141
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK141 TSD C2.2; 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
  - versioning
  - client-portal
  - pk141
  - staging
---
## Objective
Verify versioning rules: non-structural Step 1 edits do not bump the version; structural Step 2/3 edits create exactly one new version per save.

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

## Steps
1. Change only basic info / modification & approval / availability / target in Step 1, then save
2. Change Form Builder / training material / logic jump in Step 2 or Step 3, then save via Step 4 or Step 5

## Expected Result
- Then the Form Version stays the same after the Step 1-only save
- And the system creates exactly one new version for the structural save action

## Source Traceability
- TSD: PK141
- Section: C2 - Versioning
- Scenario: C2.2 - Step 1 no version, structural Step 2/3 creates version
- Acceptance Criteria: PRD C.8 Scenario 3-6, C.9 Scenario 1-6, C.10/11/13

## Evidence Required
- Version value before/after each save.

## Notes / Gaps
- Revert-before-save and mixed changes are covered by DFMOD-C2-EDGE-004.