Testing Page
See the "Testing Scenarios" and "How to Test" sections below for full details about the various flows and guidance on how to test each.
Suggested QA Portal Forms for Testing this Module:
To test other forms, edit this page and update the form using the "Form field" setting in the "Form" collapsed configuration field in the module.
Note: As of Feb 2026, the RFF is only compatible with forms where the user is redirected to a new page after submission, pending the completion of CSOL-4684: [RFF] [DEV] In-Line Thank You Message. Therefore, at this time, clicking Submit is not strictly necessary for the purposes of UX testing the form flow.
Below are the four possible scenarios in the RFF and how to test each on this page.
For more information about each scenario, check out the RFF Wiki page.
Eliminates all known lead fields. If non-lead RFF eligible fields are present on the form, these will be displayed.
When the user enters their email in the first step and clicks "Next," the email is checked against the contacts data in the portal. If there is a matching contact, any fields for which we have data are removed from the form.
If no Contact record matches the provided email, the email's domain is checked for a matching Company record (e.g. jdoe@microsoft.com matches the Microsoft). For matched companies we can remove up to 3 fields from the form: Website, Company Name, and Employee Count.
In cases where no data can be found for the user, the form will render all RFF eligible fields as normal.
How to Test:
First test scenario #2 using a fresh incognito window, ensuring you have selected the "Accept Cookies" option on the page before submitting the form (once you submit, a cookie will be saved associated with that contact record).
Then, to test scenario #1, refresh/revisit the page in the same incognito session.
Expected Result: Your email address should be pre-filled in the first step of the form and you should see the privacy policy and submit buttons.
How to Test:
Note: If you are also planning to test scenario #1, make sure you "Accept All" cookies before submitting, and you can then reuse the same incognito session for testing scenario #1 above.
In a new incognito window, submit the form above with any email that's associated with a contact in this portal. A few you can try include:
Expected Result: Upon clicking "Next", if the associated form has no non-lead, RFF eligible fields, you should see the final step of the form with the privacy policy and submit buttons.
How to Test:
In a fresh incognito window, submit an email address with a domain associated with a company in this portal, but no associated contact record. For example, rff-test.com. We suggest using the "plus addressing" approach to easily submit variations of a testing account:
Expected Result:
Upon clicking "Next," you should see a subset of the lead field forms like "First/Last Name" and "Phone Number" but not "Website" or "Company Size."
In a fresh incognito window, submit an email address not associated with a Contact or Company record, e.g. a gmail account. Example:
Expected Result: Upon clicking "Next" you should see steps for all remaining form fields for the user to complete.
As noted on the RFF Wiki page, the RFF was designed to be used with MarTech approved QL Forms, specifically those containing the lead fields. However, the RFF should work with any form that meets the criteria listed on the wiki under "Form Requirements for RFF."
Glossary of Terms: