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

Adding a Button on the WF template

Jayc

I need to add a button on the workflow template that can display information about to the user, files, etc associated with the workflow. I used the TAG_info to add html to generate this button and the button actually calls a CGI script that will display information in a pop-up window.

the html for the button look like this:
<a href="javascript&colon;my_button_win()" class="iw-base-actionlist-link">MY BUTTON</a>
<script language="JavaScript">
function show_details_win() {
newwin = window.open("/iw-bin/my_button.cgi");
}
</script>

However, I have problem passing all the workflow related variables to my_button.cgi, because the variables are too many to pass using GET method. I tried to pass via POST, by including another form in the button html, then in the javascript function, submit this form to my_button.cgi. It did not work. Can anyone help?

Thanks in advance!

Find more posts tagged with

Comments

Migrateduser

Interesting approach, but how did your POST-workaround not work? That is, were you able to capture ANY form variables? From the HTML you posted, it doesn't look as though you're performing a POST at all, rather a GET. Or, were you intentionally pasting the GET version?

Dave

Jayc

Here is the form Post version:
TAG_info(
mybutton=>
[ label => '',
html => $button_html,
is_required => 'false',
],
...

my $button_html =<<EOS;
<form method='POST' name='form1' action='/iw-bin/my_button.cgi'>
<INPUT TYPE='hidden' NAME='...
...

<a href="javascript&colon;my_button_win()" class="iw-base-actionlist-link">MY BUTTON</a>
<script language="JavaScript">
function my_button_win() {
document.forms['form1'].submit();
}
</script>
</form>

EOS

When I click on "MY BUTTON", I got error message:
document.forms.form1 is null or not a object

Migrateduser

What about not worrying about the JavaScript and instead doing the following:


<form method="post" name="form1" action="/iw-bin/my_button.cgi" target="_new">
...

It would seem to accomplish what you're trying to do and would make it that much simpler at the same time.

Please let me know what happens.

Dave

Jayc

I changed to this:
<form method='POST' name='form1' action='/iw-bin/mybutton.cgi' target='_new'>
...
<input class='fontmain' type=submit value='MY BUTTON'>

When I click the button, it submits to iwwft_instantiator.cgi instead. It is essentially the same error as in the javascript, it does not recognize that there is a form1, it submits to the default workflow instantiator form. Mybe it has to do with the fact that my html is included in the TAG_info, so my form1 is nested in the default form....

Migrateduser

I wondered about that previously -- it sounds as though the basic layout of your WF template display is the following:


<form method="post" ... (the WF template form, generated by IW) ...>
     ...
     <form method="post" name="form1" action="/iw-bin/my_button.cgi" ...>
     </form>
     ...
</form>

I have seen some strange behavior in the past by using nested forms, as this is. Am I correct in assuming that you are implementing nested forms?

I wonder if, instead of referring to the form by name, you were to refer to it by index (i.e. "document.forms[1]"), it would "understand" that.

Could you implement the following in to the HTML?


<a href="javascript&colon;alert(document.forms[1].name);" class="iw-base-actionlist-link">MY BUTTON</a>

As you can see, I'm taking the debugging route already! I'm just wondering as to why it's not recognizing your inner form.

Thanks,

Dave

WORKFLOWdude

Dave!!!! You are the Man!!!!

I had a very similar problem I had been working on for a day and a half. For some reason TeamSite seems to eliminate any mention of a:
name='bob'
....by the time the HTML is generated.

I basically had something that looked like this in my .wft file:
TAG_info(
selectform =>
[ html => "<form name='selectform'>",

Everytime I began the workflow and viewed the source html, the code just had : <form> .....Where did the name='selectform' go?

It doesn't matter now. I was able to refer to the form as: document.forms[1] instead of document.selectform

Thanks man!!!!

Migrateduser

Oh, okay! Well, good!

Honestly, I try to stay away from syntax like forms[1], especially with black boxes like TeamSite only because if they put out a new version or service pack that changes the structure of these pages, our forms[1] could syntactically become forms[2] or forms. I'm coding like this, also, but I guess use with caution.

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K