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

How to capture generated page name

manpreet1

Hi,

I am using TeamSite 6.7.1 Service Pack 1.
I have two webservers-
1) staging Web server
2) live Web server

In teamsite, I have customised the 'Preview' and 'Generate' buttons. On click of 'Preview', I am deploying the page to staging web server and on clicking 'Generate' I am deploying the page to Live web server.

I have called two ipl files in JS using the "IWDatacapture.callServer". One on click of 'preview' and second on click of 'generate'. These ipl files are actually deploying the content to web servers. These files expect different parameters. One of the parameters is "generated page name".

Now, all this works fine, when I am editing an already existing page in teamsite.
But on creating a new template using 'New Form Entry', and clicking 'preview', functionality breaks as till that point of time i don't have 'generated file name'.

In order to overcome this, I have got the file generated on 'onSaveNameSpecified' event using window.open. Now the file gets generated successfully but when I try to capture the generated page name using "IWPageGeneration.getOutputFile ()" on clicking preview. it comes blank. :-( and because of this my functionality breaks.

Can anyone please help me in capturing the generated page name on click of preview (file has been already generated on "onSaveNameSpecified" event).

Thanks in advance.

Regards,
Manpreet

Find more posts tagged with

Comments

Adam Stoller

Is the output file name supposed to be based on the DCR name? If so, you need to make sure that the DCR has been saved before you can perform your preview operation.

As for Generate - I generally don't allow users to see the Generate option, as I prefer to handle that entire process within a workflow (otherwise there's a complete circumvention of review policies for templated content)

So - you should make sure the DCR already has a name, if not - you can either attempt to perform the save operation - or you can just put up an alert informing the user that they need to perform the save first (personally, I try to make sure that my DCRs can be auto-named based on some field within the DCT and avoid the prompting for names from the users).

Once you have a DCR name - you're preview functionality can perform the exact same operation that generate would (in terms of generating a file with the real expected output file name instead of a zz_tst_... file name) and then perform whatever deployment you wish.

If you need more assistance than the above, you either need to post your code (DCT + FormAPI + IPL) - or hire someone with the proper skill set to assist you.

manpreet1

Thanks much for your response.

I am making sure that user clicks the 'save' button to save the DCR before clicking 'preview'. So I have the DCR name at the time of clicking preview.

But on click of preview, how i can generate the expected output file name instead of zz_tst... file. At what point of time the user will be prompted to set the generated page name then?

I have attached the FormAPI code for further reference.

Adam Stoller

Thanks much for your response.

I am making sure that user clicks the 'save' button to save the DCR before clicking 'preview'. So I have the DCR name at the time of clicking preview.

But on click of preview, how i can generate the expected output file name instead of zz_tst... file. At what point of time the user will be prompted to set the generated page name then?

I have attached the FormAPI code for further reference.

The point I was trying to make is that when I design forms, I try to make sure there's a field (or two) within the form that can be used to programmatically name the DCR, and that the name of the output file should be derived from the name of the DCR. E.g.:

mumbleFratz.xml (DCR) => mumbleFratz.html (output)

Thus, if you have the name of the DCR, you have the name of the output file to generate for both Preview and Generate - and you utilize iwpt_compile.ipl (or whatever the CLT is for doing XSLT PTs?) and provide it the proper arguments, including the output file name - which gives you (the programmer) full control over the process.

So - I (personally) would probably not use:

var OutputFilename=IWPageGeneration.getOutputFile ();

Unless I had explicitly set the output file name using the DCR name, removing the

templatedata/.*/data/

part, and then changing (or affixing) the extension to be what I want it to be (e.g.: .html)

Hope that helps.