nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

PT Issue

Abishk

Hi everyone,
Using FormsAPI i have configured my new form entry in such a way that user has 2 buttons performing functionality as mentioned:-
Save--> the output file is generated in a location (specified by user inside DCT) in xml(Generate.xsl) format and
Preview--> the file is displayed(not saved) in an HTML(Preview.xsl) format.

The Problem
In readonly(view) mode when user clicks preview a popup is displayed asking for selection of pt, Preview.xsl or Generate.xsl (b'coz both are registered in templating.cfg). But on click of Preview I want to display HTML(Preview.xsl)

As per now after going throug the manuals and threads i have figured out that i have to
-->Put only Preview.xsl in templating.cfg
-->Run iwpt_compile for Generate.xsl
-->On click of save setPresentationTemplate as Generate.xsl.

I want your help to figure out
-->From where to run iwpt_compile. (Inline Command?) Coz it didn't work.
-->How to set PT. (IWPageGeneration.setPresentationTemplate(new IWPresentationTemplate('preview.tpl')) Didn't work either.

Please help me out here. Any leads/help would be appreciated.

Find more posts tagged with

Comments

Adam Stoller

...
I want your help to figure out
-->From where to run iwpt_compile. (Inline Command?) Coz it didn't work.
-->How to set PT. (IWPageGeneration.setPresentationTemplate(new IWPresentationTemplate('preview.tpl')) Didn't work either.

Please help me out here. Any leads/help would be appreciated.

You would not run iwpt_compile from an inline command. You might run it from a callout, you might run it from a callServer - but personally I'd rather run it from a workflow rather than from the DCT/DCR itself if you're talking about Generate (as opposed to Preview).

IWPageGeneration.setPresentatonTemplate() should be the right function to use to set the PT - It's been a long time since I've used it, but I seem to recall just passing it a string as an argument and not using another function / constructor inside of it - however, if you only register one PT in templating.cfg and use the other one explicitly within a script - you shouldn't have to worry about it.

Abishk

however, if you only register one PT in templating.cfg and use the other one explicitly within a script - you shouldn't have to worry about it.

Ok, so i followed your advice here, i have only Preview.xsl in templating.cfg.. and i tried to setPT for Generate.xsl.. But it gives me a PT compiler error.. So i guess i need to compile it first.. Is it?

Adam Stoller

Ok, so i followed your advice here, i have only Preview.xsl in templating.cfg.. and i tried to setPT for Generate.xsl.. But it gives me a PT compiler error.. So i guess i need to compile it first.. Is it?

My advice is to do the page generation (as opposed to preview) as part of a workflow process - assuming that you've designed things well enough that the generated output file name and location can be derived from the name and location of the DCR itself.

There's nothing to "compile" here (except possibly a URLExternalTask java class for your workflow if you're not using Perl) - but you do need to make sure that the Generate.xsl is properly developed and that you are processing the DCR with that XSL template by calling the proper XSLT processor.