The default values for MultiProfileAddFormHandler properties are generally configured correctly for most situations. You can reset the properties of a MultiProfileAddFormHandler component in two ways:

The effect of property settings depends on the scope of the MultiProfileAddFormHandler instance. For more information, see Multi-Profile Form Handler Scope.

The MultiProfileAddFormHandler also shares a number of properties with the ProfileFormHandler, which serve the same purpose. These include trimProperties and confirmPassword.


This property uses the handleClear method to clear the value Dictionary when a form creating users is submitted. This property is set to true by default.


An integer that represents the number of users to be processed by the form; serves as a dimension of the users list. The default value is 0.

This property must be set before the form is rendered on the page. For request-scoped form handler components, a hidden input tag must restore the state of the count property before the </dsp:form> close tag. For example:

<dsp:setvalue bean="MultiProfileAddFormHandler.count" value="2"/>
   <dsp:form action="MultiProfileAdd.jsp" method="post">
      <dsp:input type="hidden" bean="MultiProfileAddFormHandler.count"/>

Contains the UserListItem object of the user currently being updated.

You can use this property in the postCreateUser() method when you need to extend the functionality of the MultiProfileAddFormHandler. See Multiple ProfileFormHandlers in the Working with User Profiles chapter of the ATG Personalization Programming Guide for more information.


A String that contains the default password, set when the generatePassword property is set to true.


Identical to the ProfileFormHandler property extractDefaultValuesFromProfile.


A Boolean, indicates whether to generate the password automatically when the form is submitted with the create operation. The default value is false. If set to true, the default password is set to the value of the defaultPassword property.


The maximum value allowed for this form’s count property. The default value is 0—that is, no maximum value. If set to a value greater than 0, maxCount always overrides the count property.

Note: maxCount must be set in the page before the count property.


The minimum value that the count property can be set to in this form. The default value for this property is 1. If count is less than minCount, and minCount is greater than 0, then count is set to minCount. You must set the minCount property in the page before you set the value of the count property. The minCount value must be greater than 0.


This property contains a link to the ProfileTools component. The MultiProfileAddFormHandler uses this component to perform operations that are common to all ProfileFormHandlers. See Using ProfileFormHandlers in the Working with Forms and Form Handlers chapter of the ATG Platform Programming Guide.


This String is the name of the class that the form uses to create the list of users to add. The default class is UserListItem. The UserListItem class is a subclass of RepositoryFormHandler. It provides a means to handle form exceptions for individual users. The user array instantiates this class so you can extend this class and pass added functionality to the objects in the user list.


A List of objects that contains the form update values for properties that apply to each user profile. For example, each user profile might have the properties firstName, homeAddress, and so on. For per-user property values, each object in the list contains a value Dictionary. This value Dictionary is used in the same way as the value Dictionary in the single ProfileFormHandler. It stores the values before the form is submitted.

Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved. Legal Notices