All Segment Fields Tab

Overview

The All Segment Fields tab allows configuration of field properties across all segments of a form type from a single page. Use this page to set display options, required status, visibility, initialization/update, and other properties for all fields used in the form. Form builders can still access individual segments and fields through the Pages tab as needed.

Navigation: Main Menu > Manage GT eForms 3.x > Form Setup – All Segment Fields tab

Features

Filters

For larger forms, the list of fields displayed on this page will be lengthy. To help narrow it down, three filtering fields are provided. All three filters work together when you click Search/Refresh. Each filter includes prompts based on the values used in current form type. However, you can also enter partial values in these filter fields. By default, the filtering performs a “begins with” match, but you can use SQL wildcard characters (_ and %) for more flexible searches. For any filter field left blank, no filtering will be applied for that value.

Note: Clicking Search/Refresh reloads the grid data from the database. Any unsaved changes will be lost unless you first click Apply Changes.

Field	Use
Segment	You may use the prompt to select from segments used on the current form type, or type in a partial value to match on. After choosing a value, clicking the ‘search/refresh’ button populates the grid with only those fields found on segments used on the current form type that match.
Record Tag	You may use the prompt to select from record tags used on the current form type, or type in a partial value to match on. After choosing a value, clicking the ‘search/refresh’ button populates the grid with only those fields found on record tags used on the current form type that match.
Field Name	You may use the prompt to select from all fields used on the current form type, or type in a partial value to match on. After choosing a value, clicking the ‘search/refresh’ button populates the grid with only those fields used on the current form type that match.
Search/Refresh	Use this button to filter the Fields grid based on the parameters you provide in the Segment, Record Tag, and Field Name fields.
Clear Filters	Use this button to clear all filters and load all fields in your form.

Fields Grid

The fields grid contains two tabs. The first tab, Field Properties, shows values specific to each field by segment. The second tab, Form Field Links, shows values specific to each field by record tag.

Please note, because the grid is loaded by segment field instances, a single record tag field may appear more than once if it exists on multiple segments. When this occurs, any changes made on the Form Field Links tab will automatically sync across all rows that share the same record tag field.

Field Properties

Form Field Links

Field	Use
Segment	Displays the Segment ID as a clickable link. Clicking the link opens the segment’s configuration page in a modal.
Segment Label	Displays the label defined for the segment.
Field Alias	Displays the record.field alias for the field (e.g., PAGEREC.BUSINESS_UNIT).
Label	Update the field label that displays on the form to end users.
Display Only	Update the display only property for the field Yes: display only No: editable field Dynamic: when selected, a Visual If icon will appear. Configure a Visual If expression to control when the field is display-only.
Required	Update the required property for the field Yes: required No: not required Dynamic: when selected, a Visual If icon will appear. Configure a Visual If expression to control when the field is required.
Show	Update the show property for the field Yes: visible No: hidden Dynamic: when selected, a Visual If icon will appear. Configure a Visual If expression to control when the field is shown.
Deferred	Update the deferred property for the field: Calculated: (default value) The framework determines whether field change processing can be deferred based on downstream dependencies. Off: Forces a field to NOT defer processing even if the framework determines it can be. One reason to do this is to force a trip on fields that benefit from validating formatting after the user leaves the field, such as date and number fields. On: Forces a field to be deferred even if the framework determines something depends on it on it. The dependencies will get resolved for deferred fields during the next trip that is triggered.
Initialize From	Dropdown to select how the framework should generate the value to appear in the field when the form initially loads. Dropdown Options = Constant, Data Pool, or Smart Source
Initialize From Data Pool	Enter a data pool smart source that will return a value based on the keys set on the data pool. The returned value will populate this field on form load
Initialize From SmartSrc	Enter a dynamic smart source value to populate this field on form load. Note: if your smart source is a data pool smart source, this option should not be used, and “Initialize from” should be set to Data Pool instead.
Initialize From Constant	Enter a static value to populate this field on f orm load. Constant values should obey field types (dates for date fields, code values for code fields)
Update When This Source Changes	Enter any smart source to populate this field. This logic will only run once the form is open and once any fields the smart source is dependent on change.

Applying Changes

After making changes, two Apply Changes buttons will appear. Clicking either of these buttons will immediatly apply the changes to the form setup. Once all the changes have been made and applied, a build of the form type is then required. Navigating away, even to other tabs in Form Setup, without using Apply Changes will cause unapplied changes to be lost.

The Apply Changes buttons display after any change is made within the Fields grid.