{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":39211,"path":"platform-administration/r_FieldTypes.md","title":"Field types reference","bundle":null,"doc_type":null,"release":"australia","body":"\n# Field types reference\n\nThese field types are available to administrators when creating fields or changing the type of existing fields.\n\n<table id=\"table_nkv_4m4_y4\"><thead><tr><th>\n\nField type\n\n</th><th>\n\nPlatform name\n\n</th><th>\n\nSupported in configurable workspace\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\napproval\\_rules\n\n</td><td>\n\nApproval Rules\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\naudio\n\n</td><td>\n\nAudio\n\n</td><td>\n\nNo\n\n</td><td>\n\nAudio field for uploading and embedding `.mp3` or `.ogg` audio files.\n\n</td></tr><tr><td>\n\nauto\\_increment\n\n</td><td>\n\nAuto Increment\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nauto\\_number\n\n</td><td>\n\nAuto Number\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nboolean\n\n</td><td>\n\nTrue/False\n\n</td><td>\n\nYes\n\n</td><td>\n\nTrue/False field that holds a true or false value, typically displayed as a check box.\n\n</td></tr><tr><td>\n\nbootstrap\\_color\n\n</td><td>\n\nBootstrap Color\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nbreakdown\\_element\n\n</td><td>\n\nBreakdown Element\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ncalendar\\_date\\_time\n\n</td><td>\n\nCalendar Date and Time\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ncatalogue\\_preview\n\n</td><td>\n\nCatalog Preview\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nchar\n\n</td><td>\n\nChar\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nchoice\n\n</td><td>\n\nChoice\n\n</td><td>\n\nYes\n\n</td><td>\n\nChoice field that restricts values to a list of options, which is ideal for fields with a limited set of valid entries. For example, a priority field or a category field.\n\n</td></tr><tr><td>\n\ncollection\n\n</td><td>\n\nCollection\n\n</td><td>\n\nNo\n\n</td><td>\n\nCollection field type that applies any changes made to the assigned field also to the entire tableFor example, changes such as attributes or the **Read only** check box that are applied to a table entry with this field type are applied to the table rather than a specific field. This entry is automatically created when a table is created. There shouldn't be more than one entry for a table of this type.\n\n</td></tr><tr><td>\n\ncolor\n\n</td><td>\n\nColor\n\n</td><td>\n\nNo\n\n</td><td id=\"entry_ColorField\">\n\nString field that accepts CSS color declarations,including hex or RGB notation, and displays a preview. For more information on CSS color declarations, go to the Mozilla developer web docs. See the \"&lt;color&gt;\" article. [https://developer.mozilla.org/en-US/docs/Web/CSS/color\\_value](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value).\n\n</td></tr><tr><td>\n\ncolor\\_display\n\n</td><td>\n\nColor Display\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ncomposite\\_field\n\n</td><td>\n\nComposite Field\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ncomposite\\_name\n\n</td><td>\n\nComposite Name\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ncompressed\n\n</td><td>\n\nCompressed\n\n</td><td>\n\nNo\n\n</td><td>\n\nCompressed field that stores large binary data in a compressed format, reducing database storage requirements.It's used for files like images or documents, automatically compressing and decompressing data to optimize performance. This field type helps maintain efficient storage and database performance, especially when handling large volumes of data.\n\n</td></tr><tr><td>\n\ncondition\\_string\n\n</td><td>\n\nCondition String\n\n</td><td>\n\nYes\n\n</td><td>\n\nText field that accepts a plain JavaScript condition statement that is validated automatically for correctness before an update.\n\n</td></tr><tr><td>\n\nconditions\n\n</td><td>\n\nConditions\n\n</td><td>\n\nYes\n\n</td><td id=\"Conditions\">\n\nField that adds the condition builder to a form. You must specify a dependent field that references the table name.\n\n</td></tr><tr><td>\n\ncounter\n\n</td><td>\n\nCounter\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ncss\n\n</td><td>\n\nCSS\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ncurrency\n\n</td><td>\n\nCurrency\n\n</td><td>\n\nYes\n\n</td><td id=\"entry_CurrencyField\">\n\nDecimal field with four digits after the decimal point.When displayed on a form, a **Currency** field also includes an additional list of choices for selecting the currency type. If there isn't a default value for the field, then empty **Currency** fields use the reference currency. Adding a value causes the field to use the session currency of the active user. See [Change default currency decimal places](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/currency-administration/change-currency-fraction-digits.md) for how to use two fraction digits.\n\n**Note:** After you assign this field type to a field, you can’t change it to the **FX Currency** field type.\n\n</td></tr><tr><td>\n\ncurrency2\n\n</td><td>\n\nFX Currency\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ndata\\_array\n\n</td><td>\n\nData Array\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ndata\\_object\n\n</td><td>\n\nData Object\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ndata\\_structure\n\n</td><td>\n\nData Structure\n\n</td><td>\n\nNo\n\n</td><td id=\"entry_DataStructure\">\n\nData structure field where you can select one of the following data structures and enter values to organize particular information in the record:-   String\n-   Boolean\n-   Integer\n-   Decimal\n-   Object\n-   Array\n\n</td></tr><tr><td>\n\ndate\n\n</td><td>\n\nOther date\n\n</td><td>\n\nYes\n\n</td><td>\n\nField used to store date and time values without requiring a time zone. Unlike glide\\_date\\_time, which is converted to UTC in the database, this field retains the date and time exactly as entered, without any conversion.\n\n</td></tr><tr><td>\n\ndatetime\n\n</td><td>\n\nDate/Time\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nday\\_of\\_week\n\n</td><td>\n\nDay of Week\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ndays\\_of\\_weeks\n\n</td><td>\n\nDays of Week\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ndecimal\n\n</td><td>\n\nDecimal\n\n</td><td>\n\nYes\n\n</td><td id=\"entry_DecimalField\">\n\nNumber field with up to two digits after the decimal points. For example, 12.34.\n\n</td></tr><tr><td>\n\ndocument\\_id\n\n</td><td>\n\nDocument ID\n\n</td><td>\n\nYes\n\n</td><td id=\"DocumentID\">\n\nDocument ID field that references a record on a table.\n\n</td></tr><tr><td>\n\ndocumentation\\_field\n\n</td><td>\n\nDocumentation Field\n\n</td><td>\n\nYes\n\n</td><td>\n\nDocumentation field used by admins to add the label during table or field creation.\n\n</td></tr><tr><td>\n\ndomain\\_id\n\n</td><td>\n\nDomain ID\n\n</td><td>\n\nYes\n\n</td><td>\n\nDomain ID field that contains a reference to the domain.\n\n</td></tr><tr><td>\n\ndomain\\_path\n\n</td><td>\n\nDomain Path\n\n</td><td>\n\nYes\n\n</td><td>\n\nString field that contains a domain path, which is a series of three-character codes separated by a slash delimiter that uniquely identifies a domain. For more information on domain paths, see [Domain Separation- Advanced Concepts and Configurations \\[KB0716268\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0716268) article in the Now Support Knowledge Base.\n\n</td></tr><tr><td>\n\ndue\\_date\n\n</td><td>\n\nDue Date\n\n</td><td>\n\nYes\n\n</td><td>\n\nDate field that stores a date and time.\n\n</td></tr><tr><td>\n\nemail\n\n</td><td>\n\nEmail\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nemail\\_script\n\n</td><td>\n\nEmail Script\n\n</td><td>\n\nYes\n\n</td><td>\n\nField used to create dynamic email templates. It provides the ability to use field name notation `(${fieldname})` to represent the dynamic value of variable. This field is a combination of text area and variable picker.\n\n</td></tr><tr><td>\n\nexpression\n\n</td><td>\n\nExpression\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nexternal\\_names\n\n</td><td>\n\nExternal Names\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nfield\\_list\n\n</td><td>\n\nField List\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nfield\\_name\n\n</td><td>\n\nField Name\n\n</td><td>\n\nYes\n\n</td><td id=\"entry_FieldName\">\n\nReference field for a field name in the table that is selected in a **Table Name** field type. Make this field dependent on the **Table Name** field.\n\n</td></tr><tr><td>\n\nfile\\_attachment\n\n</td><td>\n\nFile Attachment\n\n</td><td>\n\nYes\n\n</td><td>\n\nFile attachment field that can hold one file. All file types are supported.\n\n</td></tr><tr><td>\n\nfloat\n\n</td><td>\n\nFloating Point Number\n\n</td><td>\n\nYes\n\n</td><td>\n\nFloating Point Number fields use a default scale of 7, and the maximum length can't be set below 7 to ensure values can be stored and displayed correctly.\n\n</td></tr><tr><td>\n\nformula\n\n</td><td>\n\nFormula\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ngeo\\_point\n\n</td><td>\n\nGeo Point\n\n</td><td>\n\nNo\n\n</td><td>\n\nGeo point field for holding longitude and latitude coordinates.\n\n</td></tr><tr><td>\n\nglide\\_action\\_list\n\n</td><td>\n\nAction List\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nglide\\_date\n\n</td><td>\n\nDate\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nglide\\_date\\_time\n\n</td><td>\n\nDate/Time\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nglide\\_duration\n\n</td><td>\n\nDuration\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nglide\\_list\n\n</td><td>\n\nList\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nglide\\_precise\\_time\n\n</td><td>\n\nPrecise Time\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nglide\\_time\n\n</td><td>\n\nTime\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nglide\\_utc\\_time\n\n</td><td>\n\nUTC Time\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nglide\\_var\n\n</td><td>\n\nVar\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nglyphicon\n\n</td><td>\n\nGlyph Icon\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ngraphql\\_schema\n\n</td><td>\n\nGraphQL Schema\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nGUID\n\n</td><td>\n\nSys ID \\(GUID\\)\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nhtml\n\n</td><td>\n\nHTML\n\n</td><td>\n\nYes\n\n</td><td id=\"HTML\">\n\nString field with a built-in HTML editor. It supports formatted text with rich text editor and is useful for descriptions that need enhanced readability.\n\n</td></tr><tr><td>\n\nhtml\\_script\n\n</td><td>\n\nHTML script\n\n</td><td>\n\nYes\n\n</td><td>\n\nHTML script field that provides the ability to add variables in the form of field name notation `(${fieldname})` via a variable picker within the HTML editor. This field is used to create rich text content that also has dynamic values.\n\n</td></tr><tr><td>\n\nhtml\\_template\n\n</td><td>\n\nHTML template\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nicon\n\n</td><td>\n\nIcon\n\n</td><td>\n\nNo\n\n</td><td>\n\nString field that provides the user access to an icon picker in a form. By default, the favorites icon set is used.\n\n</td></tr><tr><td>\n\nimage\n\n</td><td>\n\nImage\n\n</td><td>\n\nNo\n\n</td><td>\n\nImage field used for uploading and embedding images.\n\n</td></tr><tr><td>\n\nindex\\_name\n\n</td><td>\n\nIndex Name\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ninsert\\_timestamp\n\n</td><td>\n\nInsert Timestamp\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nint\n\n</td><td>\n\nInt\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ninteger\n\n</td><td>\n\nInteger\n\n</td><td>\n\nYes\n\n</td><td id=\"entry_IntegerField\">\n\nNumber field with zero decimal points.**Note:** To search for an integer, input `=` followed by the integer in the search bar. For example, if you want to search for an Order of 100, input `=100`.\n\n</td></tr><tr><td>\n\ninteger\\_date\n\n</td><td>\n\nInteger date\n\n</td><td>\n\nYes\n\n</td><td>\n\nThe int field type is used to store alphanumeric values similar to string field type.\n\n</td></tr><tr><td>\n\ninteger\\_time\n\n</td><td>\n\nInteger time\n\n</td><td>\n\nYes\n\n</td><td>\n\nField used to store time values, similar to glide\\_time, but with a few key differences:-   The glide\\_time field stores the time as a fully formatted string \\(e.g., 1970-01-01 16:04:32\\), whereas the integer\\_time field stores it as a 6-digit string in a 24-hour format \\(e.g., 160432\\).\n-   glide\\_time supports time zones, meaning the displayed value changes based on the user's time zone settings. In contrast, integer\\_time does not support time zone adjustments and always displays the same time regardless of the user's location.\n\n</td></tr><tr><td>\n\ninternal\\_type\n\n</td><td>\n\nInternal Type\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nip\\_addr\n\n</td><td>\n\nIP Address \\(Validated IPV4, IPV6\\)\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nip\\_address\n\n</td><td>\n\nIP address\n\n</td><td>\n\nYes\n\n</td><td>\n\nVariable character field that stores IPv4 and IPv6 addresses. See [IP address field type](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/r-IPAddressFieldType.md) for more information.\n\n</td></tr><tr><td>\n\njournal\n\n</td><td>\n\nJournal\n\n</td><td>\n\nNo\n\n</td><td>\n\nJournal field that accepts text entries and displays previous entries with a user name and timestamp.\n\n</td></tr><tr><td>\n\njournal\\_input\n\n</td><td>\n\nJournal Input\n\n</td><td>\n\nYes\n\n</td><td id=\"JournalField\">\n\nJournal input field that accepts text entries but doesn't display previous entries.\n\n</td></tr><tr><td>\n\njournal\\_list\n\n</td><td>\n\nJournal List\n\n</td><td>\n\nNo\n\n</td><td>\n\nJournal list field that displays the contents of journal fields. You must specify the journal fields as the dependent fields. If a journal list field depends on more than one journal field, the entries are displayed chronologically.\n\n</td></tr><tr><td>\n\njson\n\n</td><td>\n\nJSON\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\njson\\_translations\n\n</td><td>\n\nJSON Translations\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nlanguage\n\n</td><td>\n\nLanguage\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nlong\n\n</td><td>\n\nLong\n\n</td><td>\n\nYes\n\n</td><td>\n\nLong field that stores large whole numbers, which can be useful for high-value data. This field handles values that exceed standard integer limits, which is essential in high-volume contexts like serial numbers or counting operations. This field ensures that numeric data is stored accurately without overflow.\n\n</td></tr><tr><td>\n\nlongint\n\n</td><td>\n\nLongint\n\n</td><td>\n\nYes\n\n</td><td>\n\nLongint field that stores large whole numbers, which can be useful for high-value data. This field handles values that exceed standard integer limits, which is essential in high-volume contexts like serial numbers or counting operations. This field ensures that numeric data is stored accurately without overflow.\n\n</td></tr><tr><td>\n\nmask\\_code\n\n</td><td>\n\nMask code\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nmetric\\_absolute\n\n</td><td>\n\nMetric Absolute\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nmetric\\_counter\n\n</td><td>\n\nMetric Counter\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nmetric\\_derive\n\n</td><td>\n\nMetric Derive\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nmetric\\_gauge\n\n</td><td>\n\nMetric Gauge\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nmid\\_config\n\n</td><td>\n\nMid Config\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nmonth\\_of\\_year\n\n</td><td>\n\nMonth of Year\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nmulti\\_small\n\n</td><td>\n\nMulti Small\n\n</td><td>\n\nYes\n\n</td><td>\n\nText area field that stores shorter texts like short descriptions and notes.\n\n</td></tr><tr><td>\n\nmulti\\_two\\_lines\n\n</td><td>\n\nTwo Line Text Area\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nname\\_values\n\n</td><td>\n\nName-Value Pairs\n\n</td><td>\n\nNo\n\n</td><td id=\"NameValue\">\n\nName-value pairs field that maps text values. Each mapping is one-to-one, but a single **Name-Value Pairs** field can contain multiple mappings. Each mapping must use a unique name, and the name can’t be empty.For example, you can use a **Name-Value Pairs** field to hold header information for a web service request. In this example, the name of each mapping is the header such as `Content-Type` and the value is the header value, such as `Application/json`. For information on scripting **Name-Value Pairs** fields, see [Name-value pairs field type](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/name-value-pair-scripting.md).\n\n</td></tr><tr><td>\n\nnds\\_icon\n\n</td><td>\n\nNDS Icon\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nnl\\_task\\_int1\n\n</td><td>\n\nNL Task Int1\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\norder\\_index\n\n</td><td>\n\nOrder Index\n\n</td><td>\n\nYes\n\n</td><td>\n\nOrder index field that defines the display order of records in lists or hierarchies. By assigning a numeric value to each record, it enables admins to control the visual sequence, which is helpful for logically organizing tasks, categories, or items. This field type helps improve user experience by making the interface intuitive and orderly.\n\n</td></tr><tr><td>\n\npassword\n\n</td><td>\n\nPassword \\(1 Way Encrypted\\)\n\n</td><td>\n\nYes\n\n</td><td id=\"Password1Way\">\n\nText field that stores passwords with one-way encryption. One-way encryption stores the password as a secure hash value that can't be decrypted.\n\n</td></tr><tr><td>\n\npassword2\n\n</td><td>\n\nPassword \\(2 Way Encrypted\\)\n\n</td><td>\n\nYes\n\n</td><td id=\"Password2\">\n\nText field that stores passwords with two-way encryption. Two-way encryption stores the password as a secure encrypted value that can be decrypted programmatically within the instance. You can use Password 2 encryption with form variables. To encrypt text fields on forms, see [Password2 encryption with KMF](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/password-2way-encrypted-fields.md). The length for password2 field values must be at least 255 characters.\n\n</td></tr><tr><td>\n\npercent\\_complete\n\n</td><td>\n\nPercent Complete\n\n</td><td>\n\nYes\n\n</td><td>\n\nDecimal field that renders a percent complete bar in lists. You can convert any existing **Decimal** field to a **Percent Complete** field.\n\n</td></tr><tr><td>\n\nph\\_number\n\n</td><td>\n\nPhone Number\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nphone\\_number\n\n</td><td>\n\nPhone Number \\(Unused\\)\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nphone\\_number\\_e164\n\n</td><td>\n\nPhone number \\(E164\\)\n\n</td><td>\n\nYes\n\n</td><td id=\"PhoneNumber\">\n\nString field that provides E164-compliant formatting and validation for telephone numbers.\n\n</td></tr><tr><td>\n\nprice\n\n</td><td>\n\nPrice\n\n</td><td>\n\nYes\n\n</td><td id=\"entry_PriceField\">\n\nCurrency field that enables control over conversions and display. See [Price fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/currency-administration/price-fields.md) for more information.\n\n</td></tr><tr><td>\n\nproperties\n\n</td><td>\n\nProperties\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nradio\n\n</td><td>\n\nRadio\n\n</td><td>\n\nYes\n\n</td><td>\n\nRadio field that displays mutually exclusive options as radio buttons, letting users select only one choice. It’s suitable for simple, definitive decisions, like priority level or yes/no responses. This field type helps improve usability by presenting clear options for single-selection inputs. As of the Zurich release, radio buttons can be displayed both horizontally and vertically in the form view.\n\n</td></tr><tr><td>\n\nrecords\n\n</td><td>\n\nRecords\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nreference\n\n</td><td>\n\nReference\n\n</td><td>\n\nYes\n\n</td><td id=\"ReferenceField\">\n\nQuery field that displays records from another table, which is crucial for relational data structures.\n\n</td></tr><tr><td>\n\nreference\\_name\n\n</td><td>\n\nReference Name\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nrelated\\_tags\n\n</td><td>\n\nRelated Tags\n\n</td><td>\n\nYes\n\n</td><td>\n\nField used to categorize and organize records by assigning tags. In the record page, The tags are editable using the option on the form and the same tags get reflected on the related\\_tags field type in a read only mode.\n\n</td></tr><tr><td>\n\nreminder\\_field\\_name\n\n</td><td>\n\nReminder Field Name\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nrepeat\\_count\n\n</td><td>\n\nRepeat Count\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nrepeat\\_type\n\n</td><td>\n\nRepeat Type\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nreplication\\_payload\n\n</td><td>\n\nReplication Payload\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nschedule\\_date\\_time\n\n</td><td>\n\nSchedule Date/Time\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nschedule\\_interval\\_count\n\n</td><td>\n\nSchedule Interval Count\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nscript\n\n</td><td>\n\nScript\n\n</td><td>\n\nYes\n\n</td><td>\n\nText field that accepts JavaScript code input and provides controls, such as syntax checking and formatting. It also provides a list of fields and server APIs. You must specify a dependent field that references the table name for the list of fields.\n\n</td></tr><tr><td>\n\nscript\\_client\n\n</td><td>\n\nScript Client\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nscript\\_plain\n\n</td><td>\n\nScript \\(Plain\\)\n\n</td><td>\n\nYes\n\n</td><td>\n\nText field that accepts JavaScript code input and provides controls, such as syntax checking and formatting.\n\n</td></tr><tr><td>\n\nscript\\_server\n\n</td><td>\n\nScript Server\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nshort\\_field\\_name\n\n</td><td>\n\nShort Field Name\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nshort\\_table\\_name\n\n</td><td>\n\nShort Table Name\n\n</td><td>\n\nYes\n\n</td><td>\n\nText field that stores a compact version of a table name, often used for efficiency in system configurations, URLs, or logs. It helps map the full table names to shorter identifiers, mainly for internal system use rather than direct user interaction.\n\n</td></tr><tr><td>\n\nsimple\\_name\\_values\n\n</td><td>\n\nName-Value Pairs\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nslushbucket\n\n</td><td>\n\nSlushbucket\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nsnapshot\\_template\\_value\n\n</td><td>\n\nSnapshot Template Value\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nsource\\_id\n\n</td><td>\n\nSource ID\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nsource\\_name\n\n</td><td>\n\nSource Name\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nsource\\_table\n\n</td><td>\n\nSource Table\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nstring\n\n</td><td>\n\nString\n\n</td><td>\n\nYes\n\n</td><td id=\"StringField\">\n\nString field that holds a string of characters. Strings of up to 255 characters appear in a single-line text box. Anything 256 characters or over appears as a multi-line text box.**Note:** The database may translate the value that you provide in the **Max length** field to the closest matching database field type. For example, a max string length of 80 maps to the nearest database field type of VARCHAR\\(100\\).\n\nFor Oracle instances, users aren't able to increase the max length of a string field to a value greater than 4000 through the application UI. Changes greater than 4000 require the CLOB data type in Oracle. If you require a field to be larger than 4000 characters, log an incident to request the change.\n\n</td></tr><tr><td>\n\nstring\\_boolean\n\n</td><td>\n\nString Boolean\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nstring\\_full\\_utf8\n\n</td><td>\n\nString \\(Full UTF-8\\)\n\n</td><td>\n\nYes\n\n</td><td id=\"entry_StringUTF8Field\">\n\nString field that contains UTF-8 character encoding. This field type is restricted to the same maximum length that can be defined within the application UI as the String data type. Emojis are supported in the String \\(Full UTF-8\\) field type.\n\n</td></tr><tr><td>\n\nstructure\n\n</td><td>\n\nStructure\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nsys\\_class\\_name\n\n</td><td>\n\nSystem Class Name\n\n</td><td>\n\nYes\n\n</td><td>\n\nSystem field that holds the table name.\n\n</td></tr><tr><td>\n\nsys\\_class\\_path\n\n</td><td>\n\nSystem Class Path\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nsysevent\\_name\n\n</td><td>\n\nSystem Event Name\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nsysrule\\_field\\_name\n\n</td><td>\n\nSystem Rule Field Name\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ntable\\_name\n\n</td><td>\n\nTable Name\n\n</td><td>\n\nYes\n\n</td><td id=\"entry_TableName\">\n\nString field that lets you select a table. If you use the **Field Name** field type, add this field type and make the **Field Name** field dependent on the **Table Name** field.If you're in a scoped application, you can view only the tables of that scope.\n\n</td></tr><tr><td>\n\ntemplate\\_value\n\n</td><td>\n\nTemplate Value\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ntime\n\n</td><td>\n\nTime\n\n</td><td>\n\nNo\n\n</td><td id=\"entry_TimeField\">\n\nTime field that stores a time in the database as a **Date/Time** field, but only the time part of this field is used.**Note:** This field stores the date as 1970-01-01, which doesn't fall within the dates for Daylight Savings Time \\(DST\\). As a result, the time isn't adjusted automatically for DST. If a custom feature uses time as a start time, the feature must adjust for DST, if necessary.\n\n</td></tr><tr><td>\n\ntimer\n\n</td><td>\n\nTimer\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ntranslated\n\n</td><td>\n\nTranslated\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ntranslated\\_field\n\n</td><td>\n\nTranslated Field\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ntranslated\\_html\n\n</td><td>\n\nTranslated HTML\n\n</td><td>\n\nYes\n\n</td><td id=\"TranslatedHTML\">\n\nHTML text field that displays translations based on the user's language.\n\n</td></tr><tr><td>\n\ntranslated\\_text\n\n</td><td>\n\nTranslated Text\n\n</td><td>\n\nYes\n\n</td><td id=\"entry_TranslatedTextField\">\n\nText field that displays translations based on the user's language.\n\n</td></tr><tr><td>\n\ntree\\_code\n\n</td><td>\n\nTree Code\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\ntree\\_path\n\n</td><td>\n\nTree Path\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nurl\n\n</td><td>\n\nURL\n\n</td><td>\n\nYes\n\n</td><td id=\"entry_URLField\">\n\nString field that is a selectable URL field when locked. When configuring, there’s an option to allow/disallow links with or without HTTPS.**Note:** In the mobile UI, this field appears as a multi-line text field. The field saves as a single line with the line breaks removed.\n\n</td></tr><tr><td>\n\nuser\\_image\n\n</td><td>\n\nImage\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nuser\\_input\n\n</td><td>\n\nUser Input\n\n</td><td>\n\nYes\n\n</td><td>\n\nUser input field that captures input provided by users, typically in the context of workflows, surveys, or other interactive processes. This field enables users to enter text, select options, or provide other types of input that can then be processed or stored for further use.The data collected through **User Input** fields is often used to guide decision-making in workflows or to gather information for reporting and analysis. It's a flexible field type that can be customized to fit various use cases where user interaction is required.\n\n</td></tr><tr><td>\n\nuser\\_roles\n\n</td><td>\n\nUser Roles\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nvariable\\_conditions\n\n</td><td>\n\nVariable Conditions\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nvariable\\_template\\_value\n\n</td><td>\n\nVariable Template Value\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nvariables\n\n</td><td>\n\nVariables\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nversion\n\n</td><td>\n\nVersion\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nvideo\n\n</td><td>\n\nVideo\n\n</td><td>\n\nNo\n\n</td><td>\n\nVideo field for uploading and embedding video.\n\n</td></tr><tr><td>\n\nweek\\_of\\_month\n\n</td><td>\n\nWeek of Month\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nwide\\_text\n\n</td><td>\n\nWide Text\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nwiki\\_text\n\n</td><td>\n\nWiki\n\n</td><td>\n\nYes\n\n</td><td>\n\nString field with a built-in wiki text editor that accepts a simplified version of standard wiki text formatting.\n\n</td></tr><tr><td>\n\nwms\\_job\n\n</td><td>\n\nWMS Job\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nworkflow\n\n</td><td>\n\nWorkflow\n\n</td><td>\n\nYes\n\n</td><td>\n\nList field that displays a stage in a workflow.\n\n</td></tr><tr><td>\n\nworkflow\\_conditions\n\n</td><td>\n\nWorkflow Conditions\n\n</td><td>\n\nNo\n\n</td><td>\n\n \n\n</td></tr><tr><td>\n\nxml\n\n</td><td>\n\nXML\n\n</td><td>\n\nYes\n\n</td><td>\n\n \n\n</td></tr></tbody>\n</table>"}}