TX Forms Resolved Defects
To view Release Notes, see TX Forms Release Notes
December 2024
Base Version 2412.0
- (CL-2246) File uploads display appropriate icons for file types that cannot generate a preview on TX Forms. Previously, these files showed a broken image icon in the preview.
November 2024
Base Version 2411.14
- (CL-2236) The Case object can be used when building a TX Form. Previously, it was not an option.
- (CL-2237) Long text fields on forms now display in full. Previously, the text was truncated, with an option for users to "View More."
October 2024
Base Version 2410.6
- (CL-2220) When the Submit button is clicked, error messages are now read aloud by screen readers. Previously, users who clicked Submit wouldn't hear the error message and were unaware they had missed the required fields.
September 2024
Base Version 2409.0
- (CL-2115) The General TX Forms embed code displays properly. Previously, when a General TX Form was embedded in a webpage, the form did not display properly.
August 2024
Base Version 2408.2, Events Version 2408.0
- (CL-2178) Hidden fields set to populate Account on a Contact record save correctly. Previously, when a hidden field was configured to populate Account on the Contact record, the Accountid set as the default value was not being saved.
July 2024
Base Version 2407.11
- (CL-2169) Leading and trailing spaces in text fields are removed during form submission. Previously, leading and trailing spaces in matching fields were saved, causing duplicate records to be created.
- (CL-2192) Application Form Types with matching criteria on both Contact and Application match records correctly. Previously, using an Application Form Type and matching criteria on both Contact and Application did not match using the Contact Name or Contact ID fields to match the correct Contact records.
June 2024 Hotfix
TX Forms (Base Version 2407.10)
- (CL-2192) Application Form Types with matching criteria on both Contact and Application match records correctly. Previously, using an Application Form Type and matching criteria on both Contact and Application did not match using the Contact Name or Contact ID fields to match the correct Contact records.
June 2024
Base Version 2406.0
- (PD-6559) When a student uses the reset button for a repeated section, the text area character count resets correctly. Previously, the text area character count did not reset until the student began typing in it again.
- (PD-6561) You can add Repeatable sections with Visibility Conditions dependent on a Boolean field without error. Previously, for repeatable sections with visibility conditions dependent on a Boolean field, the builder sometimes crashed when attempting to add another record.
- (PD-6563) Option groups display correctly in the TX Form Builder. Previously, when a picklist was assigned to a field on one object, and option groups were introduced based on a field from a different object as criteria, the criteria for the option groups would not appear until a question related to the first object was chosen.
March 2024
Base Version 2403.20
- (CL-2085) The Confirmation message can now be removed from TX Forms. Previously, deleting the Confirmation message did not work properly.
- (CL-2113) You can access TX Forms in Event Registration on mobile devices and navigate various picklists in the new UI. Previously, when you accessed a TX Form in Event Registration on a mobile device, you encountered large amounts of white space and difficulty navigating picklists.
- (CL-2119) Embedded forms behave as expected. Previously, embedded forms displayed the left panel when it shouldn't, and the Done button appeared and redirected you away from the page.
- (CL-2121) Unknown School is an available option in the School Picker. Previously, Unknown School was not listed as an option, and users received the message ‘No results found.’
February 2024
Base Version 2402.4
- (CL-1905) Forms created before the February ’23 release with Option Group conditions based on the Inquiry object will load data correctly. Previously, existing Option Group conditions based on the Inquiry object did not load, and users had to re-select the conditions to Save.
December 2023
Base Version 2312.1
- (CL-2011) Conditional text displays only when conditions are met. Previously, conditional text would continue to display when conditions were no longer met.
November 2023
Base Version 2311.0
- (CL-1993) Autocomplete fields pre-fill and display the value from the field set in the Answer list. Previously, autocomplete fields displayed the Account Name.
October 2023
Base Version 2310.0
- (CL-1990) Submitting a TX Form when a matching field contains an apostrophe submits without error and creates or updates a Contact record. Previously, submitting a TX Form with an apostrophe in one of the matching fields would generate an error and create a TargetX Log entry.
September 2023
Base Version 2309.3
- (CL-1955) Events TX Forms no longer generate an error once saved. Previously, Events TX Forms attempted to validate URL redirects and prevented you from saving with the error “Redirect is not an accepted URL format.”
June 2023
Base Version 2306.3
- (PD-4526) TX Forms Disclaimer fields display line breaks. Previously, when a Disclaimer was displayed to students, the line breaks added in the Builder did not appear.
May 2023
Base Version 2305.9
- (CL-1886) TX Forms using reCAPTCHA will load properly using embedded code in an iframe. Previously, reCAPTCHA was not loading properly.
April 2023
Base Version 2304.6
- (CL-1879) File Uploads Labels, which are very long, will wrap and move surrounding fields down. Previously, long labels for File Uploads caused the text to overlap other input fields.
- (CL-1884) TX Forms can be included on websites using the form’s embed code. Previously, embedded forms using iframe would not display properly.
- (PD-5578) Forms with File Uploads will create a child object record if only one field is filled out. Previously, form File Uploads were not creating child object records if only one field was completed.
February 2023
BASE VERSION 2302.17
- (CL-1785) TargetX Logs were not being created when a field was missing from permissions for Inquiry forms.