Lists of values (LOVs) are used in common property dialog box and Structure Editor property fields are used to ensure consistent data input into a database. The list entries are created either by referencing existing data or by entering customized data for your managed site. Once created, the List of Values is implemented throughout the user interface by attaching the List of Values to one or more Teamcenter or SharePoint properties. Using Lists of Values helps you improve productivity and helps prevent incorrect user entries.
In Teamcenter 5.1, Lists of Values are managed through RAC's Administrator application. In Teamcenter 7.1 and greater, Lists of Values are managed through BMIDE and then deployed to the Teamcenter database. Regardless of the version of Teamcenter you are running, all Lists of Values are implemented using a similar process.
Create a List of Values
When you create a new List of Values, you create a new object that references existing data in Teamcenter (for example, group names) or contains some custom data (a range of serial numbers) that you want to store in the List of Values.
Attach the List of Values
You must attach the List of Values to the appropriate property in order for the List of Values to display in the user interface. Attaching the List of Values to a property type links it to any input box where that data is entered. A list with the selected values is then displayed in the user interface.
Note:
The Solid Edge Embedded Client Administrator's Guide provides details on mapping lists of values.
There are five value types you can use to construct Lists of Values. Each List of Values can contain only one of the following value types. Value types cannot be mixed in the same List of Values.
|
Value |
Definition |
|
Integer |
Whole number. |
|
Double |
Double-precision floating point decimal number. |
|
Char |
Single ASCII character. |
|
String |
String of ASCII characters. |
|
Date |
Date and time (uses the Regional and Language Options Settings in Control Panel). |
Each List of Values must be assigned one of three usage types:
|
Symbol |
Type |
Description |
|
|
Exhaustive |
Defines all possible entries. Exhaustive lists prevent you from specifying a value that is not contained in the exhaustive list of values. |
|
|
Suggestive |
Provides a suggested list of choices. However, you can enter a value not contained in the list. For example, a suggestive list of values can be used to show commonly used description strings as with a Material Library. You can select one of the suggested description strings from the List of Values or enter another user-defined string. |
|
|
Range |
Indicates that the choice falls within a range of numeric values. You are prevented from specifying a value not contained within the range. For example, a range List of Values can be used to construct a small consecutive list of serial numbers. |
Note:
When you create a List of Values, you must exit and restart the application to see an updated list. The Lists of Values are evaluated once per session.
The LOV usage types can be implemented using basic, filtering, cascading (also known as hierarchical), and interdependent lists.
A Filter LOV is based on an existing LOV definition. You have the option to hide values. Filter LOV's can be of any LOV usage type (Exhaustive, Suggestive or Range) and they can be used with a Cascading or Interdependent LOV's.
A Cascading LOV (also known as hierarchical) is a list of values whose values contain other lists of values. Cascading LOV's can be Exhaustive, Suggestive or Range and have multiple entries per level, and be multiple levels deep. The only entry that is written into the property in the database is the end-point (leaf node) value.
Interdependent LOV's keep track of every entry you pick (a roadmap) and can be Exhaustive or Suggestive. The root note determines the structure's LOV usage type. For example, if the root node is Exhaustive, but a child is Suggestive, the entire group of properties is Exhaustive. User defined values are not inserted into the structure. Determine your selections by working from left to right in the common property dialog box.
Note:
All dependent properties must be mapped.
|
Symbol |
Type |
Example |
|
|
Cascading Exhaustive |
A list of states that contains a comprehensive list of cities to choose from. Only the city you choose is entered into the property. |
|
|
Cascading Suggestive |
A list of cities that contain a partial list of zip codes related to each city. You can enter zip codes that are not in the list. Only the zip code you choose is entered into the property value. |
|
|
Interdependent Exhaustive |
A list of cities where your choice determines the state that is displayed as your next choice. The selections you make are entered into the property value. The end-point (leaf node) value may not be unique. Example: Huntsville, Alabama Huntsville, Texas |
|
|
Interdependent Suggestive |
A list of cities where your choice determines the state that is displayed as your next choice and you need to be able to enter a user-defined value. Each entry you choose is entered into the property value. |
Parent-child relationships can be created between Lists of Values. These relationships can be balanced or unbalanced. In a balanced List of Values, each level of the List of Values displays a related set of values. For example, the first level of the List of Values could display state values, the second levels show city values, and the third levels show zip code values.
In an unbalanced List of Values, each level of the List of Values does not have related sets of values. For example, the first level shows related values such as states. In one set the second level shows cities, and in the other set the second level shows zip codes.
Note:
Unbalanced Lists of Values are not supported in Teamcenter Unified Architecture or Teamcenter Engineering.
In Solid Edge Embedded Client, you interact with Lists of Values when you define properties on common property dialog boxes where lists of values have been defined by a Teamcenter administrator. Two examples of dialog boxes where you see LOVs are the New Document dialog box and the Upload Document dialog box.
In Structure Editor, you interact with Lists of Values through the source and target window panes.
Basic and cascading LOV's are shown in the common property dialog box in a single column, a supported LOV type, and a LOV usage type of Exhaustive, Suggestive, or Range. A Cascading LOV displays the Select Cascading LOV dialog box to define the property.
Your interaction with various types of Lists of Values differs. The symbol associated with each type acts as a visual cue to aid you in knowing what behavior to expect.
|
Symbol |
Type |
Interaction |
|
|
Exhaustive |
|
|
|
Suggestive |
|
|
|
Range |
|
|
|
Cascading Exhaustive |
|
|
|
Cascading Suggestive |
|
Lists of Values with Property Description attachments capture both the selected value and its defined description in separate properties. Property description attachments can be used with Exhaustive and Suggestive LOV's.
A basic or cascading LOV with a property description attachment displays two columns on the common property dialog box where one column is master and the other is dependent. The master property is shown in the left column in the common property dialog box, and the dependent property is shown in the right column. If either of the columns move, both columns move to maintain their relationship. When the master property is defined through input from the user, the dependent property is empty.
Interdependent LOVs with property description attachments are represented on the common property dialog boxes by a master column and a group of dependent columns, a supported LOV type and an LOV usage type of Exhaustive or Suggestive. The root note is writable and the dependent columns are read-only.
