Bookshelf v7.5: Modifying Self-Registration Views and Workflows

Modifying Self-Registration Views and Workflows

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

You can modify the default self-registration functionality in several ways. You can do one or more of the following tasks:

Replace the license agreement text

Revise a workflow process, including creating custom business services

Redefine the fields the user is required to complete

Add or delete fields in a view

Change the physical appearance of a view or applet, such as moving fields or changing colors

Create a new view

Modify user deduplication

Modifying self-registration views, applets, and workflow processes include standard processes common with modifying other views, applets, and workflow processes. However, you should understand the way that data is collected by the User Registration business component and written to the database before you do any modifications.

The views used in the self-registration workflow processes are based on the User Registration business component. 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 business component allows collecting data into virtual fields. For most applications that use the self-registration workflow processes, no data is written to the database until all stages of collecting user data are completed. This process provides the following benefits:

If the self-registration process is terminated before completion, there is no need 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.

Siebel Partner Portal differs in how it commits data during the self-registration process. It collects data into virtual fields during the initial part of the process. No data is committed to the database during this part of the sequence. During the latter part of the sequence, in which partner-specific data is collected, the registration process makes use of multi-value groups (MVGs) to populate some fields, such as Industries.

User data is written to the database in this phase, prior to completion of the entire process, because MVGs must be associated with a user's actual record in the database. At this point the record cannot be undone.