The REF field type is used to specify that the definition of a field is based on the definition of another field. The name of the referenced field must be specified in the definition. The referencing field is given the same attributes as the referenced field but has a different field name.
The text, check and default conditions, and generation name are unique for each field. You can override these attributes.
The field length, data type, usage, and edit codes are shared. A REF field can inherit narrative (help text) from the referenced field.
You can specify different check and default conditions for the referenced and referencing fields.
For example, an existing STS field called State has all of the state abbreviations listed as conditions. If you need two states for an Order, two fields can be created: Ship To State and Bill to State. Both of these new fields would be REF fields, referencing the field State. They can now share the same conditions of the field to which they refer, State.
Defining a group of similar fields as REF fields, based on one particular field, ensures that all the fields in the group belong to the same domain as defined in CA 2E.
CA 2E carries out domain checking to ensure that only a field of the right type and size is passed as a parameter to a function.
REF fields do not share the same true domain. They do, however, share the same set of conditions. Where CA 2E requires a field to be in the same domain, the field must be the parent field or a REF field referencing the parent.
Examples of REF fields include:
|
Copyright © 2014 CA.
All rights reserved.
|
|