(Optional) Modifying Self-Registration Views and Workflows

You can modify existing views in a self-registration workflow process or create new views as required. You can also modify the seed workflow processes that are used for self-registration.

This task is an optional step in Process of Implementing Self-Registration.

You can modify the default self-registration functionality in several ways. See the following topics for additional information:

• Replacing the License Agreement Text

• About Revising a Workflow Process

• Custom Business Services

• Redefining Required Fields

• Adding or Deleting Fields in an Existing View

• About Changing the Physical Appearance of a View or Applet

• About Creating a New View for Self-Registration

Modifying self-registration views, applets, and workflow processes include standard processes common with modifying other views, applets, and workflow processes.

The views used in the self-registration workflow processes are based on the VBC User Registration virtual business component, which collects the user data. The data is written to the User Registration business component and the Siebel database only when all stages of collecting user data are completed. Before you make any modifications, you must understand how these components handle the user data.

The User Registration and User business components are both based on the same database tables: S_PARTY, S_CONTACT, and S_USER. Therefore, writing a record through the User Registration business component is equivalent to writing a record through the User business component. In either case, a new user is created.

The user-registration process provides the following benefits:

• If the self-registration process is terminated before completion, then it is not necessary to perform the time-consuming process of undoing a new, partially written record in the database. This process requires searching several tables.

• User record duplication can be prevented before a record is written.