Confirmation Pages

MULTISELECT widget has a specific mechanism allowing for confirming user selection on a separate page. This confirmation page is supposed to re-display values selected by an user on the MULTISELECT widget offering a choice to review these values and confirm them or re-visit the previous page to refine the selection.

Confirming user selection can become a problem where there is a lot of selected values from a big MULTISELECT widget to be passed to the confirmation page. There are request length limitations in place, so in order to pass bigger amounts of data possible in this case different request mechanism (request forwarding) has to be used.

MULTISELECT widget with the selection to be confirmed is specified by HAS_CONFIRM_PAGE optional attribute on the WIDGET element. The attribute is to be set to true. It is only valid for a widget of TYPE of MULTISELECT.

Some things to keep in mind with confirmation pages:

• As request forwarding is used to carry the data in this case, the URL for the confirmation page will not be displayed with the forwarding page URL shown instead.
• Even though the mentioned attribute is set on a MULTISELECT widget, the setting applies to the whole page (as there is only one form per page). So, in case where multiple submit buttons exist on a page with MULTISELECT widget to be confirmed, a confirmation step should be assumed for all of these buttons (i.e., there is no way to have a submit with confirmation and another without confirmation on that page).
• The confirmation is to be the immediate step carried out on submitting the form with user selection; no resolve page should be used in the middle.
• It is recommended to have a read-only page for user selection confirmation, allowing user to cancel and return to the previous page if the selection is to be refined.