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 requirement to generate html and associated tab delimited file.

SethHickel

We have a user requirement to generate html and an associated tab delimited file with only one generate request from user.

The tab delimited file that will contain a unique id (which will need to be generated from within TeamSite) along with the html file name, and other metadata. The unique ID will be used by IBM Commerce Server to find and display the html file.

Our dilemma is: How to generate the second file of a different type, generate the ID and publish them together. I anticipate that the requirement may grow to include an association between the two files in TeamSite that will allow for the deployment of the tab delimited file automatically each time the html file is deployed.

I’m not sure where to start my research for a solution. It was suggested that I look at iw_ostream but since I would be generating files of different types it was suggested that iw_ostream command may not work and that I may need to fulfill this requirement with a combo of form api and a callServer command to a CGI (perl).

Thoughts? Research suggestions?

Find more posts tagged with

Comments

ISCBorisB

We have a user requirement to generate html and an associated tab delimited file with only one generate request from user.

The tab delimited file that will contain a unique id (which will need to be generated from within TeamSite) along with the html file name, and other metadata. The unique ID will be used by IBM Commerce Server to find and display the html file.

Our dilemma is: How to generate the second file of a different type, generate the ID and publish them together. I anticipate that the requirement may grow to include an association between the two files in TeamSite that will allow for the deployment of the tab delimited file automatically each time the html file is deployed.

I’m not sure where to start my research for a solution. It was suggested that I look at iw_ostream but since I would be generating files of different types it was suggested that iw_ostream command may not work and that I may need to fulfill this requirement with a combo of form api and a callServer command to a CGI (perl).

Thoughts? Research suggestions?

There are many ways to accomplish it.

You can certainly use iw_ostream to generate otput with different format/extensions, that is not the issue.
You can also use iw_perl Tag(s) to do what you want and output components wherever needed.

You may also want to maintain simple individual PTs. In this case, you create three templates, generate0,
generate1 and generate_both. You will register only generate_both in your templating.cfg to avoid extra
user dialogs, etc. Now, generate_0/1 are independent from each other and can be modified individually.

Registered generate_both will then simply call iwpt_compile twice, applying generate0 and generate1 to the same DCR.
After generation you'd have to set Correct MetaData on the output Files, iwpt_compile does not do that.
(Resist the temptation to use iwgen instead. Granted, you'll have MD assigned for you but iwgen requires registered
templates. That causes extra user Dialogs on Preview/Generate, etc)

SethHickel

Thank you.

I'll experiment with your suggestions.

Seth

TommyWillB

I'm trying to do something similar, where I'd like to automatically generate xyz.html.meta when the user generates xyz.html.

Is there any way to know the name of the file the user is generating?

TommyWillB

Figured it out: http://devnet.interwoven.com/forums_vb/showthread.php?t=25394&forumid=11&highlight=iw_ostream


 my $output_file=iwpt_get_ofile_name();