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

Textarea

System

Hi,

Is there any way to get select and multiple select functionality for Textarea ??

The reason is i want full data into one textarea after that some of those data i want to move to other textarea.

Thanx in advance

Find more posts tagged with

Comments

MattP

Alright, that second sentence just make sense not Smiley Wink

I think you are trying to populate a text box based on a selection from a separate item, correct? This is pretty straightforward formAPI stuff. Is that what you are looking to do?

Matt

Matthew Petitjean
BOC Group
Murray Hill, NJ 07974 USA

Migrateduser

U r right.
I want to populate the Textarea with external program (Data from Database).

Is it possible using FormAPI.???

I am trying to using inline command but Textarea don't take inline command

Thanx for your reply

MattP

Ah, OK, not what I thought. You are correct, it doesn't seem that text areas allow inlines (seems like a snide comment should follow). If you are trying to get data from tables, it may be easier to put the logic in the presentation template. Of course if the user needs to edit this content, that doesn't help. FormAPI is not the right path. I thought you wanted to populate based on a dropdown or radio selection.

Matt

Matthew Petitjean
BOC Group
Murray Hill, NJ 07974 USA

Migrateduser

You could use FormAPI (deep breath). Have something kick off when the form is loaded that uses callServer to run a JSP or CGI to generate JavaScript to call FormAPI functions to populate the field with values from the database.

Snide comment definitely seems appropriate.

Or you could have the inline generate the FormAPI.

Edited by john on 04/17/03 12:28 PM (server time).

MattP

What do you think the limitation is? Could you change the DTD and get away with it?

How about a readonly item? I haven't used it before, but it allows callouts.

matt

Matthew Petitjean
BOC Group
Murray Hill, NJ 07974 USA

Migrateduser

I really can't imagine why they would have left out this important feature. I don't think it validates agains the DTD so I am not sure changing it would help. But just having the inline generate FormAPI doesn't seem like too much of a hack.

Adam Stoller

I'm unclear on what you are trying to do here - and though I haven't tested it out - looking at the datacapture5.0.dtd I see the following:

The <textarea> element appears to support an option <default> sub-element, which you should be able to use an <inline> command to fill - e.g.:

<textarea ...>
<inline command="..."/>
</textarea>

Assuming the inline script returns XML in the format of <default>...</default> you should be good to go.
Also supported, according to the DTD, is the <cgi-callout> (and <java-callout> if you're using Java UI) - which would seem to me to imply that the same way you would fill in a <text> field with a callout you should be able to fill in a <textarea> field with a callout

So - it looks like this is supported. Are you saying you've tried this and it doesn't work?

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

I have neither tried it not read the documentation but I do seem to remember some issue from the past regarding default text for textareas. I just responded to the comments from krishna1288 ("I am trying to using inline command but Textarea don't take inline command") and MattP ("You are correct, it doesn't seem that text areas allow inlines").

james1

> I have neither tried it not read the documentation but I do seem to
> remember some issue from the past regarding default text for
> textareas.

Perhaps you are referring to the fact that the default value for textareas provides only a default value at the time of creation of a new DCR. Editing an existing DCR discards the DCT-provided default value and instead defaults to the currently-stored value, which is then editable in the form. (It seems that a lot of people want to the "default" value to be a constant uneditable value.)

-- James

--
James H Koh
Interwoven Engineering

Adam Stoller

FYI:

I just tested using <default>...</default> hard-coded in the DCT and via an inline script - in TeamSite / TeamSite Templating 5.5.2 SP2b on Windows 2000 - and it seems to work just fine.

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

I think people want the default value to be applied to existing DCRs the first time they are opened after an item with the default value is added to an existing DCT.

OK, since I have a few minutes I will try to get an inline to populate a default value in a textarea and see if the original post was just completely off base.

Adam Stoller

Default values (for *any* field in a DCT) *only* work the first time the DCR is created - after that, the fields are considered to have values, so the default value will not be used.

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

I understand how it works, I was just mentioning how I think other people want it to work. For this reason I usually use FormAPI instead of default (check if it's blank and populate it if desired).

Migrateduser

Weird, I just tested and can't get it working. This is from the DCT:

<item name="Another">
<textarea wrap="virtual">
<default>
<inline command="C:/iw-home/iw-perl/bin/iwperl.exe C:/iw-temp/test.pl" />
</default>
</textarea>
</item>

This is the script:

print "<?xml version='1.0' encoding='UTF-8'?>";
print "<substitution>\n";
print "Written to STDOUT\n";
print STDOUT "Written to STDERR\n";
print "</substitution>\n";
exit( 0 );

If I run the command on the command line it looks like valid output is generated. If I create a new DCR with this template the textarea is blank. If I run iwdctacleval on the template it shows the default tags with nothing between them. I know it is running the command because the first time I had .ipl instead of .pl and both UI and command line threw exceptions. I tried slashes both ways but didn't try escaping the slashes (time to go back to the hotel).

Adam Stoller

This is the script:

print "<?xml version='1.0' encoding='UTF-8'?>";
print "<substitution>\n";
print "Written to STDOUT\n";
print STDOUT "Written to STDERR\n";
print "</substitution>\n";
exit( 0 );

You're missing a newline at the end of the first line - which I believe makes the result invalid XML - try this:

print qq(<?xml version="1.0" encoding="UTF-8"?>
         <substitution>
         This is my default text
         </substitution>\n);

or, as I did - put the 'default' tags in the inline script rather than in the DCT:

print qq(<?xml version="1.0" encoding="UTF-8"?>
         <substitution>
         <default>This is my default text</default>
         </substitution>\n);

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

Actually I am not sure a linefeed after the XML declaration is required - both XMLSpy and iwxmlval don't seem to think it's a problem:

C:\iw-temp>type test.xml
<?xml version="1.0" encoding="UTF-8"?><ROOT></ROOT>

C:\iw-temp>iwxmlval test.xml

C:\iw-temp>

I reduced the DCT to this:

Y:\default\main\Pioneer\Intranet\PHIWeb\WORKAREA\shared\templatedata\HR\Policy>type datacapture.cfg
<?xml version="1.0" standalone="no"?>
<!DOCTYPE datacapture SYSTEM "datacapture5.0.dtd">

<data-capture-requirements type="content" name="test">
<ruleset name="test">
<item name="Another">
<textarea wrap="virtual">
<default>
<inline command="C:/iw-home/iw-perl/bin/iwperl.exe C:/iw-temp/test.pl" />
</default>
</textarea>
</item>
</ruleset>
</data-capture-requirements>

Note this DCT references datacapture 5.0 - is that correct (I thought 5.0 didn't allow the script tag)? Not that it uses it since the DTD reference is invalid anyway.

Here is the script and output of a manual run:

C:\>type c:\iw-temp\test.pl

print "<?xml version='1.0' encoding='UTF-8'?>\n\n";
print "<substitution>\n";
print "Written to STDOUT\n";
print STDOUT "Written to STDERR\n";
print "</substitution>\n";
exit( 0 );
C:\>iwperl c:\iw-temp\test.pl
<?xml version='1.0' encoding='UTF-8'?>

<substitution>
Written to STDOUT
Written to STDERR
</substitution>

But the data does not appear in the template UI, or in the output of iwdctacleval (there is a linefeed and it does something weird to the indentation of the closing default element though):

Y:\default\main\Pioneer\Intranet\PHIWeb\WORKAREA\shared\templatedata\HR\Policy>iwdctacleval datacapture.cfg
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE data-capture-requirements SYSTEM "datacapture5.0.dtd">
<data-capture-requirements dtd-system-identifier="" name="test" type="content">
<ruleset name="test">
<label>test</label>
<item name="Another">
<label>Another</label>
<textarea cols="0" external-editor="" external-editor-config="" required="f" rows="0" rtf="f" wrap="virtual">
<default>

</default>
</textarea>
</item>
</ruleset>
</data-capture-requirements>

I tried with no output to STDERR and the results were the same. When I put the default tags in the inline script instead of the DCT it worked. My interpretation of the DTD is neither default nor textarea can contain inline, but I was always told that you could put the inline anywhere and the DTD was ignored because it was too hard to develop a DTD that indicated the fact that inline could be used anywhere:

<!ELEMENT textarea (allowed?,callout?,java-callout?,cgi-callout?,default?) >

<!ELEMENT default (#PCDATA)>

I wonder if this is specific to some build or environment issue, or if textarea suports inline but default does not. While there is a workaround I think the code is more clear if the default tag is in the DCT.

A conclusive response from Interwoven would be appreciated.