How the Parent Read Only Field User Property Works
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 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 can use the Parent Read Only Field user property to do the following:
Restrict the child records that Siebel CRM includes in a multi-value group.
Restrict the child records that Siebel CRM includes in a master-detail view. You must make sure that Siebel CRM does not use the restricted business component in the context of some other business object.
The Parent Read Only Field user property includes the following properties:
Name. Contains Parent Read Only Field.
Value. Contains an expression in the following format:
business component name.field name
where:
business component name is the name of the business component where the test field resides. For example, Account.Inactive Account.
field name is the name of the test field. This field is the TRUE or FALSE field that Siebel CRM evaluates.
You add the user property as a child of the business component that Siebel CRM restricts according to a condition. 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.
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. If it is not TRUE, then the dynamic read-only functionality does not work. If Siebel CRM displays the child record in the multi-value field in the parent business component, then the Link Specification property of the field does not have to equal TRUE.
Example of Using the Parent Read Only Field User Property
Assume that if the account record includes a Type of Competitor, then Siebel CRM must not update the Account Address Mvg Applet. To do configure this requirement, you add the same calculated field that the How the BC Read Only Field User Property Works topic describes. You then add a user property to the Business Address business component with the following values:
Name. Parent Read Only Field.
Value. Account.Competitor Calc.
This configuration causes the Account Address Mvg Applet to be read-only if the account record is for a competitor.