Rendering behaviour test

Help
Use this form to confirm BEHAVIOURS managed by form rendering, such as visibility, read-only, etc.

This form is to test form BEHAVIOURS that are or may be affected by form rendering.
  • It can be used to confirm that different kinds of hidden and read-only controls behave as intended during various form and process states.
  • It can be used to review how data is handled under different scenarios, such as when an entered value becomes hidden due to user actions.
To review general APPEARANCE and function of controls, visit:

These controls have an additional field that becomes available when the "Other" option is chosen. You can test the behaviour on-screen and confirm that the additional field remains unavailable if any of the first three options are chosen.
Radio Buttons with "Other"
  • Field should be unavailble until "Other" is chosen.
  • Field should cleared if option is changed.
  • Field should remain unavailable if options 1-3 are chosen.
Dropdown with "Other"
  • Field should be unavailble until "Other" is chosen.
  • Field should cleared if option is changed.
  • Field should remain unavailable if options 1-3 are chosen.

There is a Hidden Field control to the right. These controls are not meant to be visible at all outside the Form Builder.
  • It should not appear on the web form
  • It should not appear on the PDF
  • It should not appear in the email or XML

This section contains three read-only fields:
  1. One that should appear on the screen only
  2. One that has visibility set to "no" and should never appear
  3. One that should appear on the PDF only
Visibility = fr:mode() != 'pdf'

Do you want to make the field (right) read-only?
Missing or incorrect value
Switched between editable and read-only based on the control to the left.

This section has a Radio Button control, with each option displaying a supplemental control. There's a read-only control that always appears, and others that only appear once a choice is made in the supplemental controls.
 
NOTE: The 'Car' and 'Truck' read-only controls retain their value if you subsequently change the primary control value. This is intentional Orbeon behaviour. For testing, the related read-only controls are set to have visibility when the (A) the primary control matches and (B) the supplemental control has a value. This will hide a read-only field that contains a value, but is "unneccessary".
 
TEST RECOMMENDATION: Make a choice for both primary options ("Car" and "Truck"). Only your last chosen primary option should have visible supplemental and read-only fields. Having data for both options can uncover how this data is used for "all-data" and XML - if it's included or not.
What kind of vehicle would you like to rent?Missing or incorrect valueConditional supplemental controls appear based on choice.
Missing or incorrect valueAlways visible. Displays value of primary question.

Start with a PDF test.
  1. Click the PDF button.
  2. Review the PDF to confirm that values are displayed or hidden as expected.
  3. Carefully* review the on-screen form to check for display or formatting issues.
If you see any issues, try clicking on the general canvas first, then controls to determine if/how display issues resolve themselves, and document the 'corrective' action.
 
(*) On-screen display or rendering issues may resolve very quickly on screen clicks, form activation, or even key clicks. Try using the scroll wheel first.
Next do a submission test.
Changes might occur upon submission of the form.
  1. Enter your email address below.
  2. Click the Submit button.
  3. Carefully* review the on-screen form to check for display or formatting issues.
If you see any issues, try clicking on the general canvas first, then controls to determine if/how display issues resolve themselves, and document the 'corrective' action.
 
(*) On-screen display or rendering issues may resolve very quickly on screen clicks, form activation, or even key clicks. Try using the scroll wheel first.
Missing or incorrect valueYou'll get the test email and default attachments (XML, PDF), plus the contents of the form data in the email body.
The email contains some formatting and all attachments. This will help indicate if any rendering change affects PDF/XML production, separate from what's generated when clicking the PDF button.
 
The email also makes use of the "all-data" option to embed the data into the email. This is an 'experimental' and undocumented option, and it would be useful to verify what is meant be "all" data. Specific controls can be excluded, but none are in this test.
Re-check the PDF and form.
You may need to make another submission to reveal issues if they've already reset.
If you see any issues, such as hidden fields being visible, try clicking the PDF button while the issues appear on the form.
  • Does the PDF include anything that's supposed to be hidden?
Return to the form.
  • Did the issues resolve on clicking the PDF button? If so, note that.
Perform a document review.
Check the content and attachments of your email(s).
  • Does the PDF only display what it's supposed to?
  • Does the XML contain any extra fields or values? (1)
  • Does the email content contain any extra fields or values? (2)
Notes:
  1. Similar to a spreadsheet, the XML is presumed to contain a place for all values, but should not include unintended values.
  2. It's unclear if the "all-data" function is meant to be structured like the XML, or if will include hidden or non-data content (like this).
873125991a32bae643e221e508b5df58e6078f32
Confirm
Form Submitted
Review Form Validation Messages
Unable to complete action
Confirmation
Confirmation
Create link to share