1. A “UOA FormBuilder” Template is used to create a form on “aem. test
A “UOA FormBuilder” Template is used to create a form on “aem.test.auckland.ac.nz”

2. The “Form” component from the “Form” set is dragged in and is configured as per usual to send mail

3. The “Radio Group” component from the “UOA FormBuilder” set is dragged in between start and end of the form and is configured as shown below.

4. The “Text/TextArea Input Field” component from the “UOA FormBuilder” set is dragged under “Radio Group Test” component and is configured as shown below.
A conditional (show/hide) rule is also configured on the element as shown below.

5. The “File Upload” component from the “UOA FormBuilder” set is then dragged underneath “Text Area Test” component and configured as shown. There is no conditional (show/hide) on “File Upload Test”

6. This slide shows the “Messages” and “File Property” tabs of the file upload and their configuration. No constraints have been set.

7. Finally a submit button is added and the form is activated
Finally a submit button is added and the form is activated. The following shows how the form looks online. The text field does not initially load as it has been configured to only show when “3” is selected in “Radio Group Test”

8. Clicking on the upload now and attempting to upload any file/image does not trigger an error but does not result in the file upload component showing that the file has been uploaded.
No change in text of file upload component from “File upload Testing”
This error occurs regardless of what is selected in “Radio Group Test” and regardless of what is entered within the textbox.

9. When the from the form submission is viewed in the dummy_ it can be seen that the file has actually come through upon submission even though no response was given to the form user that the file had been successfully uploaded.

10. When our team brought up the issue with Sapient Nitro they investigated and responded with the following
This is happening because of Abacus.js which OOTB file which implements the show/hide functionality. Regardless of the OOTB functionality, we have gone ahead and investigated the issue and below is the details of the fix that can be applied. File:- abacusLink.js Path:- /etc/clientlibs/foundation/abacus/source/abacusLink.js Line No: Before:- } else if (target.attr("type") !== "button") { After:- } else if (target.attr("type") !== "button" && target.attr("type") !== "file") { Since it is an OOTB script, we are not providing it as part of the code. UoA would have to make the change onto the test instances manually as the core library updates should be deployed only once. Once the change is applied, the recommendation is to clear browser cache and try testing again.