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

Saving Generated Files

System

Hi,

This question is about saving the generated files. I'm using TS6.1 on UNIX
Sol 5.8.

1. After generating a DCR, an XML file is produced using a tpl. How do i automaticaly save the XML file with the same name as the DCR
.xml

2. when I run generate process i want the XML file to be saved in a predetermined location which can be either in a config file or some other location.

3. When saving the Generated file a preview window pops up again. HOw do i turn it off.

Help will be greatly appreciated.

Thanks
-Nomi

Find more posts tagged with

Comments

Adam Stoller

Hi,

This question is about saving the generated files. I'm using TS6.1 on UNIX
Sol 5.8.

1. After generating a DCR, an XML file is produced using a tpl. How do i automaticaly save the XML file with the same name as the DCR
<DCRNAME>.xml

2. when I run generate process i want the XML file to be saved in a predetermined location which can be either in a config file or some other location.

3. When saving the Generated file a preview window pops up again. HOw do i turn it off.

Help will be greatly appreciated.

Thanks
-Nomi

These are all questions regarding customization, and as such there are generally many possible answers.

I'd suggest FormAPI, but I think the functions for setting the output file were added in 6.5 so those won't be available in 6.1.

If you use a workflow to drive the creation process - and disable the OOTB functions for Preview and/or Generate - you can have an externaltask in the workflow figure out the name and location of the output file and provide that information on the command line for iwgen or iwpt_compile.ipl - in either case, no preview window will pop-up (unless you design your workflow to do that).

Migrateduser

Thanks for the reply ghoti,

I understand that # 2 was a customization question. But i was under the impression that 1 and 3 can be acheived by little modification to the generate process.

Also, I'm using the default Teamsite generate process which after generating pops up a preview window, i'm sure that can be controled by some config setting..

let me know if you have an example of the above.

THanks again
-Nomi

Adam Stoller

Thanks for the reply ghoti,

I understand that # 2 was a customization question. But i was under the impression that 1 and 3 can be acheived by little modification to the generate process.

Also, I'm using the default Teamsite generate process which after generating pops up a preview window, i'm sure that can be controled by some config setting..

let me know if you have an example of the above.

THanks again
-Nomi

You can use FormAPI to capture the fact that someone clicked on the Generate button and then use callServer() to do your own generation, passing information about the DCR to the script - and that should acheive your desire - it's not as nice as the 6.5 functions that allow you to pre-set the information so that you can use the OOTB functions (IMO).

You can replace the OOTB menu item for Generate with your own custom script that, essentially does the same thing.

As for an example of the workflow - see my GearUp 2005 presentation.

TestReport.rptdesign