|
The Advanced Data Modeling Tasks covers the following topics: |
|
Every class property must have an appropriate logical data type so that you can specify how you want the property data to be stored in the database. CES provides many pre-defined logical data types. This table details the logical data types:
|
||||||||||||
|
This task explains how to work with items in the Logical Data Type Definition window: |
||||||||||||
|
|
|
You need to create formulae primarily for converting units of measurement. You can specify a complex expression or supply a multiplier, addend, and the order in which they need to be applied. The Unit Conversion Formulae refers to the formulae you create. If you have already assigned a formula to a Unit Conversion Formula object, you can edit that formula. |
||
|
This task explains how to edit a formula: |
||
|
|
|
The CES Data Modeler provides many pre-defined units of measurement. In most cases, you do not need to create additional units. However, if you cannot find an appropriate unit, you can create your own unit and edit it. The CES Data Modeler can convert property values from one unit of measurement to another. For example, a value can be stored in one unit of measurement and displayed in another unit. If you create new units of measurement, for which you want the CES Data Modeler to perform a conversion, you need to provide the necessary conversion formulae. |
||
|
This task explains how to edit a unit of measurement: |
||
|
|
|
Class Aliases are user-defined alternate labels (names) for existing class names. The Class Aliases class in CES helps you create alternative names for the Classes. An existing class can have more than one Class Alias, and a single Class Alias might refer to more than one class. For example, you may try searching for lighting fixtures under the name "BULB" instead of the standard name "Lamp or Display Device". By associating aliases with existing class labels, you can search for existing classes using the familiar Class Alias name. |
||
|
This task explains how to work with items in class alias: |
||
|
|
|
Generic Referencing Counting (GRC) is a mechanism that provides an automatic way of counting the number of references made to an CES pointer object. For example, you may need to keep track of the number of parts provided by a given manufacturer. The GRC creates a counter that counts the number of references made between the Parts class (source class) and the Manufacturer class (target class). This count gives you the total number of parts provided by the manufacturer. |
||
|
This task explains how to work with items in Generic Reference Count: |
||
|
|
|
The Pattern Valid Value defines a set of valid patterns for the values of a property. For example, a class property designed to hold an Internal Part Number, 100-7067-00, could be associated with a pattern defined as "999-9999-99". You can associate many patterns with a property. For example, an internal part number pattern could be different for different manufacturers. Patterns are defined in the Pattern Valid class. This defined pattern is then assigned to a class property by specifying a pointer to that property. This causes the value for that property to be validated against the pattern. Values that do not conform to the pattern are flagged as errors at the time of validation. Many Pattern Valid Values can be associated with a single property. This allows many patterns to be legal for a single property. To reuse Pattern Valid Values, different class properties also point to the same PVV object. Thus, there is a many-to-many mapping between pattern objects and class properties. The Pattern To Property Map mapping class establishes this mapping. |
||
|
This task explains how to work with items in Pattern to Property Map: |
||
|
|
|
The Pattern Valid Values help you define search criteria for specific variable patterns. You can define many values for a single variable depending on the Forms, Users, and User Groups. For example, to search all class names beginning with a double quote create a pattern variable value named Class and search for this pattern in the Class Label property of the Classes class. All class names beginning with Class are displayed in the Results window. |
||
|
This task explains how to work with items in Pattern Valid Values: |
||
|
|
|
It is often useful to create a property whose value is an automatically generated integer. For example, this can be used for an employee ID number or an Invoice number. The auto sequence generator in CES facilitates the creation of these properties. Each time you insert a new object, the auto sequence generator automatically increments the last assigned value. For better control over the parameters defining the auto numbering sequence, you can define an object in the Auto Sequences class and then refer to that object in the Sequence Label field. The Auto Sequences class defines a name (label) and parameters, such as the starting value, for your auto sequence generator. |
||
|
This task explains how to work with items in Auto Sequences: |
||
|
|
|
The Pattern Variable Values helps you to define a search criteria for specific variable patterns. You can define many values for a single variable depending on the Configurations, Users, and User Groups. For example, to search all class names starting with Class, create a pattern variable value named Class* and search for this pattern in Class Label property of the classes class. All class names beginning with Class are displayed in the Results View window. |
||
|
This task explains how to work with items in Pattern Variables: |
||
|
|
|
By default, CES provides many units of measure. It also provides the conversion formulae necessary for users to convert values based on a new unit of measure. If you create new units of measurement, for which conversion is to be performed, you need to provide the necessary conversion formulae. You do this by creating formulae, and then entering the name of the formula as an object in the Unit Conversion Formulae class. |
||
|
This task explains how to work with items in Unit Conversion Formulae: |
||
|
|