Product Capability Core introduces Product Capabilities tied to Product Models inside the ServiceNow platform.
This helps organizations to clearly define functions or outcomes a product is designed to deliver. By representing what a product can do, it enables the organization to articulate value for users or customers and is typically used to guide development, measure adoption, and align with business outcomes.
Use Case 1: Fine-Grained Capabilities within a Product
Description: Enables direct association of detailed capabilities with a specific product, while also allowing secondary capabilities to be linked under a primary capability associated with that product.
Use Case 2: Capabilities Spanning Multiple
Products Description: Supports capabilities that are shared across multiple products, along with secondary capabilities that can belong to various primary capabilities, demonstrating the m:n relationship.
Data Model to support the above use cases:
- Product Capability
- Capability Relationship Map
- Product Capability Map
- Product Capability Usage
- Product Usage
Product Use Case — Two new tables ship in this release: Base Use Case (the extensible foundation, with complexity, owner, process flow, and a Draft → Published → Retired lifecycle) and Supported Use Case (extends Base with industry and audience type). Use Cases can be mapped to capabilities and product models via a Use Case Map, with the capability picker automatically filtered to only show capabilities active for the selected product model. State transitions — Publish, Return to Draft, Retire, Cancel — are available as UI actions in both the classic form and the workspace. Write and delete access is locked to Draft state, preventing mutations on published or retired records.
Use Case Solution Map — The Use Case Solution Map relationship is surfaced as a related list on the Supported Use Case form, with a dedicated Delete action for removing individual map entries. A Business Rule guards the map to block inserts, updates, and deletes whenever the parent Use Case is not in Draft.
Access control — Full ACL coverage added for all new tables (Base Use Case, Supported Use Case, Use Case Map) and expanded across existing tables (Product Capability, Capability Relationship Map, Product Usage), all scoped to the existing read/write/admin roles. Fields that must not be edited post-publish (number, state, active) are marked strict read-only, with N-2 compatibility ensured through the read_only_option plugin dependency.
Fluent SDK migration — The repo is now built on the Fluent SDK framework, with all existing and new artifacts represented as typed TypeScript/JavaScript source. This aligns the project with the standard platform development toolchain for testing, linting, and CI.
N/A