readonly fields for metadata

vivek01sinha

I am trying to have a field in metadata capture form, for which I am using inline command like this:
==============================================================
<item name="Branch" >
<description>The name of the Branch.</description>
<label>Branch</label>
<database data-type="VARCHAR(255)" />
<inline command = '/iw-home/iw-perl/bin/iwperl /opt/appl/cms/perl/getBranch.ipl'/>
</item>
==============================================================
The perl file looks like this:
==============================================================
#!/iw-home/iw-perl/bin/iwperl

my $workarea = $ENV{IW_WORKAREA};
my @array = split(/\/WORKAREA/, $workarea);
my $branch = $array[0];

print <<EOF;
<?xml version='1.0' encoding='UTF-8'?>
<substitution><text required="t" maxlength="50"><default>$branch</default></text></substitution>
EOF
==============================================================

What I want is that, this field should be readonly. If I try adding readonly subelement like this:
==============================================================
<item name="Branch" >
<description>The name of the Branch.</description>
<label>Branch</label>
<database data-type="VARCHAR(255)" />
<readonly>
<inline command = '/iw-home/iw-perl/bin/iwperl /opt/appl/cms/perl/getBranch.ipl'/>
</readonly>
</item>
==============================================================
then it does not show the default value and it comes blank. Is it that I cannot use both readonly and default subelements together or am I missing something?

Adam Stoller

What version of TeamSite are you using?

In pre-6.0 versions, I believe you are essentially using the datacapture4.0.dtd - which (from my 6.5 system) does not appear to support readonly at all.
If you're using 6.0 - then you are working with the metadatacapture6.0.dtd - which supports readonly, but only adjacent to text items - not with text items inside them. -- i.e. the following may work:

<readonly/>
<text><default>foo</default></text>

But not:

<readonly>
<text><default>foo</default></text>
</readonly>

Which is what you're trying to do.

I suggest you try the former approach with your inline and see if that resolves your problem - but if not - get rid of the inline [temporarily] and see if it works if you hard-code the configuration options -- if that doesn't work, trying to do it with an inline won't work either.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com