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

Regarding Inline Callout

curiousmaverick

Hi,

I need to simply populate a select list with already existing values(no dynamic value).I am using an Inline Callout for that.But I am not very sure about how the
.ipl file should be written.I mean do I simply need to put the xml portion of the code that i need to substitute?

Please guide me.

Regards,
Mav

Find more posts tagged with

Comments

kaalraa

Whatever file you call using inline callout, the output of the file should be in the XML format within <substitution> element.

Hi,

I need to simply populate a select list with already existing values(no dynamic value).I am using an Inline Callout for that.But I am not very sure about how the
.ipl file should be written.I mean do I simply need to put the xml portion of the code that i need to substitute?

Please guide me.

Regards,
Mav

Adam Stoller

Hi,

I need to simply populate a select list with already existing values(no dynamic value).I am using an Inline Callout for that.But I am not very sure about how the
.ipl file should be written.I mean do I simply need to put the xml portion of the code that i need to substitute?

Please guide me.

Regards,
Mav

the FormsPublisher Developer's Guide - but if that's you're answer - you clearly need to read it again - carefully.

curiousmaverick

No Ghoti, I'm not expecting some spoon feeding here.That never has been my intention.I did go through templating guide(page 50)..But if things are not clear( my limitations only) I guess I can seek help here, right Smiley Happy

Adam Stoller

No Ghoti, I'm not expecting some spoon feeding here.That never has been my intention.I did go through templating guide(page 50)..But if things are not clear( my limitations only) I guess I can seek help here, right

Well - if it's page 50 - I'm guessing your working with TS6.7.0 or TS6.7.1 but not TS6.7.1SP1 - am I right (I did ask you to supply that information too - which you should have done in your initial posting)

Can you explain what it is that you don't understand about the contents of that page in the manual?

Is it just that you don't understand how to write a Perl script?
Or, perhaps (now that I look at the document which I believe you're looking at) it's because the document says:[indent]The inline callout program should return a well-formed XML document...[/indent] which is somewhat inaccurate it should probably be more like[indent]The inline script should send to STDOUT a well-formed XML document ...[/indent]Is that the part you were confused about? If not, please explain exactly what part of that documentation you don't understand.

curiousmaverick

it's about how to write the script.Well,i did mention it's my limitation only...

kaalraa

it's about how to write the script.Well,i did mention it's my limitation only...

In case, you have tried something to write as per your limitations, please attach. It would be better for you, to learn from your mistakes (If you have done some in your script).

curiousmaverick

Thanks kalra...let me put in some more effort..before I raise the SOS...!

Adam Stoller

it's about how to write the script.Well,i did mention it's my limitation only...

If you're doing this in Perl and are not that familiar with Perl - then I suggest you start by getting (purchase, borrow, whatever) one of the following two books to begin with:

curiousmaverick

Please have a look at the attached IPL.I've used a "here document" form of printing, and it's giving me desired output when I run it in a Perl Interpreter.

But here it is giving an error like, "Can't find string terminator "EOF" anywhere before EOF at C:/iw-home/iw-perl/userScripts/1_columnLanguage.ipl line 2. "

Where am I going wrong ?

regards,
Mav

curiousmaverick

though using qq and then print giving me the desired result...

lalita

Please have a look at the attached IPL.I've used a "here document" form of printing, and it's giving me desired output when I run it in a Perl Interpreter.

But here it is giving an error like, "Can't find string terminator "EOF" anywhere before EOF at C:/iw-home/iw-perl/userScripts/1_columnLanguage.ipl line 2. "

Where am I going wrong ?

regards,
Mav

Use "substitution" tag inside "xml" tag.
like this:
[html]

[/html]

curiousmaverick

that doesn't seem to resolve the problem....

lalita

please attach 'cfg' file here.

kaalraa

that doesn't seem to resolve the problem....

Did you put the xml declaration tag along with values like:

[HTML] [/HTML]

Also, i hope the <select> tag would already be present in your datacapture.cfg file.

Adam Stoller

that doesn't seem to resolve the problem....

I thought you already resolved the problem using qq() - as in:

#!c:/w-home/iw-perl/bin/iwperl.exe
use strict;
use warnings;
print qq(<?xml version="1.0" standalone="yes" encoding="UTF-8"?>
  <substitution>
    <option label="Chinese" value="zh"/>
  </substitution>
);

Is the above code not working?
This is an inline script - yes?
Can you show the code in the DCT where you invoke it?

curiousmaverick

Kalra, i did put in the values Smiley Happy

Fish, yeah Ive managed to make it work using qq and then a print statement.Problem is showing if i try to use EOF format(which is in the attached file).But same file gives proper output, while run using a perl interpreter.

Regards,
Mav

kaalraa

Kalra, i did put in the values
Regards,
Mav

Hey Mav,

Nothing offensive about that Smiley Happy

Thanks,

curiousmaverick

I know, just to clear im not doing that bad ... Smiley Happy

Files.zip

Adam Stoller

Kalra, i did put in the values

Fish, yeah Ive managed to make it work using qq and then a print statement.Problem is showing if i try to use EOF format(which is in the attached file).But same file gives proper output, while run using a perl interpreter.

Regards,
Mav

I tend to dislike "hereis" style statements because they're so fragile (an extra white-space before or after the marker, at the beginning or end of the statement can screw things up and be a pain to debug.

I'd suggest sticking with qq(...) now and in the future, and not worrying too much about it ...

curiousmaverick

I'd agree to that.The KB article about this only made me curious about this technique...