--- sourceDocument: Australia Strategic Portfolio Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-business-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Demand experiences # Demand experiences {#ariaid-title1} Release version: Australia Updated September 25, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Demand experiences Demand experiences in ServiceNow define governance processes that control which form views, modules, and dynamic attributes appear on demand records. They enable different teams---such as marketing and IT---to have tailored demand management processes with relevant fields and layouts. Each demand experience can be associated with a dynamic category, which specifies the custom fields applicable to that experience. Show full answer Show less ## Key Features * **Demand Experience Records:** Define specific governance processes with customized form views and modules for demands. * **Dynamic Categories:** Created by administrators, these define and group dynamic attributes (custom fields) for an experience. They support multiple data types including String, Boolean, Date, Choice, and Reference. * **Inheritance in Dynamic Categories:** Child categories can inherit attributes from parent categories, allowing shared fields plus experience-specific additions. * **Form View Precedence:** Demand experiences automatically create view rules that determine the form view based on execution order. When active, users cannot override the view. * **Additional Information Tab:** Conditional tab on demand records in the Next Experience interface that displays editable dynamic attributes if the demand's dynamic category has defined attributes. ## Key Outcomes * Teams can capture and manage demand data relevant to their specific governance needs with appropriate fields and layouts. * Custom fields scoped to experiences ensure data relevance without impacting other demand records or default fields. * Demand managers can view and update experience-specific custom fields directly in Demand Management. * The Additional Information tab enhances user experience by presenting dynamic attributes clearly and making them editable when applicable. A demand experience defines a governance process and controls which form view, modules, and dynamic attributes appear on a demand. Different teams often need different governance processes for their demands. For example, a marketing team and an IT team may each need their own set of fields, modules, and layout. Each team captures the information that's relevant to their process. You can use a demand experience record to define one governance process, such as Marketing or IT. The experience controls the form view, modules, and dynamic attributes that appear on each demand that uses it. A demand experience can optionally reference a dynamic category. The dynamic category defines the set of dynamic attributes that are relevant to that governance process. Only an administrator can create a dynamic category. When a demand experience with a dynamic category is selected on a demand, any dynamic attributes configured on that category are available on the demand. ## Dynamic category {#demand-experiences-dw__section_ovx_dp3_tkc} A dynamic category defines the custom fields for a specific demand experience. It belongs to the `Default SPM Dynamic Namespace` and groups the dynamic attributes that appear as custom fields on demand records of that experience. Custom fields are scoped to a specific experience and don't appear on records of other experiences or affect default fields. * A dynamic category can have a parent category. A child category inherits the attributes of its parent, so you can define shared fields once and add experience-specific fields in each child category. * Custom fields support the String, Boolean, Date, Date/Time, Integer, Decimal, Floating point, Choice, and Reference data types. * Demand managers view and update custom fields in Demand Management. {#demand-experiences-dw__ul_xkk_fp3_tkc}For more information, see [Create a dynamic category](https://www.servicenow.com/docs/S2VY72_Tro49YIsl4hl3Hg "Create a dynamic category to define the custom fields that appear on demand records of a specific demand experience."). ## Form view precedence {#demand-experiences-dw__section_demand_type_view_precedence} Saving a demand experience automatically creates its view rule and workspace view rule. A demand's form view can be determined by more than one view rule \[sysview_rule\] record. When more than one view rule applies, the rule with the lower execution order takes effect. When a demand experience's view rule is in effect, users can't change the view themselves. ## Additional Information tab {#demand-experiences-dw__section_additional_information_tab} The demand record page in Next Experience for Demand Management can display a conditional Additional Information tab that shows a demand's dynamic attributes. The tab is displayed when both of the following are true: * The demand has a dynamic category from its selected demand experience. * That dynamic category has one or more dynamic attributes defined. {#demand-experiences-dw__ul_dt_tab_conditions} If the demand has no dynamic category, or a category with no dynamic attributes, the Additional Information tab isn't displayed. The tab shows the configured dynamic attributes as editable fields, and the values that you enter are saved to the demand. For more information, see [Add dynamic attributes to a demand](https://www.servicenow.com/docs/dHgeSx3pGwmYqYgeQ_vcPw "Provide values for the dynamic attributes available on a demand through its Additional Information tab. This approach captures governance-process-specific information without affecting demands using other experiences."). **Related concepts** * [Enterprise-Wide Deployment for demands](https://www.servicenow.com/docs/c5rN75kMmzEFKE3unwnGkg "Enterprise-Wide Deployment (EWD) partitions demand data by criteria such as department. Demand experiences extends that by controlling each demand's fields, modules, and layout.") **Related tasks** * [Create a demand](https://www.servicenow.com/docs/ZLhTCzaCcqZq_IxOg5g8ww "Create demands to capture the strategic and operational requirements and centralize information for stakeholder assessment and prioritization.")