Security Guide for Siebel Business Applications > Troubleshooting Security Issues >

Access Control Issues

This section describes problems related to access control.

Employee User Has Trouble Logging into a Siebel Customer Application

It is not recommended to use an Employee login account to access a customer application (such as Siebel Sales). Instead, give the user a separate login account for the application.

Cannot Delete Division Records

You cannot delete division records because business components throughout your Siebel Business Applications refer to organizational records. Deleting a division might cause invalid references on transactional records. However, you can rename a division or promote a division to an organization.

Cannot Modify Seed Responsibility

Seed responsibilities cannot be modified or deleted. Instead, make a copy of the seed responsibility you want to modify and make changes to the copy.

Excessive Synchronization Time for Some Mobile Users

Make sure the Local Access control field in the Responsibility View list is set properly. This setting determines which views mobile users can work in offline. For faster synchronization time, reduce the number of views that have local access. For more information, see Local Access for Views and Responsibilities.

Unexpected Refresh Causes Loss of Data

When you enter records on particular views (for example, Service Request List View), records can appear lost if the underlying business component is re-queried before a user is assigned to the access list. This event can occur if the associated detail applet (for example, Service Request Entry applet) expands or collapses to show or hide additional fields. By default, collapsing or expanding a detail applet results in the record being committed and the business component being requeried.

You can override the default behavior described above by setting the user property RestrictedFieldActivation = FALSE. Setting RestrictedFieldActivation = FALSE means that the business component is not re-queried if the detail applet expands or collapses. You can set RestrictedFieldActivation = FALSE in one of the two following locations:

• In the [SWE] section of the client configuration file (or Server component configuration file).
• In the applet. To set the value of RestrictedFieldActivation in the applet, you add it to the user properties of the applet in Siebel Tools.

CAUTION:  It is not recommended to set RestrictedFieldActivation = FALSE in the [SWE] section of a configuration file as it can degrade the scalability of your Siebel deployment. You are advised to set the value of RestrictedFieldActivation in the applet using Siebel Tools.

In addition to specifying the applet, you can also specify the view mode where you disable an automatic re-query of the business component when a detail applet collapses or expands. To specify the view mode, add the following entry to the user properties of the applet in Siebel Tools:

NoRestrictedFieldActivationMode<number> valueOfVisibilityMode

For example, the following entries override the default behavior in the Personal and Manager view modes:

NoRestrictedFieldActivationMode1 Personal

NoRestrictedFieldActivationMode2 Manager