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

User has to enter file name when generating

TroyB

Scenario is that after filling out a form, the user attempts to generate the file using my presentation template. I already know where I want the file saved and what the file name needs to be. I attempted to use iw_ostream but it is still prompting the user for a file name.

The goal is that since I know where and what file name I want to avoid the user putting it in the wrong place with the worng name.

Find more posts tagged with

Comments

nipper

A couple choices, you will need to use FormAPI rather than using the TPL to set the file. Check out the Page Generation section (page 66) of the TS 6.7.1 FormAPI manual.

I do not have people edit the DCR, they edit the generated page which pops up a form and then generate works the way it should. For a new DCR, they preview and workflow ALWAYS regenerates the page.

Finally if you ostream and preview, did you know that TST changes the output name ? Instead of blah.html it will become zz_tst_andy_01_blah.html. That is an issue if you are using SSI or including files (say DotNet and .ascx)

TroyB

I have not used FormAPI but I see the methods that you are talking about in the manual.

Could you elaborate on your second item a little more. I understand when you say that users do not edit the DCR like we do here but you lose me after that.

Yes, I knew that. That is the way I determine if the user is previewing or generating in my tpl file to take different actions. See code snippet below. If you know of a better/easier way to do this in my tpl I would appreciate that as well.

# determine if user is doing a preview
my $outputFileName = iwpt_get_ofile_name("basename");
my $isPreviewMode = ($outputFileName =~ m/^zz_tst_/);

if (!$isPreviewMode) {
 ...
}

nipper

Could you elaborate on your second item a little more. I understand when you say that users do not edit the DCR like we do here but you lose me after that.

If someone traverses the HTML structure and not the templatedata folder, and clicks edit on a file generated by a template, it pops up a DCR. When they finish, they are asked if they want to regenerate the page and do not need to specifiy any folder structure or filenames.

Yes, I knew that. That is the way I determine if the user is previewing or generating in my tpl file to take different actions.

No my point is if you have code like:

[html]

[/html]

it will create zz_tst_andy_01_blah.html (in preview mode) instead no matter what you hard coded. So if you are creating a file to be included (SSI, ASCX, etc) during preview you will never see the changes unless you massage the URL as well.

me

TroyB

Thanks for continuing to respond to this thread nipper.

I understand what you are saying about editing the actual html file now. I will try to push for that more here. I would still be concerned that a user could simply edit the DCR rather than the html file. In which case, I am back to the scenario that a user could screw up generating the html file.

I understood what you meant about massaging of URL's in preview. I noticed that it puts the zz_tst_* when it creates the preview file. I already had to write code to massage relative path's for images that we allow the user to include in the html we generate. Luckily, we do not generate any files that have to worry about includes. We are a java team here so that is something I may have to worry about in the future with jsp's amongst other include types.

I worked on the FormAPI today generating the file for me. That worked great if I was filling out a new DCR or editing an existing one. However, it does not appear to run the script code I wrote if the user simply opens the DCR (not in edit mode) and clicks the generate button (never saw my alert and the select an output file dialog popped). Here is my code:

[HTML]
// This function is executed at the end of this script. It
// registers the event handlers.
function handleInit() {
IWEventRegistry.addFormHandler("onGenerate", handleGenerate);
}

// Event triggered before a form is generated.
function handleGenerate(dcrPath) {
alert("handleGenerate");
IWPageGeneration.setOutputFile("CompanyNews/OurCompany/StockPrice.html", true);
return true;
}

// call the initialization routine on load
IWEventRegistry.addFormHandler("onFormInit", handleInit);
[/HTML]
Any ideas?

nipper

I worked on the FormAPI today generating the file for me. That worked great if I was filling out a new DCR or editing an existing one. However, it does not appear to run the script code I wrote if the user simply opens the DCR (not in edit mode) and clicks the generate button (never saw my alert and the select an output file dialog popped). Here is my code:

Won't happen, can't happen. Don't even try you cannot fix this. FormAPI does not get loaded on DCR preview only on edit. I would turn off the generate button if this is an issue. That is why I do the main generation in WF and have users work in the docroot and not the templatedata dir.

TroyB

So...heh...is there any way that I can turn off the generate button if they are simply viewing the DCR and not editing it (e.g., clicked the DCR file name link rather than the edit link associated with it)?

I think I already know the answer because the only way I know to turn off generate is with viewoptions in templating.cfg which turns it off in both modes.

nipper

So...heh...is there any way that I can turn off the generate button if they are simply viewing the DCR and not editing it (e.g., clicked the DCR file name link rather than the edit link associated with it)?

I think I already know the answer because the only way I know to turn off generate is with viewoptions in templating.cfg which turns it off in both modes.

You guessed it. Of course you *could* turn it off in FormAPI, but then there is this minor detail that FormAPI does not run in preview mode.

RonaldV

Scenario is that after filling out a form, the user attempts to generate the file using my presentation template. I already know where I want the file saved and what the file name needs to be. I attempted to use iw_ostream but it is still prompting the user for a file name.

The goal is that since I know where and what file name I want to avoid the user putting it in the wrong place with the worng name.

In this case I would NEVER go for FormApi (because javascript sucks bigtime) and always go for workflow that would be kicked-off via the Finish-button (e.g. tt_data).

Best option in this case is write a cgi that generates the html (or whatever) because this gives you the option to show feedback to the user; f.i. a link to the generated file in preview or an error-message. Make sure that the cgi is auto-started in the wft-definition.