Development plans — legacy configuration guide

Legacy activation and data prerequisites

Verified in code:

Control/data	Effect and scope	Source
module_plan_dev_fo	Gates the employee Development plan profile pane.	Profile index.html.twig.
plandev	Gates the manager profile development-plan pane in the inspected template.	Prospect Includes/development.html.twig.
Published/active periods	Populate optional period grouping/selection in the legacy journey.	Profile controller and dev-objs-tab.html.twig.
Active action types	Populate the legacy action-type selector.	PerformanceSection.php and profile controller.
Current-job/career-plan skills	Supply optional skills for legacy objectives.	Legacy goal modal and goal/skill handlers.

These are implementation identifiers, not confirmed editable administrator fields in PS Testing. Defaults, inheritance and current switch values were Not verified. The legacy test objective saved without a period. Do not copy career-plan horizon settings into this feature.

Troubleshooting

Symptom	Configuration check
Legacy editor remains visible	Module gate, hybrid flag and SMR read right; this can be intentional fallback.
Manager cannot see the pane	plandev, profile section, role scope and user visibility.
Can read but cannot change statuses	Separate status right and deployed role grant.
Existing form cannot be edited	Read-only form state/access; inspect an authorized editable draft.
Cannot publish local form with unlimited cap	Front validation requires positive value; backend uses null for unlimited. This differs from deployed 0 wording.
Request fields absent	Off-catalogue and individual field switches on the deployed form.
Plan blocked after reducing the cap	Historical requests still count; no automatic deletion.

Evidence and limitations

• Observed in application: legacy objective/action persistence and existing redesigned form settings in PS Testing as Jim Carter; no administrator save or campaign launch.
• Verified in code: legacy profile templates, Service/V2/SmrDisplayService.php, Company/ProspectBundle/Services/ViewSection/PerformanceSection.php; nextgen-front src/modules/ModuleConfig/Campaigns/modules/FormBuilder/{components/Builder/BuildDevelopment.vue,validation/developmentQuestion.validation.ts}; nextgen-back src/Domain/V2/ReviewForm/DTO/ReviewDevelopmentQuestionDTO.php, src/Http/Api/Routing/V2/development.yaml, rights migration Version20260909101500.php.
• Specified in PRD: Individual Development Plan, version 106, read 23 October 2026.
• Not verified: current tenant switch values/inheritance, permissions administration, draft save, mode restriction at runtime, rollout/migration, PDF and preservation after signature. No application source repository was modified.