Troubleshooting Access Control Issues

This topic describes problems related to access control. To resolve the problem, look for it in the list of Symptoms or Error messages in Table 10-3.

Table 10-3 Troubleshooting Access Control Issues

Symptom or Error Message	Diagnostic Steps or Cause	Solution
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).	Give the Employee user a separate login account for the customer application.
Cannot delete Division records.	You cannot delete division records because business components throughout your Siebel application refer to organizational records. Deleting a division might cause invalid references on transactional records.	Rename the division or promote the division to an organization.
Cannot modify seed responsibility.	Seed responsibilities cannot be modified or deleted.	Make a copy of the seed responsibility you want to modify and make changes to the copy.
Excessive synchronization time for some Mobile users.	The Local Access control field in the Responsibility View list might not be set properly. This setting determines which views mobile users can work in offline.	Make sure the Local Access control field in the Responsibility View list is set properly. 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, if you collapse or expand a detail applet, the record is committed and the business component is queried again.	You can override the default behavior by setting the user property RestrictedFieldActivation to FALSE; this stops the business component from being re-queried if the detail applet expands or collapses. You can set RestrictedFieldActivation to FALSE in a number of locations. However, for scalability reasons, it is recommended that you only set RestrictedFieldActivation to FALSE 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. 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: NoRestrictedFieldActivationModenumber valueOfVisibilityMode For example, the following entry overrides the default behavior in the Personal view mode: NoRestrictedFieldActivationMode1 Personal
Multiple sessions of an eCustomer application are opening in the same browser, without throwing any session warning message.	An eCustomer can open multiple sessions of eCustomerObjMgr_enu in the same browser (all HTML5-compliant browsers) without receiving a session warning message.	The multiple sessions warning message only works on regular (login) sessions and does not work on anonymous browsing sessions that circumvent the login page (for example: SWECmd=GotoView). There is no request for login if an anonymous user has access to the home page and the object manager session is directed to the home screen (via SWECmd=GotoView). For the multiple sessions warning message to appear in an anonymous browsing session, you must request the login page using a regular session instead of anonymous browsing. Instead of using the SMECmd=GotoView mechanism in the application interface, define the start page at the application level (for example, in Siebel Tools).