SubForm contextual parameters

As a child element of a main form, a SubForm is passed contextual parameters that help identify the context from which it is started.

These contextual parameters are included in the HTTP Request that brings up the SubForm:

Table 1. SubForm parameters
HTTP (contextual) Parameter Name	Person Create	Person Modify	Account Create	Account Modify
`target_dn`	empty	DN of Person	DN of account owner	DN of the account
`container_dn`	DN of the organization tree container where the Person is created.	DN of the organization tree container where the person is located.	DN of account owner	DN of the account owner
`search_base`	empty	empty	DN of service	DN of the service instance on which an account is provisioned

To assign the target_dn HTTP parameter value to a String declared inside a servlet:

String targetDN = request.getParameter("target_dn");

Account Modify example

For example, for Account Modify, the value of contextual parameters are:

target_dn: Is the DN of the entity whose attributes are displayed on the main form. If the SubForm is placed on a RACF® account form, this parameter value is the DistinguishedName of the RACF account.
container_dn: Is the entity container or parent. For example, if the SubForm is placed on a Person form, this parameter value is the DistinguishedName of the parent or container of the person. The container can be an organization, organizational unit, admin domain, or location.
search_base: For example, if the SubForm is placed on a RACF account form, this parameter value is the DistinguishedName for the RACF service instance on which the account is provisioned.