Discussions

Classic Design Editors: Sunset of Some Form Functionality (Feb 2020)

JodyMooney-Oracle
JodyMooney-Oracle Product Management, EloquaPosts: 349 Employee
edited Apr 29, 2022 6:27AM in Eloqua
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.  

Overview

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.

What’s changing?

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.

Timeline

Feature19B19C19D20A
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

Next Steps

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.

Additional Resources

Learn more about the responsive design editors in the Oracle Help Center:

FAQ

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

Post edited by OIT Integration User on
«1

Comments

  • When classic forms will be in 'view-only' mode, will customers still be able to save-as-new these forms?

  • Cheli
    Cheli Posts: 29 Gold Medal

    When classic forms will be in 'view-only' mode, will customers still be able to save-as-new these forms?

    Good question!  I hope so!

  • Good question!  I hope so!

    Thanks, @Cheli. I'm pretty sure the answer will be YES, but I just want double-check.

  • Hi,

    Once the Classic Forms move to the View-only mode, marketers will still be able to clone these forms to their Responsive clones through the same Save As and Save as Template options. The only functionality that will be removed will the the ability to Edit the native forms. Also, as mentioned in the FAQs above, the native forms will continue to function without trouble even after they have been moved to the View-only mode. Hope this clarifies.

  • Matt Stringer
    Matt Stringer Posts: 16 Blue Ribbon

    What is the plan for Progressive Profiling?  Will it be available on Responsive Forms?  Documentation currently stays that Progressive Profiling is only available with the Classic Editor.

    https://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAA/Help/Forms/ProgressiveProfiles/ProgressiveProfiles.htm?Highlig…

    2019-05-16_1236.png

  • What is the plan for Progressive Profiling?  Will it be available on Responsive Forms?  Documentation currently stays that Progressive Profiling is only available with the Classic Editor.

    https://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAA/Help/Forms/ProgressiveProfiles/ProgressiveProfiles.htm?Highlig…

    2019-05-16_1236.png

    With the Eloqua 19B Release, Progressive Profiling will be also available for our new responsive Form Design Editor.

  • Lauren.cocco
    Lauren.cocco Posts: 3 Red Ribbon

    "Note: 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."

    19B has just been released for my POD. I tried using the Save As features for my classic forms to save them as responsive forms, as described in the 19B release notes, but it didn't work. I could only Save As classic forma as classic forms. Will this functionality be coming later or is my approach wrong?

  • Piyush Kumar Eloqua-Oracle
    edited May 21, 2019 7:29AM

    "Note: 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."

    19B has just been released for my POD. I tried using the Save As features for my classic forms to save them as responsive forms, as described in the 19B release notes, but it didn't work. I could only Save As classic forma as classic forms. Will this functionality be coming later or is my approach wrong?

    Hi Lauren,

    Thanks for reaching out. I have looked into your Eloqua instance and have found the process of converting forms from the classic to responsive forms to be working as expected. I have recorded my actions in a screen recording that I'd love to share with you so that you can check if you have followed the same steps. Please let me know how I can share this with you. Meanwhile, you can look at the help document available at https://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAA/Help/Forms/Tasks/ConvertClassicFormToDesignForm.htm where we have outlined the steps you can perform as well.

    Thanks.

    Post edited by Unknown User on
  • Lauren.cocco
    Lauren.cocco Posts: 3 Red Ribbon
    edited May 21, 2019 9:39AM

    Hi Lauren,

    Thanks for reaching out. I have looked into your Eloqua instance and have found the process of converting forms from the classic to responsive forms to be working as expected. I have recorded my actions in a screen recording that I'd love to share with you so that you can check if you have followed the same steps. Please let me know how I can share this with you. Meanwhile, you can look at the help document available at https://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAA/Help/Forms/Tasks/ConvertClassicFormToDesignForm.htm where we have outlined the steps you can perform as well.

    Thanks.

    Hi Piyush - I works for me now. I can't think of what I did differently today vs yesterday, but it works and that's all that matters. Thank you!

    Update: I see what I did. If you create a form from a classic template and "Save As" the unsaved form, it will create the form in the classic editor. If you open a saved classic form then Save As it will create the new form in the responsive editor.

    Post edited by Unknown User on
  • Hi, in the 19B briefing, it was communicated that:

    19C: customer will not be able to create new forms using the classic design editor.

    20B: customer forms created in the classic design editor will move to a "view-only" mode.

    Now, in the latest update: "With the arrival of the Eloqua 20A release (Feb 2020), the ability to edit or create new Classic forms will be removed."

    Can you confirm if you moved up the date from 20B to 20A in terms of removing the ability to edit classic form?

  • Dave Zeltser
    Dave Zeltser Posts: 34 Bronze Medal

    One of the biggest concerns we have with the old forms being locked down and uneditable is being able to re-use the HTML form name on the new forms. We would need the ability to edit the HTML form name for example from LEAD-FORM to LEAD-FORM-OLD so that we can repurpose the LEAD-FORM value in our new responsive form.

    Without this, we risk interruptions in our data. We have roughly 2000 live forms receiving submissions from literally tens of thousands of landing pages and web sites.

    I hope others bring up this concern if you are using external landing pages that post to Eloqua forms!

    Thanks,

    Dave

  • One of the biggest concerns we have with the old forms being locked down and uneditable is being able to re-use the HTML form name on the new forms. We would need the ability to edit the HTML form name for example from LEAD-FORM to LEAD-FORM-OLD so that we can repurpose the LEAD-FORM value in our new responsive form.

    Without this, we risk interruptions in our data. We have roughly 2000 live forms receiving submissions from literally tens of thousands of landing pages and web sites.

    I hope others bring up this concern if you are using external landing pages that post to Eloqua forms!

    Thanks,

    Dave

    Hi @Dave Zeltser,

    We are currently gathering feedback on the proposed sunset plan for Forms and will update this page as and when we identify changes or additional details that need to be included in the plan. Since the sunset plan focuses on the design part of the classic forms, HTML name modification should be possible. Please watch this page for more updates around this.

    Thanks.

    Piyush Kumar

  • Jonny L
    Jonny L Posts: 6 Red Ribbon
    edited Aug 14, 2019 12:22PM

    Thanks, @Cheli. I'm pretty sure the answer will be YES, but I just want double-check.

    Hi All Sebastian/Piyush/Cheli--just wondering if there's an update on this question "When classic forms will be in 'view-only' mode, will customers still be able to save-as-new these forms?" Do you know if this is going to be possible?

  • Jonny L
    Jonny L Posts: 6 Red Ribbon

    Hi @Sebastian Zentgraf-Oracle @Piyush Kumar Eloqua-Oracle @Dave Zeltser just wondering if there's an update on this question "When classic forms will be in 'view-only' mode, will customers still be able to save-as-new these forms?" Do you know if this is going to be possible?

  • Hi @Sebastian Zentgraf-Oracle @Piyush Kumar Eloqua-Oracle @Dave Zeltser just wondering if there's an update on this question "When classic forms will be in 'view-only' mode, will customers still be able to save-as-new these forms?" Do you know if this is going to be possible?

    Hi Johnny,

    Yes, even after the classic forms move to the View-only mode, you will still be able to create their responsive versions using the Save As option. The View-only mode only restricts you from making any changes to the existing classic form, or save it as a net-new classic form using the Save As option. It can always be created as a Responsive form using the Save As option. Hope this helps.

    Thanks.

  • Sonja Halse
    Sonja Halse Posts: 2 Bronze Medal

    Hi, since the functioning existing classic forms will still work, what are the incentives for customers to transfer their classic forms into the responsive editor, when this implies extra work (both creating the new form but also potentially having to also adjust the LPs that use it)?

  • Hi, since the functioning existing classic forms will still work, what are the incentives for customers to transfer their classic forms into the responsive editor, when this implies extra work (both creating the new form but also potentially having to also adjust the LPs that use it)?

    Hi Sonja,

    Eloqua's responsive asset editors available for Forms, Landing Pages and Emails are aimed at providing marketers with two main benefits.

    1. providing state-of-the-art content creation experience across Forms, Landing Pages and Emails.

    2. Allowing for the creation of responsive assets that are rendered in the most user-friendly fashion across devices.

    Migrating older forms to the new responsive editor allows marketers to use our latest editor and leverage its enhanced form editing options, as well as an opportunity to offer their customers a more contemporary form-filling experience. This is an additional benefit since marketers can still edit forms using the classic editor.

  • claudiazoglmann
    claudiazoglmann Posts: 60 Gold Medal

    Hi Sonja,

    Eloqua's responsive asset editors available for Forms, Landing Pages and Emails are aimed at providing marketers with two main benefits.

    1. providing state-of-the-art content creation experience across Forms, Landing Pages and Emails.

    2. Allowing for the creation of responsive assets that are rendered in the most user-friendly fashion across devices.

    Migrating older forms to the new responsive editor allows marketers to use our latest editor and leverage its enhanced form editing options, as well as an opportunity to offer their customers a more contemporary form-filling experience. This is an additional benefit since marketers can still edit forms using the classic editor.

    @Piyush Kumar Eloqua-Oracle, @JodyMooney-Oracle Would you be able to clarify at which point Oracle will fully sunset Classic Forms? Unfortunately, all information around that seems to have been removed in revision 7 of this Product Notice and, as far as I'm aware, no further guidance has been given since.

  • zweiler
    zweiler Posts: 9 Blue Ribbon

    I understood, that the Classic Forms are still editable under Release 20A. So what is the new timing, when Classic Forms become non editable?

  • Thamina Christensen-Oracle
    Thamina Christensen-Oracle Group Product Manager Posts: 143 Employee

    Hi everyone,

    Because forms are an essential part of lead flow management and we don't want to disrupt that process, we will not be removing editing capabilities for Classic Forms. All net new forms will need to be created with the new form editor, but you will not have to migrate or move off an integrations you have with the Classic Forms. Again, we are not currently planning on removing editing capabilities with Classic Forms in the near future.

    Thanks,

    Thamina

  • claudiazoglmann
    claudiazoglmann Posts: 60 Gold Medal

    Hi everyone,

    Because forms are an essential part of lead flow management and we don't want to disrupt that process, we will not be removing editing capabilities for Classic Forms. All net new forms will need to be created with the new form editor, but you will not have to migrate or move off an integrations you have with the Classic Forms. Again, we are not currently planning on removing editing capabilities with Classic Forms in the near future.

    Thanks,

    Thamina

    Thanks for the feedback, @Thamina Christensen-Oracle.

    It seems quite unfortunate that Oracle has not made this position more clear after all the initial announcements towards sunsetting. A lot of clients have already or are currently in the process of allocating time and budget to migrate their Classic forms to Responsive ones.

    May I challenge your comment around “the near future”? Would you expect Oracle to sunset Classic forms later in 2020 or in early 2021 given that Oracle might want to further promote Responsive forms?

  • Thamina Christensen-Oracle
    Thamina Christensen-Oracle Group Product Manager Posts: 143 Employee

    Thanks for the feedback, @Thamina Christensen-Oracle.

    It seems quite unfortunate that Oracle has not made this position more clear after all the initial announcements towards sunsetting. A lot of clients have already or are currently in the process of allocating time and budget to migrate their Classic forms to Responsive ones.

    May I challenge your comment around “the near future”? Would you expect Oracle to sunset Classic forms later in 2020 or in early 2021 given that Oracle might want to further promote Responsive forms?

    Hi @claudiazoglmann,

    You are right that the initial announcement was confusing. Additionally after receiving feedback from many customers including a customer who would need to migrate 800+ landing pages tied to forms, we updated the product notice to not disrupt the editing capabilities of classic forms.

    Starting in our 20A (February 2020) release, a customer will not be able to create or copy any classic form. Because that functionality will no longer be available, the new form designer will naturally be promoted as the only option for new forms. As for my comment around "the near future", that is my safe harbor statement saying things could change but they won't right now. To be clear, we don't have plans to change the current plan in either 2020 or 2021.

    We did our best to update customers and make it very clear that editing would not be affected. I apologize for the unnecessary burden that you and all our customers have experienced.

    Thanks,

    Thamina

  • zweiler
    zweiler Posts: 9 Blue Ribbon

    Hi @claudiazoglmann,

    You are right that the initial announcement was confusing. Additionally after receiving feedback from many customers including a customer who would need to migrate 800+ landing pages tied to forms, we updated the product notice to not disrupt the editing capabilities of classic forms.

    Starting in our 20A (February 2020) release, a customer will not be able to create or copy any classic form. Because that functionality will no longer be available, the new form designer will naturally be promoted as the only option for new forms. As for my comment around "the near future", that is my safe harbor statement saying things could change but they won't right now. To be clear, we don't have plans to change the current plan in either 2020 or 2021.

    We did our best to update customers and make it very clear that editing would not be affected. I apologize for the unnecessary burden that you and all our customers have experienced.

    Thanks,

    Thamina

    Hello Thamina,

    Thank you for the update.

    So, it looks like we still have some time to migrate the forms. It´s not the best situation for all of us, as clients have already invested budget and we started with the form migration.

    For any future planning, I recommend to have a better research in the instances and ensure a better sunset planning.

    Thank you in advance

    Sonja

  • Hi,

    What about the HTML name, when we do a Save As then there would be 2 forms with same HTML name one in classic and one in design mode. We mostly rely on HTML names in our landing pages. Will this be a problem when we move to design mode.

    Regards,

    Srikanth

  • Hi,

    What about the HTML name, when we do a Save As then there would be 2 forms with same HTML name one in classic and one in design mode. We mostly rely on HTML names in our landing pages. Will this be a problem when we move to design mode.

    Regards,

    Srikanth

    Hi Srikanth,

    When you create a Responsive copy of a form, the newly created form's HTML name by default is "copyOf<original_form_htmlname>". For example, if your original form's HTML name was testform, the new Responsive form you create will have copyOftestform as its default HTML name.

    This behavior remains same whether you create a Responsive copy of a Legacy form via the Save As option, or create a Responsive copy of a Responsive form via either the Copy option or the Save As option. This way we avoid having two forms with the same HTML name. Hope this answers your question.

  • jdebrincat
    jdebrincat Posts: 12 Silver Medal

    We have a lot of "integrated" forms using HTTP post with 3rd party vendors. Will we be able to do a "save as" and create a responsive form, but keep the old "elqFormName" value? Otherwise, we may have issues with getting our vendors to switch all of these out.

  • Gatormain
    Gatormain Posts: 18 Red Ribbon
    edited Jan 21, 2020 12:52PM

    We have a lot of "integrated" forms using HTTP post with 3rd party vendors. Will we be able to do a "save as" and create a responsive form, but keep the old "elqFormName" value? Otherwise, we may have issues with getting our vendors to switch all of these out.

    Yes you can use that same value - that is what is set on the HTML Name configuration but must be unique. To use that previous value, you will have to edit the HTML Name on the old form so it can be used on the new form. It should only take a second to do but I'd still choose a time that the least amount of form submissions come through.

  • katp
    katp Posts: 16 Blue Ribbon
    edited Feb 13, 2020 4:12PM

    I may have missed it, but can we still add form fields or processing step after the 20a release?

  • I may have missed it, but can we still add form fields or processing step after the 20a release?

    Hi,

    Yes you will be able to edit classic forms which includes being able to modify form fields as well as processing steps. The changes made will be saved in the same form if you click on the File> Save menu option. However, if you select the File >Save As or File > Save As Template options, then the changes will be saved into a new Responsive form or template and the original classic form will not have these changes incorporated. It will continue to be in the same state as before.

    Hope this helps.

    Thanks,

    Piyush Kumar

  • katp
    katp Posts: 16 Blue Ribbon

    Hi,

    Yes you will be able to edit classic forms which includes being able to modify form fields as well as processing steps. The changes made will be saved in the same form if you click on the File> Save menu option. However, if you select the File >Save As or File > Save As Template options, then the changes will be saved into a new Responsive form or template and the original classic form will not have these changes incorporated. It will continue to be in the same state as before.

    Hope this helps.

    Thanks,

    Piyush Kumar

    Thanks Piyush! Glad we can still add fields since we have hundreds of forms that we need to update.