Classic Design Editors: Sunset of Some Form Functionality (Feb 2020)
July 31, 2019: We have revised the dates of the sunsetting of some functionality of our Classic Form Design Editor. Please review the updated Product Notice details below for further information and additional schedule changes.
Eloqua’s new, fully responsive, Form Design Editor launched with the 19A release (Feb 2019), is now the default form editor for Eloqua. As such, we will be sunsetting some functionality contained in our Classic Form Design Editor with our 20A (Feb) release in order to maintain a modern, consistent experience for customers.
Note: Forms created with the Classic editor will continue to function throughout, and these changes do not effect form processing steps.
With the arrival of the Eloqua 20A release (Feb 2020), the ability to create or copy new Classic forms will be removed. When creating a new form, by default it will be created in the new Form Design Editor. If you open a form created in the Classic editor, you will still be able to edit the design and the processing steps.
Customers are encouraged to use the “Save As” functionality which will automatically create new, responsive versions of the forms which will be fully supported by the new Form Design Editor.
|Creating classic forms by right-clicking on a classic form and selecting copy option|
|Creating net new classic forms using the Basic Form icon in the Template chooser|
|Creating net new classic forms using the Blank Form icon in the Template Chooser|
|Saving a classic form as a template for creating classic forms using the Save as Template option|
|Saving a classic form as another classic form using the Save As function|
|Editing classic form design|
|Editing and Saving Processing steps of Classic forms|
Given as of the 20A release customers will not be able to create Classic form design elements, customers are strongly advised to use this time to review the forms they’ve created in the Classic form editor and begin creating all new forms in the new form design editor.
Some responsive forms might require updating the styling of their corresponding landing pages or webpages in order to ensure their layout is not affected. There will be periodic reminders sent by Eloqua as we approach the 20A Release, but no extensions will be provided post 20A for allowing the creation of new forms in the classic editor.
Any forms created using the classic editor will continue to function without any loss of service after the 20A release including capturing submission data and executing processing steps.
Learn more about the responsive design editors in the Oracle Help Center:
Q: Is there a way to migrate my content from the classic design editor to either the responsive design editor or source editor?
A: As of the 19B Release customers can leverage Save As Template and Save As features for your classic forms to save them as responsive forms in our new Design Editor.
Q: I have a lot of content to manage. Can I get an exception?
A: No. Oracle has premium resources such as professional services to help with any transition needs.
Q: Do I have to re-create my forms for use with the new Email and Landing Page Design Editors?
A: In most cases the responsive forms will work without any compatibility issues.
Q: Can I use the same Form ID from a Classic Form that has been saved as a new Form?
A: No. Each asset will have a unique form ID.
Q: I rely heavily on the Copy function to create copies of my forms. Can I continue using it after 20A as well?
A: No, the copy functionality will be removed per the Sunset timelines, thus removed as of the 20A (Feb 2020) release. No extensions or changes to this plan will be made outside of the plan.
Group Product Manager, CX - Marketing: Eloqua