Existing HTML Templates into Web Forms | Community
Skip to main content
E
eriku40433679
Level 3
February 15, 2018
Solved

Existing HTML Templates into Web Forms

  • February 15, 2018
  • 2 replies
  • 1893 views

Hi guys,

We have a pre existing form that we want to host host within Campaign as a Web App form and serves to control certain fields of the recipient record. The raw html form has custom css and javascript to drive behaviour similar to Bootstrap CSS components butweI would like to tie the values of these components into the recipient fields.

Is there an easy way to achieve this with out first starting with the HTML generated by campaign and having the design agency work around it?

Thanks,

--Erik

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by eriku40433679

Hi guys,

Since I haven't heard back from anyone after 5 days and couldn't find any thing specific in the docs, this may not be how Adobe intended the feature to be used. I'd like to share our workaround for anyone else who have to do the same thing. Please share your idea if you have a better one.

We decided to keep the original form generated by Campaign but made it invisible via CSS. We then used our original HTML template as a static container in the Web app and used javascript to map the values of the custom forms, to the original campaign forms. Ugly, but it works.

Hopefully there's a simple way to map them that I missed as the "generated form" approach seems highly backwards; considering there are more modern options  available to build these forms. Reminds me a bit of the mess that was GWT...

Cheers!

--Erik

2 replies

E
eriku40433679AuthorAccepted solution
Level 3
February 18, 2018

Hi guys,

Since I haven't heard back from anyone after 5 days and couldn't find any thing specific in the docs, this may not be how Adobe intended the feature to be used. I'd like to share our workaround for anyone else who have to do the same thing. Please share your idea if you have a better one.

We decided to keep the original form generated by Campaign but made it invisible via CSS. We then used our original HTML template as a static container in the Web app and used javascript to map the values of the custom forms, to the original campaign forms. Ugly, but it works.

Hopefully there's a simple way to map them that I missed as the "generated form" approach seems highly backwards; considering there are more modern options  available to build these forms. Reminds me a bit of the mess that was GWT...

Cheers!

--Erik

florentlb
florentlb
Level 10
March 12, 2018

Hi Erik,

Thanks for sharing your workaround. I'm not really familiar with this feature so I don't have any other idea than what you are doing.

Florent

Terms & ConditionsAccessibility statement

Loading footer...