Hi,

I have a HTML page created in HTML Layout painter which has a multi-select listbox and passes the values chosen to a fex when a "Run Report" button is clicked. However when the number of choices chosen are more than 70 or 80 a server has crashed error appears. Is there a limit to the size of the parameters (number of choices made in a listbox) or number of parameters that can be passed to a fex?

This message has been edited. Last edited by: Kerry,

There is a limit to the number of characters that can be passed in a URL request when using the GET method (which is the default for the HTML Layout painter.) The limit is not related to WF. So the the number of values you can select depends on the length of the values passed. If you search the forum, there are numerous posts on the subject. You really want to select 70 or 80 values from a list box? Isn't there a better way to handle this?

if the GET function was being used i would see the parameters in the URL right? i don't see any that happening and that's why i posted this query as i know that GET has a limitation... but does POST also have a limitation? because the URL of the new window (result page) has on the base url and no parameters. 70-80 choices selection is not the proper way but i got a client who thinks otherwise...

also if "get" IS the default function in HTML layout painter, how can i change it to POST?

If your result has http://{server}/ibi_apps/WFServlet only, then it should be a POST.

Have you looked at the source of the page being submitted ?, The forms Method may be aded later by javascript, but you can check.

Method POST effectively does not have ant limitations, as the parameters are send in the header of the request.

I doo agree with Darin, if you have to select 70 or 80 options from a select list, then perhaps there is a better way. HTML pages that are large can also be slow in the browser as well.


One technique I've used in the past to check what is happening in a webpage is to add in some javascript to alert or prompt the contents of items on the page, for example the form being submitted. You can also check if the submit button is a type of submit or does it call a javascript routine.

Have a look at the agent on the WF server, it may have an error code.

Have a look at the server log, there may be some info there.

You could also trace the server to see what is happening there.