Edited Forms

Of the default forms that ship with Waveset, you will probably edit one of the following five forms:

• End User Menu Form

• Anonymous User Menu Form

• Tabbed User Form

• End User Form

• Approval Form

• Change Password Forms

These edited forms control the creation and modification of users and the display of the main menu that the user sees. They are described in greater detail in the following sections.

During view and form interactions through the Administrator Interface JSPs for launching requests (before workflow launch), the view is edited directly. Consequently, the form runs in the namespace specified by the form attribute. Typical attribute namespaces include:

• accounts[*].*

• waveset.*

• accountInfo.*

• :display.session (session for admin)

  Does not apply to approval pages.

Change Password Forms

By default, there are two implementations of the Change Password forms:

• End User Change Password – This form is the default password change form. It presents a simple set of fields with which the user can change their password. The password policies for all resources that are assigned to the user are aggregated and summarized, and Waveset applies the password change to all assigned resources.

• Basic Change Password – This form is present in both the Administrator and User Interfaces. It provides information about the resources that are assigned to the user and allows the user to individually select on which resources Waveset will change the password.

Both Password Change forms support the use of the RequiredChallenge form property. When this property is set to true, the user is prompted to enter the old password after specifying the new password. See Adding a Password Confirmation Challenge for more information.

End User Menu Form

End User Menu Form controls the display of the main menu in the Waveset User interface. Typically, this form contains links for changing the user’s password, editing account attributes, and changing answers to authentication questions.

You can customize End User Menu Form to add links to launch special workflow processes that are accessible to the user (for example, a process to request access to a system).

You can set the RequiresChallenge property in the End User Interface Change Password Form to require users to reenter their current password before changing the password on their account. For an example of how to set this property, see the Basic Change Password Form in enduser.xml.

For example, to present the End-User Test Process as a link to click from the end- user pages, add the entries shown in the following code example:

Example 2–1 Adding End-User Test Process link to End User Menu Form

<Configuration id=’#ID#Configuration:EndUserTasks’ name=’End User Tasks’>
<Extension>
   <List>
      <List>
         <String>End-User Test Process</String>
         <String>An example end-user workflow</String>
      </List>
   </List>

The Waveset User Interface displays a list of self-service processes for selection. This is expected to be a list of lists. The first element of the sublist displays the process name, and the second element describes what the process does.

Waveset re-evaluates this form’s <Default> expressions whenever the page is refreshed. You can disable this forced regeneration of the form by adding the doNotRegenerateEndUserMenu property (set to true) on the End User Menu form.

Waveset re-evaluates this form’s <Default> expressions whenever the page is refreshed. You can disable this forced regeneration of the form by adding the doNotRegenerateEndUserMenu property (set to true) on the End User Menu form as follows:

<Properties>
   <Property name=’doNotRegenerateEndUserMenu’>
      <Boolean>true</Boolean>
   </Property>
</Properties>

Anonymous User Menu Form

Anonymous User Menu Form controls the display of the main menu in the Waveset User interface when an unknown user logs in.

Waveset uses the anonymous end user pages for users who are not defined in the system through the process of user self-provisioning. For example, an Waveset administrator can set up pass-through authentication for an Active Directory resource. As a result, any person who has an Active Directory account can log in to the Waveset User interface. You can customize those pages so that when a user who does not have a Waveset account logs in, an Waveset user object is created and the Active Directory resource is added. Subsequently, through a series of questions, the system can set up the user’s role, organization, and other resources.

You can customize Anonymous User Menu Form to launch workflow processes to request services before an Waveset user exists.

Tabbed User Form

Tabbed User Form is the default form used for user creation and modification in the Waveset Administrator Interface. You can customize a copy of this form by extending it with a form of your design.

Do not directly edit the Tabbed User Form. Instead, Sun recommends that you make a copy of this form, give it a unique name, and edit the renamed copy. This will prevent your customized copy from being overwritten during service pack updates and upgrades.

Customize your copy of Tabbed User Form to:

• Restrict the number of attributes that are displayed on the Edit User page. By default, this page displays every attribute that is defined on the schema map for a resource, which can result in an overwhelming list of attributes for a hiring manager to fill out.

• Set the default field types to more helpful select boxes, checkboxes, and multi value fields. By default, every attribute defined on a resource assigned to a user will appear on the Create User and Edit User pages as a text box (or as a checkbox for Boolean values).

• Include additional forms to allow common forms to be used on multiple pages.

Tabbed User Form contains these fields:

• accountId

• firstname

• lastname

• role

• organization

• password

• confirm password

• email

• resource list

• application list

• MissingFields

Do not use the MissingFields element in a production environment. It is provided for educational purposes only.

When creating or customizing a User form from the Tabbed User form, you must replace the MissingFields element with explicit references to each individual attribute that can be pushed to the assigned resource. You must provide this replacement to avoid common pitfalls that can result from using the global namespace too heavily. (For example, your workflows will not populate resources unless they use global syntax.)

(The MissingFields field is not actually a field. It is an element that indicates to the form generator that it should automatically generate text fields in the global namespace for all attributes that can be pushed to the assigned resources that are not explicitly declared in the Tabbed User Form.)

By default, every attribute defined on a resource that is assigned to a user appears on the Create User and Edit User pages as a text box (or checkbox for Boolean values).

End User Form

End User Form controls the page that the system displays when a user selects Change Other Attributes from the /user/main.jsp on the Waveset User interface. From this page, a user can change his password, authentication questions, and email address.

You can customize End User Form to grant users control over other fields, such as those that handle phone numbers, addresses, and physical office locations.

Approval Form

Approval Form controls the information that is presented to a resource, role, or organization owner when he is designated an approver of user requests. By default, this page displays a set of read-only fields that contain the name of the administrator that started the process. It also displays information about the user, including the account ID, role, organization, and email address.

This form ensures that the resource owner gets a last chance to change a user value before the user is created. By default, approving a user displays all the user attributes in read-only fields.

You can customize Approval Form to:

• Add and remove information about a user.

• Assign the approver the ability to edit this information so that he can modify the information entered on the initial user form.

• Create your own approval forms for different purposes. For example, you can create different approval forms for use when an administrator or resource owner initiates account creation or deletes a user.