About Field Management
In Oracle CRM On Demand you can perform the following field management tasks for the different record types:
When you create custom fields or edit field definitions, you can specify default values for the field that take effect when new records are created. You can also specify that field validation is performed for the field to ensure that it has a particular value.
About Copying Fields
Most record types in Oracle CRM On Demand have a copy function; that is, users can copy the current record they are using. When a user clicks the Copy button on the Record Detail page, it opens a new record page. This new Record Page contains all the fields that can be copied. A user can change and save these fields.
NOTE: When you use the Copy button, only the base record is copied, but not the related item for child records.
The following restrictions apply when using the copy function:
You can copy fields by using the Copy button in record detail pages in Oracle CRM On Demand. You can enable this setting by using the Copy Enabled check box in the Field Management page of the Application Customization section of Oracle CRM On Demand. For more information on specifying which fields can be copied in Oracle CRM On Demand, see Administering the Copy Enabled Setting.
About Field Validation
When you create custom fields or edit field definitions, you can specify in the Field Edit page that fields are required or read-only. You can also specify predefault or postdefault values on new records.
There are various situations where you might define fields as required. For example, your company might require that every service request must track information on the cause of a service request. In this case, you specify that the Cause field for service requests is required. Then, when a record is created or updated, and saved, the application validates that the Cause field is NOT NULL.
As another example, your company might have a business policy that if an opportunity is lost, which had an expected revenue of $100,000 or greater, the reasons for losing must be tracked. In this case, you define the Reason field on Opportunity as required only when the Revenue field has a value greater than 100,000. When an Opportunity record is saved, the application validates that the Request field's value is greater than 100,000.
If a validation fails, an error message is displayed, warning users to enter a value for the required field before saving the record. You can also specify a custom error message (in the Field Validation Error Message field) to be displayed if the validation fails.
When you specify a field as Required, the validation is enforced through all interfaces, including the user interface, Web Services, and data import.
The fields specified as required in the Field Edit page, are required fields for all users, regardless of their role. If you need to make a field required only for a specific role, you can do so by editing the appropriate page layout for fields that are not already required fields. For more information, about editing page layouts, see Customizing Static Page Layouts.
The following are situations in which you might define fields as read-only:
Custom Field Validation Rules
You can use Oracle On Demand Expression Builder (Expression Builder) to create expressions for custom field validation rules. You can click the fx icon next to the Field Validation field to open the Expression Builder window in which you can enter an expression. For information about the syntax you can use for expressions, see Expression Builder.
The following are situations in which you might define custom field validation rules:
The following circumstances prevent a field validation expression from being evaluated:
If a validation expression is not evaluated, or if a validation expression evaluates to NULL, no error message is generated. An error message is generated only when the validation expression fails (that is, the expression evaluates to FALSE).
Field validation expressions assume that the first parameter is the field name itself. If, for example, you are putting a simple field validation expression on an Amount field to specify that the value must be greater than 1000, it is sufficient to enter >1000. You do not need to enter [<Amount>]>1000. For more information on more complicated expressions, see About Expressions.
Restrictions on Specifying Field Validation Rules
You cannot specify field validation rules for these types of fields:
About Defining Default Field Values
You can specify default values for fields in the Default Value field in the Field Edit page when you create custom fields or edit field definitions.
Specifying a default value for a field is useful where you require:
NOTE: Most of these are possible only if your role includes the Advanced Field Management privilege.
There are two types of default values for fields:
Pre Default is the default type of value for fields. You can specify Post Default by selecting the check box of that name in the Field Edit page.
NOTE: Post Default field values are not supported in the Offline client, and display as blank fields.
Default field values are applicable to new records only, and not applicable to record updates.
If you specify a default value for a field that already has a system-specified default, your value takes precedence for your company. An exception to this rule is the Revenue field on Opportunity records. Any default or post default values you specify for this field are ignored, because the field is used in the generation of forecasts based on opportunity revenue.
You cannot set default values for these types of fields:
The following table shows the default values that you can specify for the different field types in Oracle CRM On Demand.
NOTE: If you create an expression to set a default value, the result of the expression must not exceed the maximum number of characters allowed in the field. In addition, any string or numeric literal passed to a function in Expression Builder must not exceed 75 characters. For more information about using Expression Builder, see Expression Builder.
You can also create complex expressions for default field values. You can enter an expression directly in the Default Value field, or click the fx icon to open the Expression Builder window, where you can enter an expression. For information about the syntax you can use for expressions, see Expression Builder.
To use Expression Builder in field management, you must have the Advanced Field Management privilege in your user role. Users who have the Administrator role can enable this privilege for their own role and for other roles.
|Published 5/4/2012||Copyright © 2005, 2012, Oracle. All rights reserved. Legal Notices.|