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; } } }

xsl presentation template in workflow

sdragice

I have created a new presentation template using xsl rather than the perl based .tpl ... it all seems to work fine through the UI, I can generate and regenerate a DCR using the XSL presentation teplate and it all works as expected

However when I push the corresponding DCR through a workflow I get a different result, no errors but the output that's generated is just a dump of the XSL, no transformation is taking place. Any suggestions as to what I may have missed?

Find more posts tagged with

Comments

Rick Poulin

Are there relevant messages in any logs? Are you sure that the workflow task was properly configured and is executing *something* ?

WC_Library_WhatDoesItDo_Master.zip

sdragice

thanks for replying. I can't see any errors in the logs but may be lookingin the wrong place so will check again

the workflow does run to completion .. the only difference is when I use a perl based presentation template (.pt) I get the desired output generated but using the xsl all I get is a dump of the xsl so I can't figure out what's causing this

Rick Poulin

How are you calling the transformation process? Java (which class) or the iwgen.exe?

sdragice

yes it is calling the iwgen command through a .ipl script. The parameters to the command arethe presentation template, DCR and output file.

Hope I'm not being too vague, I'm fairly new to Teamsite

Rick Poulin

The error messages from that command often get printed to STDOUT/STDERR so you might be missing out on the diagnostic information. I'd doublecheck content_center.log and server.log, but I think the real answer would be to create a quick perl script as a wrapper to iwgen.exe so you can log the output to a file.

sdragice

I couldn't see any errors in these logs

I ran the iwgen in a commandprompt with the same parameters, I didn't see any output messages at all but it did complete but gave the same result, a dump of the xsl as the output. Would runing it in a perl script be likely to provide any additional info?

CustomDesignFile.rptDesign

Preview from the BIRT Designer.pdf

Preview from the Server Environment.pdf

Adam Stoller

It sounds like either your XSLT has an issue or that something isn't configured correctly such that iwgen is attempting to use the TPL processor instead of the XSL processor. Are you sure the templating.cfg is set up correctly?

Rick Poulin

I was thinking that since it works from the cmd prompt but not in workflow, there's something about the context that must be different (environment variables or access rights), or perhaps the parameters have characters that aren't being encoded properly.

sdragice

Just to clarify, this fails through both the workflow and when executing iwgen from the command line ..i,e,: the output is a dump of the XSL.

It does however work from the UI ("Actions --> Generate Page" or "Actions --> Regenerate Page"). The output result is exactly what I expect, the DCR is transformed correctly to the desired output

I have the following in templating .cfg for the presentation template... ptcompiler="com.interwoven.ui.formspub.utils.XSLTPTCompiler"

So does iwgen actually use templating.cfg to determine which compiler to use?

Reason I ask is because if I remove the above entry from templating.cfg and execute "Actions --> Generate Page" from the UI then it fails, i.e.: what's output is a dump of the XSL. So that makes me think that iwgen is defaulting to the perl compiler, so how do I get it to use the XSL compiler?

Adam Stoller

sdragice wrote:
[...]
So does iwgen actually use templating.cfg to determine which compiler to use?

Reason I ask is because if I remove the above entry from templating.cfg and execute "Actions --> Generate Page" from the UI then it fails, i.e.: what's output is a dump of the XSL. So that makes me think that iwgen is defaulting to the perl compiler, so how do I get it to use the XSL compiler?

That's what I was wondering about too - there's nothing in the iwgen documentation to indicate that it knows anything about the XSL compiler (but nothing to indicate it doesn't either).

You should probably open a case with Support regarding this - if possible, put together a very simple [repeatable] test case - perhaps using one of the OOTB XSL DCTs and XSL templates [to remove as much as possible "customizations"]. E.g.: Using xslt/general-content.

I just tried this on my 7.5 Windows implementation - and iwgen appears to work just fine for generating the HTML from the XSLT.

If you try this and it works correctly with the OOTB stuff - then you need to start debugging your configurations (templating.cfg and XSLT) against the OOTB stuff to see if you can identify what it is in your custom code that might be preventing it from working correctly.
If you try this and it fails to work correctly with the OOTB stuff - then you have a good basis for opening a case with Support.

fontsConfig.xml

sdragice

Thanks for your assistance. I'll follow your auggestions and contact support if need be, sounds like it may be a bug in the product. I think I may need to revert back to the Perl PT in the mean time and try to muddle through as best I can.

Nice to know it works on 7.5 as we will be upgrading to that version in the next few months

Adam Stoller

Until you make the *same* test in *your* environment - don't be so sure it doesn't work in your environment. If it does - then the problem is with your specific usage and not the product.

sue27

Hi,

Did you get any direction from support on this? I am seeing the same issue on TS 8.1, I can generate via "generate" option in the DCR but when I try to use iwgen from command line , the html file is created at correct location but it dumps the complete xsl in the html file.

I am using this command:

iwgen.exe -t <Y: path to .xsl> -r <Y: path to DCR> <Y: path to output html>

nipper

Sue

I would start a new thread, include all your details, OS, TS level (8.1), etc.

If you can, include maybe a small sample, or if the OOTB templates behave the same way, then include a way to reproduce it. Some of us may be able to verify. I have access to 8.2, not 8.1, but can let you know.