File Upload builder inputs - Portlet Factory v6.1.2

Portlet Factory, Version 6.1.2

File Upload builder inputs

This topic describes the inputs for the File Upload builder.

Table 1. File Upload builder inputs
Input name Description
Name Name for this builder call. The WebSphere Portlet Factory Designer displays this name in the builder call list.
Page Location Page or pages on which this builder call acts.
Subfolder (Optional) Specify a subfolder in which (of the configured IBM® WebSphere Portlet Factory upload folder) to store the uploaded file.
Note: Setting this optional subfolder in this builder sets it for the entire form being submitted. If you have multiple File Upload controls in a single HTML page or form, they must all use the same subfolder, because the subfolder to save to is saved once for the entire page or form.
To save different types of files to different subfolders, use multiple HTML pages or forms.
Process Upload Errors When you enable this input, all exceptions are caught and stored in the request in an attribute (bowstreet.fileUploadException). Processing continues in the webApp.
Note: This allows you to look for an exception in the request in the action that is about to run.

Parent topic: File Upload builder

Library | Support |

Input name	Description
Name	Name for this builder call. The WebSphere Portlet Factory Designer displays this name in the builder call list.
Page Location	Page or pages on which this builder call acts.
Subfolder	(Optional) Specify a subfolder in which (of the configured IBM® WebSphere Portlet Factory upload folder) to store the uploaded file. Note: Setting this optional subfolder in this builder sets it for the entire form being submitted. If you have multiple File Upload controls in a single HTML page or form, they must all use the same subfolder, because the subfolder to save to is saved once for the entire page or form. To save different types of files to different subfolders, use multiple HTML pages or forms.
Process Upload Errors	When you enable this input, all exceptions are caught and stored in the request in an attribute (bowstreet.fileUploadException). Processing continues in the webApp. Note: This allows you to look for an exception in the request in the action that is about to run.