Which statement is true regarding hidden fields on the dsp:form?
A.
User defined hidden fields are not allowed. ATG will use hidden fields forinternal tracking.
B.
User defined hidden fields are allowedbut they can only pass static or EL values, to form
handlers for additionalprocessinglogic.
C.
User defined hidden fields are allowed and they can set component properties on form
submission. However only static and EL values are allowed as a value.
D.
User defined hidden fields are allowed and then can set component properties on form
submission.The value can either be static or a param field bean attribute.
Explanation:
Note 1: You can use hidden input fields to differentiate various forms. This mechanism is
especially useful when you generate multiple forms dynamically; in this case, you can test the
value of each form’s hidden input field to determine which form to render.
Note 2: dsp:form
Sets up a form for user input.
<dsp:form
method=”{get|post}”
[action=”jsp-page”]
[synchronized=”component-spec”]
[formid=”id”]
[requiresSessionConfirmation=”{true|false}”]
Note 3: EL Variable: Expression Language variable
You can set any Nucleus component and Dynamic Bean to a variable that can then be referenced
by the JSP Expression Language (EL). The DSP tag library provides three tags for setting
components to EL variables:
* dsp:getvalueof enables access to standard JavaBean components, page parameters and
constant values.
*dsp:tomap enables access to non-standard Dynamic Beans—for example, a RepositoryItem.
*dsp:importbean, which imports Nucleus components into a JSP, can also be used to set standard
Java Bean components to EL variables.
ATG Page Developer’s Guide, dsp:form