Autonaming of generated html files

Hi all ,

Using TS 6.1 Win2k .

We have a requirement for autonaming of generated HTML .When we click on 'Generate' button it asks us to choose TPL & also to give the path for 'html' file .

Now I want to autogenerate the html name . Is it possible to do this ?

Can we customized the 'Ok' button on 'Browse' window .
( when we click on 'Ok' a perl script will be called which will autogenerate the html filename )

Pls view the screen shot attached for 'Ok' button.

Regards
Rohit pathak

Find more posts tagged with

Comments

kaalraa

Rohit,

Either "Get a Training" or "RTFM". You will find enough knowledge as per your requirement within the manuals or search thru devnet.

iw_store

Hi all ,

Using TS 6.1 Win2k .

We have a requirement for autonaming of generated HTML .When we click on 'Generate' button it asks us to choose TPL & also to give the path for 'html' file .

Now I want to autogenerate the html name . Is it possible to do this ?

Can we customized the 'Ok' button on 'Browse' window .
( when we click on 'Ok' a perl script will be called which will autogenerate the html filename )

Pls view the screen shot attached for 'Ok' button.

Regards
Rohit pathak

Hi,

my $generate_cmd = "$iwhome/bin/iwgen -t \"$template\" -r \"$dcr\" \"$target\"";

$template - tpl
$dcr - dcr
$target - name of the file to store and complete path

you can make target name depeding upon dcr name.

I feel will help you.

Bill Klish

kaalraa,
Not sure why you mention Training or RTFM. Totally inappropriate here.

Rohit,
You are not able to customize the Ok button on this window using the standard UICG framework that lets you modify other aspects of Content Center. That being said, you could override that window if you could find the correct JSP within Interwoven's code, but any modification would not be supported by Interwoven and likely would be broken by future service packs and patches.

The code sample provided is the likely route you need to take. Unfortunately in 6.1 there is no way to auto generate HTML file names unless you have some sort of workflow process that creates the files.

I haven't tried it, but it *may* be possible to customize the Generate action link on the template form to run your own CGI/JSP, but haven't tried it myself.

Hope that helps.

Adam Stoller

Hi all ,

Using TS 6.1 Win2k .

We have a requirement for autonaming of generated HTML .When we click on 'Generate' button it asks us to choose TPL & also to give the path for 'html' file .

Now I want to autogenerate the html name . Is it possible to do this ?

Can we customized the 'Ok' button on 'Browse' window .
( when we click on 'Ok' a perl script will be called which will autogenerate the html filename )

Pls view the screen shot attached for 'Ok' button.

Regards
Rohit pathak

Unfortunately - the FormAPI code that could help you acheive some of what you're looking to do - was added in 6.5 - and you're using 6.1. If you upgrade to 6.5 (or later) - you can use things like IWPageGeneration.setOutputFile() and IWPageGeneration.setPresentationTemplate() - which, if set, would skip the dialog box you're looking to customize.

rohitspathak123

Hi ,

Thanks for ur response !

Our requirement is that the generated jsp should be renamed ( for eg all spaces in jsp name should be replaced by UNDERSCORE ). Eg., if jsp name entered is 'war crimes.jsp' then it should become 'war_crimes.jsp'.

We are a bit confused about where we should put our code for this renaming jsp name .

We donot want to use IWPageGeneration.setOutputFile() in DCT for doing this .

Can we trap the onClick event of 'Ok' button present on the Generate Dialog box which will call our custom code for changing the jsp file name .

For the screen shot of 'Generate Dialog' box refer to start of this post .

ISCBorisB

...Can we trap the onClick event of 'Ok' button present on the Generate Dialog box which will call our custom code for changing the jsp file name

Rohit, you already have solid input on the topic from bk99nd. There is simply no supported and documented way to do that.

That being said, you could override that window if you could find the correct JSP within Interwoven's code, but any modification would not be supported by Interwoven and likely would be broken by future service packs and patches..

The File to customize is "iw-home/httpd/webapps/content_center/formspub/generate/generate_settings.jsp".
You'll find some details in Interwoven® User Interface Customization Guide though not exactly the guidelines to modify vendor's jsp's

Adam Stoller

The other alternative, which I've used a great deal in past projects, is to drive the entire templating creation process through workflow - prompt for the name and location of the DCR in either the job instantiation form or a CGI task - do your file name munging there - then create an empty DCR in the correct place with the correct name (and EAs) programmatically and provide the user a link to click on (or redirect from the CGI script) to the Edit DCR window.

Also make sure to remove the Save As option from the Edit DCR window via the viewoptions element in the templating.cfg, and possibly remove or replace the Move and/or Rename menu items to prevent users from being able to screw things up that way.

I'm assuming you don't want to use the FormAPI mechanism because you aren't naming the DCR based on content input entered into the DCT form. If that's not the case (i.e. you are naming it based on fields in the DCT) it would be interesting to know why you wouldn't want to use the FormAPI mechanism.