Technical Alert: Online Application Conditional Display Based on Boolean or Checkbox Fields Issue
| [10/14/22 Update]
We have released a new version of the October '22 package for Online Application: 2210.14. We recommend all clients update to this version as soon as possible. In the past 2 weeks, we identified and resolved two critical issues: CL-1767 (about saving custom objects) and CL-1773 (about boolean field visibility). In earlier versions of the October Online Application package, these fixes were missing. In 2210.14, they are both present. If you were affected by either of these critical issues, we strongly recommend you update to 2210.14 as soon as possible. A full list of the changes in this package can be found here: October '22 Release Notes. |
| [10/11/22 Update]
Our Product team has resolved the issue with Boolean/Checkbox fields in the online application. If you identified your org to be impacted, you will need to update to the newest version of the Online Application package (2210.10), which is now available in the Online Application Admin Group in the TargetX User Community. With this change, all Critical Online Application issues have been resolved. Because of this, we recommend updating to the October packages for all Online Application clients who have identified their org to be impacted. If you have any questions or issues with installing this package, please submit a case to Support via the Community. |
We have identified an issue in the Online Application package which impacts clients who are on versions released on or after August ‘22.
This issue causes Boolean/Checkbox fields displayed as picklists on the form to not display a value when the form initially loads, and Boolean/Checkbox fields displayed as picklists on the form do not retain their selected value after save and refresh. Changing the Checkbox (Boolean) field from being displayed as a picklist to being displayed as a radio button does resolve the issue of the selected value not being displayed if the applicant leaves the application and later returns.
Fields/Questions with visibility conditions based on a Checkbox/Boolean field may be shown on the form when the application initially loads, regardless if they meet the conditions. When a condition is selected for the Checkbox/Boolean (which in the application is displayed as picklist) field, the visibility conditions do not display as expected. This means that subsequent cards or questions that are conditioned based on the checkbox response do not display to the applicant. Because of this, the applicant will not have the opportunity to respond to the conditionally displayed questions.
Additionally, the application snapshot does not display the values in the snapshot after the student submits the application when the Boolean field is a picklist.
There is a risk of data loss because of this issue. We are working to correct the issue with a new package as quickly as possible.
As soon as a new package version is available, we’ll be sure to share those details and update the package links in the User Community.