Define elements of a Model in Oracle Configurator Developer for use with this extension. For details about defining Model elements, see the Oracle Configurator Developer User's Guide.
1. For the Line Types that you have defined in Oracle Order Management (as shown in the example in the table Example Line Types Defined in
OE_TRANSACTION_TYPES_TL, page 11-14), define sets of Properties in the Main area of the Repository. Each Line Type will require at least one set of properties, and may require more, depending on how many ways you plan to test for the Line Type. For example, a Line Type of CHANGE may need multiple tests (for attribute changes, name changes, and so on), and each test will require a set of properties.
Use the settings shown in the table below. In each set of Property names, replace n with an integer, incrementing n by 1 for each set. There is no limit on the number of sets you can specify.
User Properties for Line Types
Name Data Type Default Value
LINETYPE_n_NAME Translatable Text (Definition is optional.)
LINETYPE_n_ID Integer (Definition is optional.)
LINETYPE_n_TEST Text (Definition is optional.)
The result should be multiple sets of Properties named in the following pattern:
LINETYPE_1_NAME, LINETYPE_1_ID, LINETYPE_1_TEST, LINETYPE_2_NAME, LINETYPE_2_ID, LINETYPE_2_TEST, LINETYPE_3_NAME, LINETYPE_3_ID, LINETYPE_3_TEST, and so on
Note that you may not want to enter a default value for these Properties. If your implementation has a standard set of tests that do not vary much when applied to specific nodes, then it might be more convenient to set them as default values. But if multiple products have different Line Types and different ways of testing for them, then you should not set default values. You will be entering node-specific
properties in a subsequent step.
The form of these Property names is mandatory, unless you modify the source code for this extension to search for different strings. Oracle recommends that you not make such a change.
Important: In cases where the remote server for publication has TRANSACTION_TYPE_ID values that differ from those in the Configurator instance being used for development testing or staging, the published model will have incorrect Property values.
For this reason Oracle recommends that you use only LINETYPE_n _NAME to set up the Line Type Configurator Extension. The previously documented use of LINETYPE_n_ID is still supported, but is deprecated. If you use both NAME and ID, their values may not match. This Extension does not check this situation, but uses the last Property that it examines.
2. For each root node in your container Model that requires Line Types, add a set of these LINETYPE_n Properties on that node for each applicable Line Type, with node-specific values, as described in the following steps.
The Properties can be defined on a BOM Model, BOM Option Class, or BOM Standard Item.
3. Set the priority of the Line Type relative to the other Line Types, by selecting the set of Properties that correspond to this priority, using the integer part of the Property name to indicate the priority. The priority determines the order, at runtime, in which this extension applies tests to the associated node. The first test that passes (that is, returns a True value) causes the assignment of the corresponding Line Type to the node.
For example:
• LINETYPE_1_TEST is applied first.
Set Up Oracle Configurator Extensions 11-17
• If LINETYPE_2_TEST passes, then the value of LINETYPE_2_NAME is assigned to the node as its Line Type.
• If LINETYPE_2_TEST fails, then LINETYPE_3_TEST is applied, and so on.
4. For the LINETYPE_n_NAME (or LINETYPE_n_ID) member of the Property set, enter the instance-independent NAME (or instance-specific
TRANSACTION_TYPE_ID) for the Line Type, as shown in the table, Example Line Types Defined in OE_TRANSACTION_TYPES_TL, page 11-14.
For example, for the Line Type called ADD, enter ADD as the value of the Property LINETYPE_1_NAME (or enter 2476 as the value of the Property LINETYPE_1_ID).
The value you enter for LINETYPE_n_NAME is of type Translatable Text. You must ensure that this name is unique for the translated language in which you enter it, and that it corresponds exactly to the translated value of the NAME defined in Order Management table ONT.OE_TRANSACTION_TYPES_TL.
5. For the LINETYPE_n_TEST member of the Property set, enter a token string which indicates the CIO test that determines whether the specified type of change
occurred that corresponds to the Line Type. The token string is composed of the string &BaseNode. combined with one of the predefined CIO test methods listed in the table, Methods for Identifying Changes Against the Baseline, page 11-30, later in this chapter. (If you wish to use the method
isIBNodeOrDescendantChanged(), you must customize the code of this extension.)
For example, for the Line Type called ADD, you would probably enter the following token string:
&BaseNode.isAddChanged()
If you use the method isTargetChanged(), then you must use the token string syntax &BaseNode.Connectorn.isTargetChanged(), for each Connector, since the target change is on the Connector, not on the Base Node.
You must determine which test corresponds to your own definition of the meaning of a particular Line Type. If the CIO tests listed in the table, Methods for Identifying Changes Against the Baseline, do not capture some of your Line Types, then see the section, Setup in Oracle Configurator Developer Using Features, page 11-21.
6. When you have finished defining your Property sets, the results should resemble the contents of the table Line Type Definitions Compared to User Properties for Line Types, page 11-18, which combines the Line Types shown in the table Example Line Types Defined in OE_TRANSACTION_TYPES_TL, page 11-14 with the Property definition sets that correspond to each of them. The Line Type priorities shown for LINETYPE_n are for demonstration only. You must assign your own priorities.
Line Type Definitions Compared to User Properties for Line Types
2476 ADD 1 ADD 2476 &BaseNode.isAddCha
nged()
2477 CHANGE 3 CHANGE 2477 &BaseNode.isAttrib
uteChanged()
2516 MOVE 4 MOVE 2516 &BaseNode.isLocati
onChanged()