Tables in Actions and Procedures
Purpose
In actions and procedures, tables are used to infer values.
Prerequisites
Process Flow
The following example is for an action.
The tables calls in actions are the same as the table calls in procedures.Configurable material BIKE has characteristics SADDLE, SADDLE_SUPPORT, and SUPPORT_MATERIAL.
The data for the saddle can determine the type of SADDLE_SUPPORT.1.
Create table T_SADDLE and assign your 3 characteristics to it.
All characteristics are single-value, so you use the same characteristics in the table and in the class.
Characteristic SADDLE is defined as a key field in the value assignment alternative:
Characteristic |
Key Field |
SADDLE |
X |
SADDLE_SUPPORT |
|
SUPPORT_MATERIAL |
2.
SADDLE |
SADDLE_SUPPORT |
SUPPORT_MATERIAL |
SR_ErgoGel |
Patent support |
Steel |
SR_Gel |
Standard support |
Steel |
Touring_saddle |
Standard support |
Aluminum |
MTB_saddle |
Special patent support |
Aluminum |
3.
TABLE T_SADDLE
(SADDLE = SADDLE,
SADDLE_SUPPORT = $SELF.SADDLE_SUPPORT ,
SUPPORT_MATERIAL = $SELF.SUPPORT_MATERIAL)
4.
Allocate this action to the configuration profile.Result
In the class, assign a value to characteristic SADDLE.
The table call in the dependency finds the correct table line and infers values for SADDLE_SUPPORT and SUPPORT_MATERIAL.