---
id: DFMOD-C6-POS-001
title: "Availability changes are accepted with latest config as source of truth"
product: web
module: digital-form
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK141
  tsdSection: C6
  tsdScenario: C6.1
  prd: PK141
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK141 TSD C6.1; 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
  - availability
  - client-portal
  - pk141
  - staging
---
## Objective
Verify valid availability changes (permanent/temporary, extend/shorten) take effect with the latest saved config winning.

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

## Steps
1. Switch permanent↔temporary, extend, or shorten the period, then save
2. Adjust only the end date without changing the start date

## Expected Result
- Then the latest saved configuration becomes the source of truth
- And multiple sequential changes leave only the latest saved state in effect
- And adjusting the end date preserves the start date

## Source Traceability
- TSD: PK141
- Section: C6 - Availability Modification
- Scenario: C6.1 - Availability change with valid logic
- Acceptance Criteria: PRD C.22 Scenario 1-5, C.23 Scenario 1-4

## Evidence Required
- Saved availability config across sequential edits.

## Notes / Gaps
- Invalid-period blocking is covered by DFMOD-C6-NEG-002.