Generate Output File

Hi all,

I have been working on "Auto Generate Content" for quite sometime, the idea is to automate the content generate process without allowing the end user (Author) to specify the location of the output file. As we knew that the end user might not have technical knowledge so they might sometimes generate the content in the wrong place.

so I have a tought, I capture the Output File in the Data Capture Template (DCT) as shown in the first image, the red circle. that field will be populated using formAPI script. so the end user (Author) don't have to worry where to save the output file.

Picture 1 data captured template screen

When the end user (Author) clicked on the generate button on the Data Capture Template (DCT) screen, the generate output file screen popup as the one shown in the Picture 2.

Instead of prompting the end user (Author) to browse the output file, I plan to populate the Output File value that captured by the Data Capture Template (DCT) screen into the the field that circled in Red colour in Picture 2.

Picture 2 generate output file screen

OR

Can I skip the Generate Output File Screen, and generate the output file using the value captured in the Data Capture Template (DCT)?

Thanks in advance, really hope can get it work. Smiley Happy

regards,
waikong

Find more posts tagged with

Comments

Adam Stoller

Hi all,

I have been working on "Auto Generate Content" for quite sometime, the idea is to automate the content generate process without allowing the end user (Author) to specify the location of the output file. As we knew that the end user might not have technical knowledge so they might sometimes generate the content in the wrong place.

so I have a tought, I capture the Output File in the Data Capture Template (DCT) as shown in the first image, the red circle. that field will be populated using formAPI script. so the end user (Author) don't have to worry where to save the output file.

Picture 1 data captured template screen

When the end user (Author) clicked on the generate button on the Data Capture Template (DCT) screen, the generate output file screen popup as the one shown in the Picture 2.

Instead of prompting the end user (Author) to browse the output file, I plan to populate the Output File value that captured by the Data Capture Template (DCT) screen into the the field that circled in Red colour in Picture 2.

Picture 2 generate output file screen

OR

Can I skip the Generate Output File Screen, and generate the output file using the value captured in the Data Capture Template (DCT)?

Thanks in advance, really hope can get it work.

regards,
waikong

For questions like these - it really helps to know what version of TeamSite you are using.

If you're using 6.5 or above (which the rendered image would seem to support) - there are FormAPI calls you can make to set the output file name and location. You can then use FormAPI's callServer to perform the actual page generation.

Alternatively, if you wrap the entire templating process within a workflow - and can derive the name and location of the generated file from either information within or about the DCR you could perform the generation process via an externaltask or cgitask script.

It's a matter of design and implementation - both of which are more in your control than ours.

Note: If you're going to handle this automatically / programatically - you should probably remove the Generate option from the Edit DCR window (read the FormsPublisher Developer's Guide for details about viewoptions)

waikong

For questions like these - it really helps to know what version of TeamSite you are using.

If you're using 6.5 or above (which the rendered image would seem to support) - there are FormAPI calls you can make to set the output file name and location. You can then use FormAPI's callServer to perform the actual page generation.

Alternatively, if you wrap the entire templating process within a workflow - and can derive the name and location of the generated file from either information within or about the DCR you could perform the generation process via an externaltask or cgitask script.

It's a matter of design and implementation - both of which are more in your control than ours.

Note: If you're going to handle this automatically / programatically - you should probably remove the Generate option from the Edit DCR window (read the FormsPublisher Developer's Guide for details about viewoptions)

Hi ghoti,

I am using TeamSite 6.5

Thanks for your reply, which really helps alot, now I am getting closer to the solution. I found a section in the formAPI document called [highlight]Page Generation - IWPageGeneration[/highlight] which allow me to set the output file properties, and now when user click the Generate button, they no longer required to manually browse the output file, instead the output file will be generated based on the configuration I setted. Smiley Happy

but in order to move forward, I have more question, hope you doesn't mind.

is there a formAPI function to replace the and "Generate" button that located on top of the Data Capture Template form? (as shown on picture 1, the red circle), my next objective is to call out the generate function when the user click "Finish" button. So the output file generate process is transparent to the end user, and thats put an end to my "Auto Content Generate" issue log Smiley Wink

Picture 1, Data Capture Template

* I have do a search through the formAPI document, and I couldn't find the function I am looking for, or maybe it is there, but I can't identify it. perhaps you can enlighten me.

ISCBorisB

is there a formAPI function to replace the and "Generate" button that located on top of the
Data Capture Template form?
my next objective is to call out the generate function when the user click "Finish" button. So the output file generate process is transparent to the end user, and thats put an end to my "Auto Content Generate" issue log

1. You can hide/show DCT buttons but not with FormAPI. This is specified for the data
capture template through the actionlist attribute of the <viewoptions> tag in the templating.cfg file.
For example, something like the following will hide "Generate":
<viewoptions actionlist="save; saveas; settings; preview; "/>
See TeamSite® FormsPublisher Developer’s Guide

2. Your second requirement is not that simple. You have few options here.

a) Develop "Generation" workflow. Use External task with iwpt_compile.ipl or iwgen to generate
what you need (iwgen is easier to use, iwpt_compile gives you more *advanced* options).
Configure this WF to run on "Finish". This is specified for workflow template through
the value attribute of the <command> tag in the available_templates.cfg file. (value="tt_data").
Disadvantage of this approach is an additional unsolicited user dialog (start WF, use another WF or ignore).
I have yet to find a way to suppress this *user friendly* lunacy.

b) Modify "Finish" button functionality and use FormAPI callServer to generate what you need
with iwpt_compile.ipl or iwgen. "Modify Finish" portion of that phrase is a hack,
it's not supported. There are couple threads on DevNet showing how to do that.
This approach gives you total control of what happens when and how, but it is much harder
to do and only partially documented/supported.
See TeamSite® Command-Line Tools and TeamSite® Workflow Developer’s Guide

You may also want to consider the following approach: Create dedicated Author Workflow
where your content contributor does not control generation at all, "Generate", "Finish",
whatever. He simply transitions to the next task, the rest is done by WF.
Like "UserTask Edit DCR"->"UserTask Edit MD"->"ExternalTask Generate"->"CGITask Show", etc

LexileRangeChart.rptdesign

jkm

[html]
a) Develop "Generation" workflow. Use External task with iwpt_compile.ipl or iwgen to generate
what you need (iwgen is easier to use, iwpt_compile gives you more *advanced* options).
Configure this WF to run on "Finish". This is specified for workflow template through
the value attribute of the tag in the available_templates.cfg file. (value="tt_data").
Disadvantage of this approach is an additional unsolicited user dialog (start WF, use another WF or ignore).
I have yet to find a way to suppress this *user friendly* lunacy.
[/html]

Another approach to achieve this is on click of Finish button, give a alert box and ask user if he wants to generate the page. If user selects yes then invoke the workflow and generate the page. This will avoid two steps in the user journey

1. Submit Now/Later screen
2. Selection of the workflow

waikong

Thanks for your suggestion, which really inspire my tought.

after reading through your post, i am thinking, is the iwgen is possible to be call from the formAPI?

report1.rptdesign

Adam Stoller

Thanks for your suggestion, which really inspire my tought.

after reading through your post, i am thinking, is the iwgen is possible to be call from the formAPI?

FormAPI runs on the client side.
iwgen runs on the server side.

The bridge between the two is FormAPI's callServer() - which is used to call a program on the server side - usually a perl script to which you have passed specific parameters so that you can construct whatever command you wish to run.

Please read the documentation regarding this in the FormAPI Developer's Guide and/or the plethora of threads in these forums discussing and/or detailing its usage for things like this.