function_name(arguments); //eg. tpzDrillTable('','Login','0','listdetail');
where “function_name” is the Java script statement to be executed on clicking “Submit” button. You can find this statement in the “onclick” attribute of the “Submit” button
The code for this form is given below.
Please note that the code contains only some illustrative functions which would be required to explain Formfill and do not reflect the exact code of the HP Service Manager Login form.
In Linux Access Gateway, you can configure a form fill policy to submit the form in the following ways:
where form is the single form present in the HTML page and submit” is the default action associated with the Form’s submit button to submit this form to webserver automatically. This approach will work for forms with default action of the “Submit” button as POSTing the form data.
For example, these touch files help proper Formfill of complex login forms by CRM applications or TWC applications. When the touch files are present form fill does not perform HTML parsing, just as the case is with manual submitting though Autosubmit option is enabled. All the fields in the original HTML form are populated with the values configured in the form fill policy and the form data is sent to the Web browser.
However, one of the limitation with this approach is that functions configured in the Functions to keep section fail to get executed as Linux Access Gateway does not process HTML to include the function LAGSubmitForm()to perform autosubmit. To workaround the issue, the statement document.forms.submit(); must be added to the Statements to execute section. This statement ensures that the form is submitted properly with the assumption that the default action of the Submit button is POST for the form.
The following section explains the process that takes place when a client requests for a form which is configured with a regular form fill policy.
The following is the POST request sent to the browser
row=&__x=&thread=0&event=0&transaction=0&type=detail&focus=var%2Fuser.id&focu sContents=testuser1&focusId=X2&focusReadOnly=&start=&count=&more=&tablename=& window=&close=&_blankFields=&_uncheckedBoxes=&formchanged=&formname=login.pro mpt.g&_multiSelection=&_multiSelection_tableId=&clientWidth=1473&var%2Fuser.i d=testuser1&var%2Fold.password=novell081&var%2FL.language=en&0=Login&3=Cancel
However, the browser expects to receive the following POST request and does not auto submit the form:
row=&__x=&thread=0&event=0&transaction=0&type=detail&focus=var%2Fuser.id&focu sContents=testuser1&focusId=X2&focusReadOnly=null&start=&count=&more=&tablena me=&window=&close=&_blankFields=&_uncheckedBoxes=&formchanged=&formname=login .prompt.g&_multiSelection=&_multiSelection_tableId=&clientWidth=1217&var%2Fus er.id=testuser1&var%2Fold.password=novell081&var%2FL.language=en
Note the difference in POST requests sent to the browser. In the first case, the POST request has &0=Login&3=Cancel appended, which causes the login to fail.
For Formfill to work for the sample login form one must do the following modifications:
The following procedure describes the steps to configure the form fill policy with Java or VBScript functions.
Please note that all the Input Field Value are illustrative and have to be substituted with the actual values from the original form.
function dvdRegisterSelect() function enableAll() function verify(f, bSubmitToSelf) function printThisView() function tpzDrillTable(a,b,c,d)()
When this touch file is used, the Linux Access Gateway does not generate a new page if autosubmit is enabled, but fills the page received from the Web server and hides the text/password/unspecified type fields. Form-Fill issues for CRM applications and teaming and conferencing applications are resolved with this touch file.
However, when this touch file is used, the Debug Submit and JS Functions to Keep options of the Form Fill policy do not work.
/etc/init.d/novell-vmc stop /etc/init.d/novell-vmc start
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.