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 field label field type purpose name string the name of the question not visible to end users on the catalog items docid\ bfgj8ynh1hsi8zaeyyopc parent reference (auto populated) catalog item where this question is visible order number numerical display order for this question determines in which order the field should be visible on the catalog item active boolean toggle status of the question only active questions will be rendered on the form preceding question reference allows for selection of prior question for rendering question string the question that will be presented to the user submitting the catalog items docid\ bfgj8ynh1hsi8zaeyyopc tooltip string the tooltip text visible to the end user when populating the form datatype choice servicely supports the usage of many different question types (alonside their own configuration options) see the question datatypes & configuration options section of this page for more detail readonly boolean determines if the field should be editable by users submitting the form mandatory boolean mandatory fields must be completed before submission can occur background only boolean the question is active, but not rendered on the form for end users helpful for more advanced use cases that require additional data that isn't presented to the end user data type options many servicely supports the usage of many different question types (alonside their own configuration options) see the question datatypes & configuration options section of this page for more detail precondition filter the precondition must be met for this question to be presented this is the mechanism for varying flows for an item, based on previous answers precondition script script in complex scenarios, a script may be run to result in a boolean value for satisfying the precondition, or set in the answer variable the questions variable can be used to access other questions by name to get their answers section title string allows for the question to sit within it's own named section of the field following questions will appear within the section unless a new section title is identified, or the question is configured to close the section close section after boolean determines if this question should be the last within it's section hide section if hidden boolean when a question is hidden (based on the precondition or precondition script), this flag allows the entire section to be hidden alongside it clear answer if hidden boolean by default, when a field is hidden the contents are not removed from the field validation script script allows for complex validation of field data alongisde the specified datatype e g , regex validation renderer choice allows the user to modify the way the datatype is rendered (e g , showing an attachment drag and drop for attachment fields instead of a reference) renderer properties properties allows for further advanced modification of the renderer record field fields copy this answer to the given field on the generated record copy display value boolean instead of copying the exact value to a field, copy the configured display value helpful when copying the name of a reference to a string field process answer script optionally process the answer the question is available as current and the initial answer is available as value replace answer boolean replace the original answer with the processed answer default from question fields default from a previously answered question typically, this would be reference field, say requestor, and the default of this answer is requestor > location if we are defaulting a location question default from function choice the default may be set from one of a number of pre defined functions, such as the current user default from script script in complex scenarios, a script may be run to result in the default value, or set in the answer variable the questions variable can be used to access other questions by name to get their answers always use default boolean determines if the script should always be run (for visiblity) or only once during the form initialisation 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