Working with Aliases

Aliases represent logical statements that can be used when authoring conditional rules, advanced assigned expressions, and other aliases.

Aliases allow you to efficiently manage reusable segments of logic. Typically, there are some common definitions that are reused in the configuration of the product. You can capture these common definitions as aliases, and manage them globally for the product. For example, you can create an alias SmallTires and define it as 28IN/30IN/32IN/36IN/48IN by referencing the selected choices from the option TIRE. Next time you create an expression for a conditional rule or for an assigned expression, you can include the alias SmallTires instead of listing all acceptable tire choices.

• Aliases are available only to the members of the Platform Structures group.

• Only Option Managers who are members of the Platform Structures group have permissions to create, edit, or delete aliases. Team members have only Read-only access to the aliases.

Aliases provide you with these benefits:

• You can efficiently create expressions by including aliases in them; thus eliminating the need to retype long strings. This also increases the accuracy and consistency of the configuration logic.

• Because aliases are globally managed for a product or library context, you can easily update the alias if the logic changes. This way, you need not update the changed logic in individual assigned expressions or conditional rules.

• As the logic evolves, an alias can have multiple revisions. You can also apply the date effectivity to the use of the alias versions in advanced expressions and conditional rules.

IF ((HP=45HP/55HP/65HP/85HP and DIFF=IVT/CVT) and Tires=28IN/30IN/32IN/36IN/48IN) THEN Enable Country=CANADA/BELGIUM/FRANCE/MONACO/CH/LUXENBOURG

If you define an alias MidPowerTrain to represent HP=45HP/55HP/65HP/85HP and DIFF=IVT/CVT, and SmallTires to represent Tires=28IN/30IN/32IN/36IN/48IN, then this conditional rule is simplified as follows:

Aliases can be used in logical expressions that are part of advanced expressions, conditional rules, or other aliases. Logical expressions can refer to aliases by their name or number, depending on the user configuration.

When an alias is included in a logical expression, the system validates that the alias exists and that the alias is not calling itself. In addition, companies can plug in site-specific validation.

If an alias has multiple revisions, the configuration specification is used to determine the proper revision of aliases to use in the evaluation of conditional rules and advanced assigned expressions.

Aliases can be referenced in expressions by their name or number, depending on the user configuration. You can assign advanced expressions with aliases to parts and part usage links.

You can include aliases in the logical expressions in the IF part of a conditional rule. Aliases can be referenced by the name or number, depending on the user configuration. Your configuration specification determines the version of the alias to be included in the rule.

When you are filtering a product structure using the Option filter, the filtering logic evaluates the assigned advanced expressions and compares them with the selection criteria. The system evaluates the alias first, and then evaluates the rest of the expression.

Conditional rules that are set up for defining the filtering criteria can also include aliases in its expressions. These aliases are evaluated as part of the logic of the IF statement of the conditional rule.

You can import and export aliases, conditional rules with aliases, and part structures with advanced expressions that contain aliases.

You can publish aliases, conditional rules with aliases, and part structures with advanced expressions that contain aliases to the ESI system.