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

passing EA as parameter in inline command

ChristianFracky

I would like to pass the value of an EA, say where ABC="red", to an ipl, but am having trouble with the syntax.

What has to change in the syntax below to pass "red" as the parameter?

{inline command="E:\iw-home/iw-perl/bin/iwperl.exe E:\iw-home/custom/server_side_inline_callout.ipl ABC" /}

(replace { with < and } with > in the above statement).

p.s.: I am doing this from the Tagging UI and therefore do not have access to FormAPI.

Find more posts tagged with

Comments

Migrateduser

I would like to pass the value of an EA, say where ABC="red", to an ipl, but am having trouble with the syntax.

What has to change in the syntax below to pass "red" as the parameter?

{inline command="E:\iw-home/iw-perl/bin/iwperl.exe E:\iw-home/custom/server_side_inline_callout.ipl ABC" /}

(replace { with < and } with > in the above statement).

p.s.: I am doing this from the Tagging UI and therefore do not have access to FormAPI.




# Inline script code snipet
use Getopt::Long;

my %eas;
GetOptions("eas=s%" => \%eas);

ChristianFracky




# Inline script code snipet
use Getopt::Long;

my %eas;
GetOptions("eas=s%" => \%eas);

Thanks for the posting. The assumption with the code provided is that you would have to know that the EA is ABC=red in advance. I would like to pass "ABC" in as the parameter, and have it resolve to "red" so that the receiving code can act on "red". Thoughts?

Adam Stoller

Where is the EA supposed to be coming from?

I ask because an inline command is run prior to instantiating the DCT form.

In FormsPublisher it has access to information about the DCT, user, role, and workarea - I don't think it's any different for Metadata Capture - however, if you create an inline script that dumps out all the environment information to a debugging file and use that in your metadata capture form - you should be able to see what is / is not available for use in your inline script coding.

So - where the EA is supposed to be coming from is critical to your question.

Assuming you get the above issue resolved - then passing the path / name of the EA to your inline script and having your inline script run iwextattr (or equivalent) to retrieve the value of that EA should be pretty simple.

ChristianFracky

Hey fish,

The behaviour would be as follows:

1. User in DCT, clicks "Tag" button
2. EA (call it "colour") is populated prior to Tagging UI opening
3. Tagging UI opens. For a different EA in the Tagging UI different than that in 2., a callout is made to an .ipl file and passes in as a parameter the value for "colour" autopopulated in 2.

Is this possible? My (wrong) syntax in the Tagging UI is as follows:

inline command="E:\iw-home/iw-perl/bin/iwperl.exe E:\iw-home/custom/server_side_inline_callout.ipl colour" /

Adam Stoller

Hey fish,

The behaviour would be as follows:

1. User in DCT, clicks "Tag" button
2. EA (call it "colour") is populated prior to Tagging UI opening
3. Tagging UI opens. For a different EA in the Tagging UI different than that in 2., a callout is made to an .ipl file and passes in as a parameter the value for "colour" autopopulated in 2.

Is this possible? My (wrong) syntax in the Tagging UI is as follows:

inline command="E:\iw-home/iw-perl/bin/iwperl.exe E:\iw-home/custom/server_side_inline_callout.ipl colour" /

Let me see if I got this straight:

You are tagging a file ("file_foo.xyz")
Just prior to initiating the tagging UI on "file_foo.xyz" you explicitly set "TeamSite/Metadata/colour=red" (or whatever colour you like) on "file_foo.xyz"
You have an inline script specified in your metadata DCT which, as a parameter, you pass the tail-end of the EA name ("colour")
In the inline script you wish to retrieve the value of the EA ("TeamSite/Metadata/colour") from the file being tagged ("file_foo.xyz") in order to determine some aspect of the MDC DCT that you are about to have rendered

Is that about right?

I don't know the answer off-hand, and don't have time to try to play with this right now - but assuming the above is what you are doing (or trying to do) - I would add debugging print statements to your inline script that will write out all the envirionment and ARGV information to a temporary file so you can see what is available within the inline script for you to make use of. e.g.

#!.../iw-perl
use strict;
use warnings;
my $dbgfile = "c:/temp/inline_dbg.txt";
if (open(OUT, '>', $dbgfile)){
    print OUT "DEBUGGING DATA&colon; " . localtime() . "\n";
    print OUT "[ARGV]: $_\n" foreach(@ARGV);
    print OUT "[ENV]: $_ => '$ENV{$_}'\n" foreach(sort(keys(%ENV)));
    close(OUT);
}

You should experiement to see the output both from when you edit an existing DCR and from when you edit a brand new, never been saved form. The output should go a long way to providing information about what you can and cannot do from your inline script.

ChristianFracky

Let me see if I got this straight:
You are tagging a file ("file_foo.xyz")
Just prior to initiating the tagging UI on "file_foo.xyz" you explicitly set "TeamSite/Metadata/colour=red" (or whatever colour you like) on "file_foo.xyz"
You have an inline script specified in your metadata DCT which, as a parameter, you pass the tail-end of the EA name ("colour")
In the inline script you wish to retrieve the value of the EA ("TeamSite/Metadata/colour") from the file being tagged ("file_foo.xyz") in order to determine some aspect of the MDC DCT that you are about to have rendered
Is that about right?

I don't know the answer off-hand, and don't have time to try to play with this right now - but assuming the above is what you are doing (or trying to do) - I would add debugging print statements to your inline script that will write out all the envirionment and ARGV information to a temporary file so you can see what is available within the inline script for you to make use of. e.g.
#!.../iw-perl
use strict;
use warnings;
my $dbgfile = "c:/temp/inline_dbg.txt";
if (open(OUT, '>', $dbgfile)){
    print OUT "DEBUGGING DATA&colon; " . localtime() . "\n";
    print OUT "[ARGV]: $_\n" foreach(@ARGV);
    print OUT "[ENV]: $_ => '$ENV{$_}'\n" foreach(sort(keys(%ENV)));
    close(OUT);
}
You should experiement to see the output both from when you edit an existing DCR and from when you edit a brand new, never been saved form. The output should go a long way to providing information about what you can and cannot do from your inline script.

You've summed up the requirement nicely.

Ran the syntax provided, and not a whole lot is visible, *sigh*.

Ok, another angle: What I am after here is, in the Tagging UI, populating a select box via an inline command. The values in the select box are dependent on a different EA in the Tagging UI, say EA "colour".

Any suggestions in this task? My approach appears to be limited as for attaching derived parameters in the inline command.

Adam Stoller

You've summed up the requirement nicely.

Ran the syntax provided, and not a whole lot is visible, *sigh*.

Ok, another angle: What I am after here is, in the Tagging UI, populating a select box via an inline command. The values in the select box are dependent on a different EA in the Tagging UI, say EA "colour".

Any suggestions in this task? My approach appears to be limited as for attaching derived parameters in the inline command.

I'm not sure about inline callouts - but there was a patch provided for one of my customers for TS 6.5 SP1 that allowed CGI callouts to access information about which file was being tagged and to access fields by name in the DCT form (there was a major change in regard to this between the old tagging UI and the 6.x tagging UI - the patch helped bridge the gap).

Again though, this was for a CGI callout - where form variables were available for accessing. I don't believe inline's get form data posted to them (do they?) - so a lot depends on the information you *did* get back from printing out the ENV and ARGV data (and you can try creating a TeamSite::CGI_lite object and print out all the $cgi->{form} and $cgi->{cookie} data if any)

Lastly - consider trying to re-architect your requirements as a CGI Callout rather than an inline and perhaps that will work for you (though you may need to get the 6.5SP1 patch from Support if the current version you're running (6.5SP1 or later) doesn't provide the cross-field interface you need)

ChristianFracky

Thx, fish. For anyone reading this posting who may be interested, I was informed from IW direct that there is no way to pass a dynamic parameter in an inline command from the Tagging UI. Instead, we are opting to use multiple rulesets until such a time that FormAPI-like functionality is available to the Tagging UI (anyone have any idea when that is?).

Migrateduser

I keep hearing that it's coming in the next version or the next SP. I heard that before 6.5, before 6.5 SP1, before 6.5SP2, and now I'm hearing it about 6.7. I'll believe it when I finally see it.

jbonifaci

Dusty O'Brien from Interwoven will be presenting in 2 weeks at GearUp on Next Gen MetaData Capture, so you might get your answers then.

~Jeff

Migrateduser

I'll bring my torch and pitchfork in case I don't like the answers Smiley Happy