Preview Problem

KiranM

Hi,

I am a newbie to Teamsite and i have a requirement as follows. Please suggest me any ideas or reference material which helps me overcome this problem.

I have a template which acts as a master. The functionality of this template is to create many child dcr's based on a type value selected. For example if i selected type as "ABC", i can create multiple ABC dcr's from this template. If i selected "PQR", i can create multiple PQR dcr's. Here ABC and PQR are by themselves templates.

When i select preview for the master template, it should read the type and based on the type it should pick the appropriate presentation file (.tpl) and read the dcr paths from the master template and show the preview for all the child dcr records seperated by a seperator. I couldn't find any CLT which takes the DCR path and the tpl path to show the preview.

Appreciate your help. Please let me know if the problem description needs more elaboration.

Thanks,
Kiran.

ISCBorisB

Hi, I am a newbie to Teamsite and i have a requirement as follows. Please suggest me any ideas or reference material which helps me overcome this problem. I have a template which acts as a master. The functionality of this template is to create many child dcr's based on a type value selected. For example if i selected type as "ABC", i can create multiple ABC dcr's from this template. If i selected "PQR", i can create multiple PQR dcr's. Here ABC and PQR are by themselves templates. When i select preview for the master template, it should read the type and based on the type it should pick the appropriate presentation file (.tpl) and read the dcr paths from the master template and show the preview for all the child dcr records seperated by a seperator. I couldn't find any CLT which takes the DCR path and the tpl path to show the preview. Appreciate your help. Please let me know if the problem description needs more elaboration. Thanks, Kiran.

It is not that hard to do.

For example, in the template-oriented design your *master* presentation code can parse master DCR, get child DCRs/child PTs
and run iwgen or iwpt_compile to (re)generate child DCRs output. Generated *master* output then can be a Page that shows
other Pages for preview. To achieve that you'll use frames, iFrames, or open up multiple Pages on Load Event with JS window.open
method or perhaps single Page with "show this" controls like radio buttons or drop-down, etc.

With workflow-oriented design you can use External Task(s) to do similar generation and then use CGI Task(s) to Preview
generated components.

Easy to do or not, the implied design behind all that certainly raises eyebrows. Forced DCR relations of the type you've described
are unconventional to say the least, maintaining DCR referential integrity must be a nightmare. How can you enforce "all or none"
collection submission to Staging for example is beyond me. You may perhaps benefit by hiring IWOV specialist to do a design for you