Information for migration
Migration was not preformed due to complexity and ambiguity. At the moment, the configuration should be done manually.
To use image slots in HTML 5 client a user has to perform the following configuration:
-
Frontend:
-
Create "Reference table" attribute definition in Classification view → Configuration → Attribute definition pool (frontend)
-
Create the "Reference table" attribute by linking the attribute definition to a classification node via DnD in Classification view → Configuration → center/left view (frontend)
-
Set necessary characteristics for the attribute in Classification view → Templates (frontend) for each available template separately including:
-
"Linked attributes" (center) view:
-
'attribute product type' - defines for which object in Product/Article/Variation the attribute is available
-
'inheritance type' - defines if the attribute is available and editable on the lower levels in Product/Article/Variation hierarchy (not visible - unavailable, visible - available without possibility to set own value, editable - available and changeable)
-
'language dependence'
-
'optional/required/mandatory' option
-
-
"Node for PEO strategy" view
-
'attribute PEO behavior' - defines the behavior of the attribute in PEOs:
-
not used
-
use from PIM2 - uses product value and no own value can be assigned in PEO
-
use in PEO - default value comes from product but can be overwritten with own PEO value
-
direct link - product value is used, changes in PEO are possible and affect the product value as well
-
-
-
-
Use the configured "Reference table" to link objects to a specific product/article/variation (frontend) -optionally
-
-
Config client:
-
Add the corresponding "Reference table" attribute in FSDetail of 'Product Export Option 2' object type
-
Use the configured FSDetail in PEOView function plugin configuration as a content view
-
Afterwards, configured reference table can be used in the frontend to visualize related(linked) images in defined PEOs as described in the Configuration section above.
|
The compatibility of PEOs created in old client with HTML5 PEO functionality is ensured, including:
|