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

Preview Dialogue box

bturns

TS 6.5
Solaris 9

Hi There,

I have a data type that has multiple tpls. One tpl is need for previewing and one is needed for generation. All the file generation happens behind the scenes (via workflow). When the user previews I'd like to have the preview tpl automatically chosen. However, since there is also a tpl for generation a dialogue box always displays asking the user which tpl they would like to preview with (the preview tpl or the generate tpl) Is there a way of not allowing the dialogue box to display?

I can't remove the generation tpl from the available_templates.cfg because it needs to be there so it can generate in workflow.

Any thoughts?

Thanks,

Brian

Find more posts tagged with

Comments

moonkhanna

Brian,

write a function for onPreview and set the tpl there. Refer to the formApi guide on how to set the tpl for preview.

nipper

I solve this issue a little differently.

I use the same TPL for both (then it never asks for the TPL).

iwpt_compile can point to any TPL, so you can have another not referenced in templating.cfg, that can be used in WF.

Finally, if you want to do something different in preview as opposed to generate, a bit of perl like this will work:



for (my $i=0; $i<@ARGV; $i++)
{
 if ($ARGV[$i] =~ /iw_pt-preview/) 
 {
  $mode = "preview";
 }
}

ISCBorisB

I can't remove the generation tpl from the available_templates.cfg because it needs to be there so it can generate in workflow

First, it's templating.cfg, not available_templates.cfg (probably just a slip/typo).
Second, if you use iwgen or iwpt_compile to do your WF generation you may specify any pt you wish, registered or otherwise

Adam Stoller

First, it's templating.cfg and not available_templates.cfg (probably just a slip/typo).
Second, if you use iwgen or iwpt_compile to do your WF generation, you may specify any pt you wish, registered or otherwise

Either I'm mis-remembering, something has changed, or you're only partially right. I seem to recall that iwgen looks up information in the templating.cfg file to find registered PTs and extensions - whereas iwpt_compile.ipl does not.

ISCBorisB

I solve this issue a little differently.

I use the same TPL for both (then it never asks for the TPL).

iwpt_compile can point to any TPL, so you can have another not referenced in templating.cfg, that can be used in WF.

Finally, if you want to do something different in preview as opposed to generate, a bit of perl like this will work:
for (my $i=0; $i<@ARGV; $i++)
{
 if ($ARGV[$i] =~ /iw_pt-preview/) 
 {
  $mode = "preview";
 }
}

if (iwpt_get_flag_param('-oprefix')) {
# It's a Preview
}
else {
# It's a Generate
}

ISCBorisB

Either I'm mis-remembering, something has changed, or you're only partially right. I seem to recall that iwgen looks up information in the templating.cfg file to find registered PTs and extensions - whereas iwpt_compile.ipl does not.

I stand corrected - iwgen does require pt registration. Thanks

bturns

you're right I did mean to say templating.cfg

I've gotta run a test here. Last time I tried to generate a file with iwpt_compile without having an entry in templating.cfg I got an error. Let me check though. It could be one of the options I'm using.

Thanks,

Brian

moonkhanna

you're right I did mean to say templating.cfg

I've gotta run a test here. Last time I tried to generate a file with iwpt_compile without having an entry in templating.cfg I got an error. Let me check though. It could be one of the options I'm using.

Thanks,

Brian

Brian - it seems to me as if you hate FORM API. I feel that setting the PT On preview would be the easiest you can do.. Comments?

ISCBorisB

Comments?

PT "preview-recognition" approach seems both safer and more logical.
For example, FormAPI is ignored completely if you open up your DCR in View mode

moonkhanna

PT "preview-recognition" approach seems both safer and more logical.
For example, FormAPI is ignored completely if you open up your DCR in View mode

Hi ISCBorisB,

Thanks for the explanation. Yes, that would be reasonable approach in that case..

Thanks!

Best Regards,

Munish Khanna

bturns

If it does work to remove the tpls from the templating.cfg, then I think that would be the easiest approach. I would only have to delete a couple lines from an xml file as opposed to creating some javascript (FORM API) and testing. If removing from the templating.cfg does not work then I will consider the javascript (FORM API) option. Thanks!

Brian