I need to add a new choice value "On Hold" the planning state filed on the sn_align_core_planning_item table. What should be considered when adding a new value?
A few things to consider when adding "On Hold" to the planning_state field on sn_align_core_planning_item:
Choice List — Add the value (e.g., on_hold) via System Definition > Choice Lists. Keep the internal value lowercase with underscores to match OOTB conventions, and make the change in your custom scope — not Global - to stay upgrade-safe.
Business Rule — Review the OOTB BR "Set Planning state on state change." This automatically maps execution-side State values (Demand, Project) to Planning State. Decide if any state should map to/from "On Hold" and update the script accordingly.
Roadmap Visibility — The Portfolio Planning Workspace applies default filters on planning state. Decide whether "On Hold" items should appear on the roadmap and check for any quick filter scripts that hardcode state arrays — your new value won't show up unless it's included.
Alignment Integration — If you have field maps syncing planning state between execution tables (dmn_demand, pm_project) and alignment tables, make sure on_hold exists on both sides to avoid sync issues.
Existing Scripts — Do a quick search for planning_state references across Business Rules, Flow Designer, Client Scripts, and reports. Hardcoded state checks are easy to miss.
Governance — Define what "On Hold" means for your org, who can set it, and whether items in that state should trigger a notification or review cadence.
