Security Adapter Support for Synchronization Authentication

See Providing Security Adapter Authentication for Synchronizing the Local Database.

Security adapter authentication is supported for Mobile Web Client users to synchronize their local databases with the server database.

Enhanced Conflict Resolution Options

See MRG:Inter Table Conflict Res.

This enhancement lets Siebel administrators choose between available preference values to determine how each Siebel implementation will handle insert conflicts on intersection tables.

New Time Filtering Feature

See Preventing Extraction and Synchronization of Older Data.

This new feature allows administrators to prevent selected kinds of older data from being sent to all Mobile Web Clients during database extraction or synchronization. By reducing the amount of data to be sent to Mobile Web Clients, the use of time filtering can reduce the time required for database extraction and synchronization, and may also enhance Mobile Web Client response time.

Resetting the Password for the Local DBA Account at GenNewDb

See Changing the Local Database Administrator Password.

Whenever you run the Generate New Database component to create a database template, you can use a runtime parameter, NewDbaPwd, to specify the DBA account password for the local databases that will use the new database template. A local DBA password that is specified as a runtime parameter is used only for the current run of Generate New Database. If no password is specified at runtime, the local DBA password is set to the value of the parameter as defined in an administrative view. If no administrator has set the value of the parameter in an administrative view, a default value based on the Enterprise name is used.

Standard Encryption of the Local Database

See Encrypting the Local Database.

This new feature provides the option to encrypt the local database template to provide a layer of security against unauthorized access to the local database.

Enhanced TrickleSync Administration

See Setting Up TrickleSync for Users as an Administrator.

This enhancement allows a Siebel administrator to set up the TrickleSync feature (formerly called Autosynchronization) for one or more users.

Separate Credentials for Synchronization and Local Database Access

See Providing Credentials to Synchronize the Local Database and Changing the Local Database Password.

The credentials for access to the local database and for synchronization can be managed independently. The Mobile Web Client user can change the local database password. New options are provided for providing the synchronization credentials without having to enter them manually.

Strong Encryption of Local Database Password

See Configuring the Mobile Web Client for Local Database Password Encryption and Configuring the Remote Server for Local Database Password Encryption.

This new feature allows RSA SHA-1 encryption to be applied to the local database password before it is passed to the local database for authentication.

Routing Model Enhancements

See Routing Model Enhancements in Siebel Release 7.7.

Routing model definitions can now exclude information (prevent it from being routed) at the dock object level. The Enterprise dock object is one of the dock objects that routing models can exclude.

New Handheld User Routing Model

See Handheld User Routing Model.

This new routing model is designed for mobile users who synchronize Siebel Handheld applications with Siebel Mobile Web Clients, and who use Siebel Remote to synchronize Siebel Mobile Web Clients with the Enterprise database.

New Life Science User Routing Model

See Life Science User Routing Model.

This new routing model is similar to the Mobile Client - Standard model, but it contains extra rules required by the Siebel Life Sciences Mobile Web application.

New Selective Retrieval Routing Model

See Selective Retrieval Routing Model.

This new routing model supports the use of the new Selective Retrieval feature, which allows users to specify particular records to be included in Mobile Web Client synchronizations.

New Selective Retrieval Feature

Using the Selective Retrieval Routing Model.

This new feature allows users to specify particular records to be included in Mobile Web Client synchronizations. This functionality provides an alternative to more traditional Routing Models for specifying the data to be synchronized.

Selective Retrieval is suitable for Mobile Web Client users who also regularly use another type of Siebel client to connect directly to Enterprise or Regional databases. This distinction is necessary because of the following limitations in the Selective Retrieval feature:

• To specify the records to be synchronized, Selective Retrieval users need a direct connection to an Enterprise or Regional database.
• Certain advanced features, such as forecasting and quotes, are not available to Selective Retrieval users when they are using the Mobile Web Client.

For appropriate users, the benefits of using Selective Retrieval can include reduced synchronization time and reduced local database size, due to a reduction in the amount of data that is transferred during synchronization.

Enhanced Database Extraction to CD-ROM

See Performing a Database Extract to a CD Directory.

This enhancement uses a new configuration file parameter, DbinitLocalSource, to specify the directory that will be used to store files to download for the initialization of the client's local database. In previous releases, the FileSystem parameter was used for this purpose.

You may need to change the value of this parameter if you want a Mobile Web Client to initialize a local database from a CD-ROM or a directory other than the default location on the Siebel Remote Server.

Enhanced Monitoring

See About Automatic Notification of Critical Conditions.

This new feature provides automatic email notification when certain critical conditions are reached in the Siebel system.

Enhanced Monitoring

See Checking Siebel Remote Transaction Backlogs.

This new feature allows administrators to check the number of Siebel Remote transactions waiting for handling by the Transaction Router, on a per user, per server, or Enterprise basis.