Preview multiple presentation templates

GriffTheDog

TeamSite 6.7.1
Windows 2003

Problem: Users enter multi language data into a DCT. Each language has it's own PT and the users would like to preview both languages. After they select a PT from the "Select a Presentation Template" popup, they can't easily switch PT as the same first PT selected is now defaulted every time.

Rejected solution: save DCR, close DCT and edit DCR. This causes the "Select a Presentation Template" window to popup again, but the users find this very clumsy and time consuming.

How do I make Content Center popup the "Select a Presentation Template" every time the user clicks preview?

Is there a different direction I could be looking at to deal with this?

Thanks!

ISCBorisB

TeamSite 6.7.1 Windows 2003 Problem: Users enter multi language data into a DCT. Each language has it's own PT and the users would like to preview both languages. After they select a PT from the "Select a Presentation Template" popup, they can't easily switch PT as the same first PT selected is now defaulted every time. Rejected solution: save DCR, close DCT and edit DCR. This causes the "Select a Presentation Template" window to popup again, but the users find this very clumsy and time consuming. How do I make Content Center popup the "Select a Presentation Template" every time the user clicks preview? Is there a different direction I could be looking at to deal with this? Thanks!

- In the "Edit" mode you can to a degree control Form Settings using FormAPI IWPageGeneration object. Like that

function init() {
   IWEventRegistry.addFormHandler("onPreview", hi_dog);
}
. . .
function hi_dog() {
   // Clear out Current PT Choice with feigned "new" PT
   IWPageGeneration.setPresentationTemplate(new IWPresentationTemplate('',''));
   return true;
}

Note though that it's a hack and it won't work in "View" mode.

- There are multiple alternatives. For "template-oriented" design you may register single *utility* template that will use iwgen/iwpt_compile
and whatnot to generate *real* pages and either output a *utility* Page with links or simply open up all of them.

- "workflow-oriented" design is even easier, you can have all control you need with External/CGI Tasks