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

How to create two list boxes with different name using single TAG_info()

Dasari

Hi,

In my workflow I want to create two list boxes in the same row. How do I create two list boxes with different names by using a single TAG_info() element. I want to use the list boxes names in JavaScript to retrieve the values of the list boxes. I am using TeamSite 6.5

If I use the following code it is creating in different rows.
[html]
TAG_info(listbox1 => [html => "",
label => "Approver", is_required => 'false',],

listbox2 => [html => "",
label => "Approver",is_required => 'false',],
);
[/html]

Thanks

Find more posts tagged with

Comments

Adam Stoller

Hi,

In my workflow I want to create two list boxes in the same row. How do I create two list boxes with different names by using a single TAG_info() element. I want to use the list boxes names in JavaScript to retrieve the values of the list boxes. I am using TeamSite 6.5

If I use the following code it is creating in different rows.
[html]
TAG_info(listbox1 => [html => "",
label => "Approver", is_required => 'false',],

listbox2 => [html => "",
label => "Approver",is_required => 'false',],
);
[/html]

Thanks

I don't believe that the workflow instantiator provides for having multiple fields in the same row. The code you posted would result in two fields labeled "Approver" (*) but each would point to a different field behind the scenes (one to listbox1, the other to listbox2) and they would show up one over the other, not next to each other.

I'm hoping this is a poorly constructed simplification of what you are attempting to do - because I don't see how this example (as is) makes much sense.

(* The term is "Reviewer" not "Approver": A reviewer may choose to approve or reject something - an approver is a monkey with a rubber-stamp)

ISCBorisB

Take a look at [post=83030]this[/post] sample, see if you can leverage it. Note that it's a hack though

Dasari

Hi,

Thanks for your reply ISCBorisB. But I want to retrieve the name of the two select boxes not the value of the select box. I want to use those two names in my java script code. As you specified I tried to add but internally it is converting as [html] [/html]. I want two different name for two text boes.

ISCBorisB

I want two different name for two text boes

It is what it is. WFT's new_job Command builds WF Instantiation Screen with the single unique name for every
(vertically spaced) Entry. As far as I can tell, you can either place your text boxes vertically and have two names
or horizontally and have single Array name, that's it. You can use either one of this formats in Java Script.

Dasari

HI ISCBorisB,

Thanks for your reply. I tried with the two text boxes with the same name, it is giving properly. But when I tried with the two select boxes, the first select box the name is populating but for the second select box name is not populating. I tried with the follwing code.

[html]
TAG_info(test_select => [html => "",label => "Test", is_required => 'false',],);
[/html]

Please suggest.

Adam Stoller

HI ISCBorisB,

Thanks for your reply. I tried with the two text boxes with the same name, it is giving properly. But when I tried with the two select boxes, the first select box the name is populating but for the second select box name is not populating. I tried with the follwing code.

[html]
TAG_info(test_select => [html => "",label => "Test", is_required => 'false',],);
[/html]

Please suggest.

Try putting a name attribute in the second one:

"<select multiple size="6"></select><select name="Test2" multiple size="6"></select>"

The WF instantiator will override any name attribute in the first instance to be the label associated with it, but the second one goes through and might preserve your supplied name attribute.

Dasari

Already I tried by hard coding the name, but couldn't succeed. Workflow is removing that name automatically.

ISCBorisB

Already I tried by hard coding the name, but couldn't succeed. Workflow is removing that name automatically.

As I explained before you simply can not have multiple names horizontally..

Form Builder used by the new_job Command eats up all "horizontal" names coded in HTML. Eligible DOM Objects
then obtain a name of the "Horizontal Entry Hash" provided in the TAG_info Call. The rest remains anonymous, with no
names at all.

Above I've provided a reference to the sample that illustrates one possible option to deal with that. Basically, you
encapsulate several input elements into a "single row" Table thus creating an Array of values to use.

Another option is to use element IDs instead of names. That propagates as is. Note though that __VALUE__ function
can not be used with IDs so this technique is harder to implement correctly.

Dasari

Hi ISCBorisB,

I tried with the example you have provided in earlier reply. It is working fine with the two text boxes with the same name in same row. But when I use Select Boxes instead of text boxes it is not considering the same name for both select boxes. For the first select box name is assigning properly, but for the second select box the name is ananymous. My question is why it is working with text boxes and why it is not working with the select boxes? Are there any technical limitations for select boxes?

ISCBorisB

Hi ISCBorisB,

I tried with the example you have provided in earlier reply. It is working fine with the two text boxes with the same name in same row. But when I use Select Boxes instead of text boxes it is not considering the same name for both select boxes. For the first select box name is assigning properly, but for the second select box the name is ananymous. My question is why it is working with text boxes and why it is not working with the select boxes? Are there any technical limitations for select boxes?

Please remember that all these is a hack. If you can make it work - fine. If not, you are on your own.

"select" is not one of the input Tag types, that's *probably* the reason why you have problems with it.
If you need your own instantiation Screen, CGI starting task is often a good compromise. It's documented,
supported and you can do what you want there.