portal questions are used within catalog items docid\ bfgj8ynh1hsi8zaeyyopc to gather the necessary information required to have all of the information necessary to fufil the catalog item's workflow this could be mandatory data, approvers, or other information used by automation or service agents to resolve the request questions have a many to one (many 1) relationship with catalog items, meaning that a question can only exist on one catalog item at a time question configuration true false 227,270false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type question datatypes & configuration options the following datatypes and configurations are available for questions acknowledgement acknowledgement fields allow for agreement or attestation to a specific condition when marked as mandatory, they must be selected before submission can occur boolean boolean values allow for capturing both the true or false outcome of a field booleans have two (2) available rendering options; checkbox (the default display), or switch (offering more visual distinction between true and false values) choice choice fields offer a means to create a predefined selection of choices that the end user can select from choices can be rendered as a standard choice field (the default display), or as multi choice (allowing the user to make multiple selections, similar to multiple reference fields), or radio buttons date date fields allow for selection of a date from a calendar picker date fields can be used in conjunction with validation scripts to ensure more complex logic is handled (for example, not being able to specify a date in the past) date fields have a number of default form functions ootb that allow for rapid selection of the dynamic default data, including yesterday today, tomorrow, last, this and next week, last, this, and next month, last, this and next quarter, last and next 30 days, last and next 60 days, last and next 90 days, last and next 3 months, last and next 6 months, last and next 9 months and last and next 12 months, date and time date and time fields function the same as date fields, but allow for additional selection of a time field date and time fields can be used in conjunction with validation scripts to ensure more complex logic is handled (for example, not being able to specify a date in the past) date and time fields have a number of default form functions ootb that allow for rapid selection of the dynamic default data, including yesterday today, tomorrow, last, this and next week, last, this, and next month, last, this and next quarter, last and next 30 days, last and next 60 days, last and next 90 days, last and next 3 months, last and next 6 months, last and next 9 months and last and next 12 months, decimal allows for capturing decimal data includes ootb validation of appropriate decimal fields additional render options for decimals include accounting identifies decimal values as accounting figures, including different rendering of negative numbers decimal ootb rendering rating (number) allows for numerical ratings to be captured for a field percentage renders the deicmal as a percentage rating allows the user to select a star rating for a field text removes all rendering and captures data as static text html html fields allow for rich text editing within the catalog item; useful for more complex fields or for copying+pasting from other systems integer captures data as an integer (number) and includes ootb validation of the field integers can be rendered in the same ways as a decimal field, including accounting identifies decimal values as accounting figures, including different rendering of negative numbers decimal ootb rendering rating (number) allows for numerical ratings to be captured for a field percentage renders the deicmal as a percentage rating allows the user to select a star rating for a field text removes all rendering and captures data as static text money renders the input as a money field, and includes the user's configured currency as the output format multiple reference multiple reference fields create correlation between a form to a table allowing the user to select multiple records from other tables within servicely there are many possible use cases for this, but one of the most common is for identifying approvers for the catalog item mutiple reference fields can also benefit from reference filter docid 01hgnetwa vhssq15nimw to ensure that only appropriate fields can be selected reference reference (like multiple references) fields create correlation between a form to a table allowing the user to select a single record from other tables within servicely there are many possible use cases for this, but one of the most common is for identifying approvers for the catalog item reference fields can also benefit from reference filter docid 01hgnetwa vhssq15nimw to ensure that only appropriate fields can be selected string string fields can be used to capture a single line of text from the user submitting the form text text fields can be used to capture mutliple lines of text from the user submitting the form, without any rich text editing