|Bookshelf Home | Contents | Index | PDF|
You can turn on or turn off the read-only status of a business component or business component field while Siebel CRM is running, depending on the value in a specific field in the current record. For more information, see Example of Defining Read-Only Behavior for a Business Component.
Table 12 describes the business component user props that you can use to define read-only behavior. For more information about user properties, see Siebel Developer's Reference.
The BC Read Only Field user property specifies a Boolean field that, if TRUE, changes all fields in the current record to read-only. This property also prevents the user from updating or deleting the record, but does not prevent the user from adding new records to the business component.
Assume you must prevent the user from updating an inactive account. The Inactive Account field in an account record is a TRUE or FALSE field that, if TRUE, indicates that the account is inactive. To configure dynamic read-only behavior for the Account business component, you can add a business component user prop to the Account business component. This example business component user prop contains the following properties:
The Field Read Only Field user property is similar to the BC Read Only Field user property because it tests the field that you define in the Value property and enforces a read-only restriction if the value of the test field is TRUE for the current record. Unlike the BC Read Only Field user property, the Field Read Only Field user property restricts only one field in the business component record rather than restricting all fields in the entire business component record.
The Parent Read Only Field user property, like the BC Read Only Field user property, places a read-only restriction on an entire business component rather than on a single target field. This restriction occurs if a TRUE or FALSE test field includes a TRUE value. Unlike the BC Read Only Field and Field Read Only Field user properties, the Parent Read Only Field user property places a restriction on a child business component of the business component that contains the test field. In the other user properties, Siebel CRM places the read-only restriction on the business component that contains the test field, or on another field in the same business component.
You add the user property as a child of the business component that is conditionally restricted. The business component that contains the test field must be a parent of the restricted business component through a link or through a series of link relationships.
NOTE: If you use the Parent Read Only Field user property, then the value of the Link Specification property of the test field must be TRUE. Otherwise, the dynamic read-only functionality does not work. However, if the child record displays in the multi-value field in the parent business component, then the Link Specification property of the field does not have to equal TRUE.
Assume you must disable the update of the Account Address Mvg Applet if the account record includes a Type of Competitor. To accomplish this, you add the same calculated field as described in Example of Using the BC Read Only Field User Property. You then add a user property to the Business Address business component with the following values:
The Parent Read Only Field: business component name user property allows a child business component to perform a TRUE or FALSE test on multiple parent business components. The behavior of the Parent Read Only Field: business component name user property is similar to the behavior of the Parent Read Only Field user property. However, the name rather than the value specifies the parent business component. If the calculated value of the field is TRUE or Y, then the child business component is read-only. For more information, see Siebel Developer's Reference.
Do not use a business component user prop with an applet that resides in a view where the Admin Mode Flag property of the view contains a check mark. If Admin Mode Flag contains a check mark, then Siebel CRM turns off all insert and update restrictions for the business components that the view uses, including those that the business component user prop defines. Siebel CRM ignores the Sales Rep and Personal visibility modes of the business component. Records that do not include a primary team member are also visible. However, Siebel CRM does not override pop-up visibility.
You must only set the Admin Mode Flag property to contain a check mark in a view that is part of a screen that contains only administration views. Do not use the Admin Mode Flag property for a view in a screen that contains any views that are not administration views. You can create a list view where the Admin Mode Flag property contains a check mark if this list view drills down to a detail view that is not marked as an administration view. This technique allows you to share a detail view with a list view that is not an administration view.
CAUTION: All views and drilldowns in a screen that is granted Admin Mode behave in Admin Mode due to their subordinate relationship to the screen. If a view is a child of a screen that is in Admin Mode, and if the Admin Mode flag for the view does not contain a check mark, then Siebel CRM still displays the view in Admin Mode.
|Configuring Siebel Business Applications||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|