Form-Action for callout calling itself

I am using an inline callout ipl to provide the users with a more comfortable data entry form. The script uses some of the form cgi parameters to read some value from the dcr and later write it back.
Now this script basically builds an HTML form, that at some must call itself (the script) to apply some changes (Does anybody know, how to build this form-action so all the environment variables are preserved?

Greatful for any hint :-)
Regards

Find more posts tagged with

Comments

reddyl

Inline callout are run on the server when the DCT form initially loads. You should use callserver so that you can post the form data to the script.

ninickname

Thanks, but maybe I didnt make myself clear...
I have no problem with the DCT/DCR calling the script (inline callout works fine); but the script calling *itself again* via a form action! I am loosing all teamsite environment values doing so; looks like there must a special form action neccessary?

Adam Stoller

Thanks, but maybe I didnt make myself clear...
I have no problem with the DCT/DCR calling the script (inline callout works fine); but the script calling *itself again* via a form action! I am loosing all teamsite environment values doing so; looks like there must a special form action neccessary?

Maybe it's me - but I still don't think you're being clear.

An inline callout, as stated, is called during form initialization and is, I believe, more of a command-line script rather than a CGI script. So it's not working with FORM variables, but ENV variables and command-line arguments.

As a command-line script - it doesn't really make sense for it to call itself again; instead it makes more sense for it to iterate through itself again - call the same subroutine as part of a loop or recursive subroutine.

At this point, in order to make yourself clearer, the only thing I can think of is that you'd need to post the code (or a reasonable snippet of the code that demonstrates the issue you are trying to resolve).

mstradling

This might just be mixing terms, so could you clarify if this is an Inline or a Callout?

Inlines are processed at template compile time, do 'stuff' and write DCT XML in to the calling datacapture.cfg. This is passed to the form processing code that chuck up a web form in the users browser.

Callouts are static in the datacapture.cfg, and the form processing code turns them in to a HTML form button where the callout script is the target ofr the HTML form.

These can interact with the user through a pop-up window and right back to the data capture from the user is viewing in their web browser.

If your trying to get an Inline to call it's self - why? Just write the code to do what you need.

If your not using an Inline, or the code needs to interact with the user (e.g. a search that needs search text from the user to operate), then you need to be using a Callout (, or depending on the version of TeamSite/datacapture.dtd your using).

ninickname

First of all, thank you guys for your help Smiley Happy

Ok, this is from the DCT:

[...]
< textarea cols="80" rows="20" required="t">
< callout url="/iw-bin/nicer_form.ipl" label="Nicer form" window-features="width=1024, height=700, resizable=yes,toolbar=no,scrollbars=yes"/>
< /textarea>
[...]

And the base of the IPL is actually one of the Documentation examples since it explains pretty nice how to read the data from the DCR and how to write it back:

[...START...]

my $cgi = TeamSite::CGI_lite->new();
$cgi->parse_data();

my $form_name = $cgi->{'form'}{'iw_form_name'};
# ^^ NECCESSEARY FOR FEEDBACK TO DCRs
my $field_name = $cgi->{'form'}{'iw_callback_var'};
my $user_name = $cgi->{'form'}{'user_name'};
my $field_value = $cgi->{'form'}{$field_name};

[...]

var calloutForm = eval($form_name);
if (!calloutForm)
{
return false;
}

var calloutElementFound = false;
for ( i = 0 ; i < calloutForm.elements.length ; i++ )
{
if (calloutForm.elements.name == '$field_name')
{
calloutForm.elements.value = selectedValue;
calloutElementFound = true;
break;
}
}

[...END...]

The IPL itself displays a nicer DHTML form (need some more usability than being provided through DC Templating) inside < form action="?someOfmyOwnVariables">. Some usability features I cannot cover through DHTML/client side scripting, so I need to reload the form once in a while; and the problem is that the reloaded page only contains three large textareas - they seem to come from TeamSite itself since there is no html code from me doing so. So my guess is, something must be wrong with simply reloading the form with < form action="?someOfmyOwnVariables">

reddyl

What happens when you invoke the CGI script "ipl" with the parameters alone.

jbonifaci

The IPL itself displays a nicer DHTML form (need some more usability than being provided through DC Templating) inside < form action="?someOfmyOwnVariables">. Some usability features I cannot cover through DHTML/client side scripting, so I need to reload the form once in a while; and the problem is that the reloaded page only contains three large textareas - they seem to come from TeamSite itself since there is no html code from me doing so. So my guess is, something must be wrong with simply reloading the form with < form action="?someOfmyOwnVariables">

Hmmm, callouts just give you a bunch of post data, they don't control your form in any way. Your script and code is outputting anything you see in your callout browser window. Why don't you post your script to give people a better idea of what you're trying to do.

Btw, the ivow example callout code is very out dated. Since the addition of 5.5.2, all interaction with the DCT form the callout window should be done via FormAPI. I'm sure if you search a little you can find a few examples on here.

~Jeff