--- sourceDocument: Australia Sales and Order Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management Release : - australia ft:locale : - de-DE ft:publication_title : - Australia Sales and Order Management ft:clusterId : - omgmt bundleId : - omgmt workflow : - Customer and Industry --- # Configure fields # Configure fields {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 Minuten Lesedauer Learn about how fields in CPQ help structure data collection efficiently and about the various types of field. Associate fields with blueprints for consistent use across configurations, layouts, and rules. A field is a designated space where users can enter specific information. Imagine fields as sections in a questionnaire, each awaiting a particular piece of data. The usefulness of fields lies in their ability to structure data collection, making it easier for both users to enter values and admins to set them up efficiently and effectively. Without fields, the process of gathering information would be a chaotic jumble of function parameters, lacking the coherence necessary for meaningful data storage or the ability to enact rules. In CPQ, fields are global. This means a field may be reused in any blueprint, rule, or layout without having to create a unique field for each. * [Layouts](https://servicenow-prod.fluidtopics.net/wS0f8xuGMW15PkmEtFt8zw "Layouts define the structure and appearance of the configuration interface. They organize fields into pages, tabs, and sections, shaping how users interact with configurations and view shopping cart details in CPQ.") * Fields are the most granular component that make up a layout. A layout consists of many fields arranged into a navigational flow or page. * Tabs, expandable sections, column sets, field grids, and headings provide additional organization to the fields in a configuration experience. {#fields_101__ul_nbw_vvy_1hc} * [Rules](https://servicenow-prod.fluidtopics.net/0jeoZYZ~Zc8QyLRoCARYOw "Learn how to create and manage rules to deliver dynamic configuration experiences. Define conditions and actions to show or hide fields, display messages, calculate values, and generate bills of material (BOMs). Explore rule types, including visibility, message, inclusion, exclusion, determination, and product actions, to efficiently build intelligent, responsive configurations.") * Rules leverage fields as inputs to conditions, calculations, and logic. * Rules act on fields. A rule may determine the value of a field, display a message associated with a field, hide a field, control the options available in a field, and send the information in a field to the Product List, all in the same rule. {#fields_101__ul_urs_xvy_1hc} * [Blueprints](https://servicenow-prod.fluidtopics.net/eRUnHpp8p4Q0McxNPewqaQ "Blueprints define the structure of a configuration experience in CPQ. They act as containers that bring together fields, rules, layouts, and configurable products, enabling administrators to design, deploy, and manage complete configuration workflows across environments.") * Because fields are global across an environment, the only way for them to be a part of a specific configuration is to be associated with a blueprint. * When all of the fields referenced by a rule are associated with a blueprint, the rule is associated with the blueprint without the need to specify it. * When a field is associated with a blueprint, the field can be added to the layouts of the blueprint. {#fields_101__ul_ufb_zvy_1hc} {#fields_101__ul_yfm_5vy_1hc} When you associate a field to a blueprint, the application automatically associates all rules that leverage the field to the same blueprint. Fields and rules may be reused on any number of blueprints. ## Field types {#fields_101__section_jwl_5wy_1hc} Many field types are available, each with constraints and rules for entered values. For example, a number field is more suitable than a text field as a quantity field, since the only inputs it accepts are numbers. Similarly, if there are only a few options that a user should be allowed to enter, a picklist field should be used to limit the options for the end user. Because fields are global across an environment, all fields need a unique variable name when they are created. They can also be set as required during configuration, so that if the field is associated with a blueprint, it must be filled out before the configuration can be saved. Text fields accept any characters entered into the field up to 2000 characters. The field definition allows the admin to specify minimum and maximum field lengths and a static default value. Numbers fields accept only numeric characters in their fields. The field definition requires the admin to specify whether the field will be used as a number, currency, or percentage. Optional settings include minimum and maximum values and a default value. The unit label setting is not currently used in the application. To specify the display precision of a numeric value, in the CPQ layout, click the gear icon in the number field. Then, set the precision in the Display Precision field. Boolean fields accept only two values: true and false. The field definition allows the admin to specify a true label, a false label, and a default value. Unless specified, the default true label is Enabled and the default false label is Disabled. The default state is false. Picklists are fields that only allow specified options to be selected, such as catalog items. When defining the field, the admin must specify whether the field is single-select, where the user must select one value, or multi-select, where the user can select as many values as desired. If the field is single-select, the admin must also specify whether the option values should be evaluated as a text field or a number field. The admin can also add field options, set an order, or a default value or values, and add picklist extension data if necessary. A product picker is like a picklist with extended data. product pickers can add products to a bill of materials and map additional data to product list fields, including extended data, without writing standard rules. A set is a collection of fields that interacts only with the fields in their own row and column. ## Sample blueprint showing field options and display variations {#fields_101__section_gzr_b3l_jhc} The following blueprint includes all the different field options and display variations. This ZIP file contains the layout CSV files that show how to set the component display types for each option. [Component Display type blueprint](https://drive.google.com/file/d/1gq0Cc6ymPstowbT4xAg4M0GI8VlE9apj/view?usp=sharing) **Zugehörige Konzepte** * [CPQ fields, system fields, and partner fields](https://servicenow-prod.fluidtopics.net/D3bEzg_QVyaTaJ9BrmT8hg "Learn about the three types of fields in CPQ—CPQ, system fields, and partner fields. Understand how each type stores, retrieves, and displays data in configurations, and how they interact with Salesforce and partner systems for seamless data integration.") * [Grid-style fields and field collections](https://servicenow-prod.fluidtopics.net/_4Ru4DlNVy3XMbYgRwcv1g "Learn about the various types of grid-style fields: the picklist extension, the field grid, the indexed set, the associated picklist set, and the product picker. Learn how best to choose a field type for your data.") **Zugehörige Verweise** * [Field type display options](https://servicenow-prod.fluidtopics.net/jtKWX4X2Dwe2TFI6DfkizA "Field type display options") * [Boundaries and limits](https://servicenow-prod.fluidtopics.net/aNAEkXxrJjmIExwPhlkgZw "View a list of boundaries and limits in CPQ.")