We have installed Tridion UI 2012. We will implement it for our dynamic web sites (based on Tridion CWA framework) but we are also investigating to use it in relation with our E-Marketing (Outbound E-mail) implementation.

Today our Outbound E-mail implementation is fully static. No Broker DB, mirror pages are directly published as HTML files on a web server (live or staging).

When we configure UI 2012 for these pages, all works (Inline editing tags are correctly included and interpreted) except the Session Preview.

Each time we edit a page, a warning message appears on the top of the window : "The preview for this page is not up to date". If we click on the button "Update the page preview" the message still appears and modifications are not displayed. If we publish modifications on the staging server then all is ok.

My questions:

• Is there a way to configure the Session Preview in this kind of implementation WITHOUT transforming the staging environment into a "dynamic implementation" (java or .net) ?
• According to the documentation, it seems that the only way to enable session preview is to configure a preview claimstore. Is there an alternative way (don't know. Maybe based on AJAX direct calls to the preview webservice for ex) ?

We have installed Tridion Experience Manager 2012. We will implement it for our dynamic web sites (based on Tridion CWA framework) but we are also investigating to use it in relation with our E-Marketing (Outbound E-mail) implementation.

Today our Outbound E-mail implementation is fully static. No Broker DB, mirror pages are directly published as HTML files on a web server (live or staging).

When we configure Experience Manager for these pages, all works (Inline editing tags are correctly included and interpreted) except the Session Preview.

Each time we edit a page, a warning message appears on the top of the window : "The preview for this page is not up to date". If we click on the button "Update the page preview" the message still appears and modifications are not displayed. If we publish modifications on the staging server then all is ok.

My questions:

• Is there a way to configure the Session Preview in this kind of implementation WITHOUT transforming the staging environment into a "dynamic implementation" (java or .net) ?
• According to the documentation, it seems that the only way to enable session preview is to configure a preview claimstore. Is there an alternative way (don't know. Maybe based on AJAX direct calls to the preview webservice for ex) ?