---
id: DFMOD-C5-POS-001
title: "CP user modifies compound config with form-builder-consistent behavior"
product: web
module: digital-form
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK141
  tsdSection: C5
  tsdScenario: C5.1
  prd: PK141
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK141 TSD C5.1; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-DF-compound-exists
tags:
  - web
  - digital-form
  - form-modification
  - compound
  - client-portal
  - pk141
  - staging
---
## Objective
Verify compound editing behaves consistently with the form builder and warns on impactful changes.

## Preconditions
- See [[PRE-DF-compound-exists]]
- And the user opens the compound edit page from the list

## Steps
1. Change general config, item source, info detail, question list, question config, or options

## Expected Result
- Then all interactions behave consistently with the form builder
- And validation rules stay enforced
- And a warning appears when a source change or input-type change impacts the structure

## Source Traceability
- TSD: PK141
- Section: C5 - Compound Modification
- Scenario: C5.1 - Modify compound config consistently
- Acceptance Criteria: PRD C.16 Scenario 1-6, C.17 Scenario 1-7

## Evidence Required
- Screen recording of compound edit + impact warning.

## Notes / Gaps
- Editing an option on a compound used by many forms must keep impact awareness visible.