I would like to understand what is the best way to create Vanity URL for public facing forms.
For eg. consider a form which is rendered using a custom profile like this :
how can i mask the URL so that public facing link appears to be like:
http://hostname:4502/form1.xdp
or
http://hostname:4502/formStore/form1.xdp
I want to generalize the approach, so that a single config /mapping can be used for all the form templates which are located in the same folder.
Views
Replies
Total Likes
What is your use case?
are you trying to populate data in the form?
what kind of form is it?
Hi Girish,
We have quite simple XDPs being simply rendered as HTML / Mobile form - for now. There's no pre populated data, and these forms do not trigger any workflow.
The user can fill the form online, and then click a button to generate a flattened PDF of their form, which can be later posted via email or conventional postage.
There's a custom render profile which introduces some minor cosmetic changes to toolbar.
All our forms are in a single folder under /content/dam/formsanddocuments/<folder>
There's a public portal which currently has links to PDF forms, and those will be replaced by these new links for rendering HTML forms.
While there will be a load balancer / webserver / dispatcher layer which will conceal the actual host where AEM is running, but we also want to conceal the structure of our rendering profile, or the folder where our forms are located, which gets exposed in the URL.
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Rendering profile can be hidden
but not sure about the xdp path
what is the reason you want to hide xdp path?
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Likes
Replies