Default Content Rendering
What does it do
It receives a hash and all POST/GET parameters you want and forwards it to a Journey, resulting in the content (not specifically HTML but the end result of the Journey needs to be a Page in any case) inside the browser.
The content renderer will normally be deployed on the same location for every customer. It will be available on url https://yoursolutiondomain/renderers/...?ID=xxxxx. The hash ID of the page has to be filled in after the equal sign.
Handlers/pages
Within the content renderer, a set of handlers and pages can be used
Active handlers/pages
Name | Type | Description |
---|---|---|
DEFAULT.ASPX | Page |
This web page will contain the content of the Engage page. The html header and html body will be printed out in the body tag of the page one after the other. The html header will not be put in the header tag of this page |
BODY.ASHX | Handler |
This handler will only return the html body of the Engage page |
JSON.ASHX | Handler |
This handler returns the html head and html body of the Engage page in a json
format.
|
HEAD.ASHX | Handler |
This handler will only return the html head of the Engage page. It is the most recent addition of the content renderer. |
DOWNLOAD.ASHX | Handler |
This handler will return the html body of the page and open this as a file. The parameter filename can be used here in the url to specify the name of the document that will be generated.
|
XML.ASHX | Handler |
This handler will return the html head, html body and html body attributes of the Engage page in an xml format. Copy
Example:
|
Deprecated handlers/pages
These handlers are still used on some older installs but will not be used any more for new clients. No real support will be given any more.
Name | Type | Description |
---|---|---|
BODY.ASPX | Page |
This content renderer will only return the content of the html body of the Engage page. |
EMPTY.ASPX | Page |
This page will only return the html body of the Engage page. |
JSON.ASPX | Page |
This page returns the html head and html body of the Engage page in a json format |