Advanced field configurations give you the power to collect nuanced data, streamline form completion, and improve back-end automation. This guide walks through commonly used advanced field types and their configuration options.
When an Autocomplete field is selected, such as School Name, users can specify an Answer list, a Filter Field, and a Filter Value to display.
You can enter multiple values for the Filter Value by separating each value with a semicolon. An option will display if it contains at least one of the values listed.
Note: The Site Guest User will need Read/Edit access to the Autocomplete (lookup) field, Read access to the lookup object, Read access to the Answer List and Filter Field fields on the lookup object, and a Sharing Rule will need to be created that grants Read access to the object for the Site Guest User for any records that need to be searched.
Question fields that are checkboxes will display the options:
You can change the text for Answers, but you can NOT update the Integration Values. If you change the text, the Reset icon will reset the values to the default. Radio buttons are NOT an option for Checkbox fields.
Conditional visibility allows you to make a content block appear only when a condition is met (e.g., if someone selects a specific option).
Note: Any fields used in your conditions MUST be on the form. For example, if you create a Content Block to display only for PA residents, then you MUST have the State field on your form.
Notes on TX Forms Conditional Content:
When generating records associated with an Application, you have the option to connect these records either to the Contact or directly to the Application. This linkage is crucial for incorporating them into record matching processes and for preventing the creation of duplicate records.
To illustrate, you can incorporate fields related to enrollment history that are connected to the Contact. Subsequently, you can add a Hidden field that establishes a link between the Contact's data and the Application. Should a matching enrollment history already exist, the system will refrain from generating a new enrollment history record. In the scenario outlined below, the system will search for corresponding Enrollment History records pertaining to the Contact. In the event that a new record is necessitated, it will be affiliated with the corresponding Application:
Content Type |
Object |
Field |
Options |
---|---|---|---|
Question |
Enrollment History (Contact) |
School Name |
|
Hidden Field |
Enrollment History (Contact) |
Application |
Link to Application = Enabled Used for Matching = Enabled |
Objects connected to a Contact record allows for the storage and management of additional information related to the contact, such as notes, activities, and communications.
Note: Administrators MUST grant READ access to Site Guest Users for all fields configured on your TX Forms.
Option Groups display if you've selected a picklist field:
Notes:
Picklist fields will automatically populate with the values configured in Salesforce within a text field. You can remove or rename any of these values according to their preferences. However, it is important to note that users are unable to add new values to the picklist. The formatting of these values adheres to the following guidelines:
Label, Integration Value
When a Multi-select picklist field is selected as a field, it will display as such in the Details window:
The question will default the Salesforce configured Values in a text field, and users can remove/rename any they wish. Users can't add new values to the picklist. Values are formatted as follows:
Label, Integration Value
The URL Pre-fill option adds a Pre-fill key that can be populated and shared to Pre-fill certain fields on your form. There is a limit of five Pre-fill fields per form.
Example Pre-fill URL:
https://yourdomain.my.salesforce-sites.com/Inquiry/TargetX_Base__InquiryForm#?formId=b1MDa55555XW99MAG&formType=general&txf1=<PREFILL VALUE>
Example:
Notes:
txf1=Kudos
Test your pre-fill code on exposed fields when using special characters to ensure the pre-fill data populates correctly. This is especially important for hidden fields since you cannot see whether the field is pre-filled.
You can include Read-Only fields on your form to flag them for matching, or to reference in option groups, or visibility conditions. For example, you can include fields for the Contact ID and Application ID populated via a URL pre-fill. These fields will then be used to match a Contact/Application record when the form is submitted.
You can define a Salesforce record type when creating records using a TX Form. This is accomplished by configuring a question or setting up a hidden field. For example, to allow users to enter Advising information such as Kudos or Alerts, configure the following:
Sample Label |
Object |
Field |
Sample Values |
---|---|---|---|
Type of Advising record? | Advising (Student) | Record Type ID |
|
Category? | Advising (Student) | Category |
|
Type? | Advising (Student) | Type |
|
What is this Alert/Kudo about? | Advising (Student) | Notes/Log | <text area field> |
Hidden Field (optional) |
Advising (Student) |
Public? |
The value must be set to True to ensure newly created records appear in Student Success Center. |
Note: When using URL Pre-fill on a Record Type ID field, use the Label in the URL, not the ID. For example: txf1=Kudos
Your form would then present this to the user:
For details on submitting Faculty Early Alerts with TX Forms, see Submitting Faculty Early Alerts with TX Forms.
The School Picker is an autocomplete field used to enter a School Name. When a user types a School Name, the system autocompletes to find the institution name.
Note: Separate the values with a semicolon to add multiple Filter Values. For example, High School;College
You can configure your form to display a text field for students to enter a School Name if Unknown School is selected for the School Name.