Configuration Attribute Editor
Overview
After adding a configurable attribute, the next page is an Attribute Editor specific to the type of attribute you created.
In 19D and later, there are two types of configurable attributes: configuration attributes and signed punch-in attributes. For more information, refer to Configurable Attributes Overview.
Use the General tab to view and edit current information.
The other tabs available are Related Rules, Template Properties and Set Properties.
The Set Properties tab appears only when the configuration attribute is of the type Array.
Administration
Accessing the Attribute Editor
-
Navigate to the Attributes Administration List page.
-
Click Admin to go to the Admin Home Page.
-
Click Catalog Definition in the Products section.
The Supported Products page opens.
-
In the Navigation column, select Attributes and then click List.
The Attributes Administration List page opens.
-
Click the link in the Name column to open the Attribute Editor page specific to the attribute data type.
Order of Operations and Attribute Order
Rules are executed in the order that their related Configuration attribute appears within in the Attributes Administration List page.
In general, most users will not need to reorder their attributes; only a few special circumstances warrant attribute reordering.
- Configuration Flow Rules
- Constraint Rules
- Recommendation Rules
- Constraint Rules (again)
- BOM Mapping Rules
- Hiding Rules
- Recommended Item Rules
- Bill of Materials Rules
Attribute Order & Rule Precedence
Order becomes important when there are dependent Recommendation Rules that need to be calculated in a specific sequence.
For example, D is the sum of B and C; C = A*2. If C appears after D within the Attribute List, D's calculation will use a stale value for C, resulting in an incorrect value for D.
The attribute order affects rule order in the following ways:
- Config rules with "True" conditions are reviewed.
- The rules that reference the first Configuration attribute are run.
- The rules that reference the second Configuration attributes are run.
- Rules on subsequent attributes are run.
Notes
Note: Customers should not use any of the following names for Configuration attribute variable names. Using these values may cause issues with customer configurations and could possibly alter site functionality.
action_id
bm_cm_process_id
_bom_
bs_id
commerce_doc_url_params
commerce_list_id
document_id
document_number
folder_id
formaction
from_config
scrollTop
shopping_cart_id
step_id
token
version_id
- NULL and blank Integer values are treated as separate values:
- Using NULL as an attribute value is strongly discouraged.
- If you use logic that tests for NULL values in rule conditions or BML, confirm that the logic takes this difference into account.
Related Topics
See Also
