Defining Attribute Transfer Values
Relationship types can also be used to define the values for those attributes that are transferred to the copied product. Attributes can be defined to be set to one of three values:
• The same value as the original attribute (default setting)
• A specified value
• No value (the user manually enters a new value)
There are two different property settings, depending on whether the user has selected a relationship type.
|
|
Attribute transfer value property settings must be entered in the attributesTransfer.properties file, which is found in the codebase.
|
Out-of-the-Box
By default, the system uses the original attribute value for the copied attribute value when copying products. You are not required to enter a property setting to enable this. Out-of-the-box, the system does this automatically, regardless of whether the user has selected a relationship type.
Configuration
To specify a value, or to specify no value for copied attributes, you must enter a property setting for each attribute that you want to have either a specified value or no value. One property setting controls those attributes and values when no relationship type is selected. The second property setting defines the attribute values for specific relationship types.
The basic form of the property setting to control attribute transfers is:
<TypeClass>^<TypeName>^COPY.<RelationshipTypeName>^<AttributeTypeContext>^<AttributeKey>=<value>
Each property setting entry is separated by a caret (^).
|
|
The <AttributeTypeContext> entry is required only for product-season and cost sheet objects, as these objects can exist on both the Product and Colorway types. Attribute type contexts must be entered in all capital letters, either as PRODUCT or SKU.
|
Specific Objects and Object Types
Before you can enter property settings, you must first know which objects are available for attribute transfer, as well as their object type.
This table only displays the root object type name. However, you can enter any corresponding object subtype in the property setting for the <TypeName> entry, as long as it is entered in the standard format. Product\Apparel is an example of an object subtype entry.
The two object types are equivalent to the <TypeClass> entry and the <TypeName> entry in the property setting (if you use the root object type).
|
|
You can access these entries yourself from the side navigation bar by clicking > .
|
You can specify attribute transfer values for the following objects and their corresponding root object types.
|
Product Option
|
Type Class Entry
|
Type Name Entry
|
|
Bills of Labor
|
com.lcs.wc.flexbom.FlexBOMLink
|
BOM Link
|
|
Bills of Materials
|
com.lcs.wc.flexbom.FlexBOMPart
|
BOM
|
|
Colorways
|
com.lcs.wc.product.LCSSKU
|
Colorway
|
|
Constructions
|
com.lcs.wc.construction.LCSConstructionInfo
com.lcs.wc.construction.LCSConstructionDetail
|
Construction
Construction Detail
|
|
Cost Sheet (requires <AttributeTypeContext> entry)
|
com.lcs.wc.sourcing.LCSCostSheet
|
Cost Sheet
|
|
Documents
|
com.lcs.wc.document.LCSDocument
|
Retail Document
|
|
Document (images page)
|
com.lcs.wc.document.LCSDocument
|
Retail Document
|
|
Measurements
|
com.lcs.wc.measurements.LCSMeasurements
com.lcs.wc.measurements.LCSPointsOfMeasure
|
Measurements
Measurements POM
|
|
Product
|
com.lcs.wc.product.LCSProduct
|
Product
|
|
Sources
|
com.lcs.wc.sourcing.LCSSourcingConfig
com.lcs.wc.sourcing.LCSSKUSourcingLink
com.lcs.wc.sourcing.LCSSKUSourceToSeasonLink
|
Sourcing Configuration
Sourcing Configuration to Colorway
Sourcing Configuration to Season
|
|
Specifications
|
com.lcs.wc.specification.FlexSpecification
|
Specification
|
To configure product-season attribute values, use the following entry:
|
Type Class
|
Type Name
|
|
com.lcs.wc.season.LCSProductSeasonLink
|
Product Season Link
|
|
|
You must include an <AttributeTypeContext> entry, either PRODUCT or SKU, for all product-season attributes.
|
Property Setting for Not Specifying a Relationship Type
This property setting is used to specify the values for those attributes that are transferred when no relationship type is selected.
The basic form of the property setting to control attribute transfers without specifying a relationship type is:
<TypeClass>^<TypeName>^COPY^<AttributeTypeContext>^<AttributeKey>=<value>
|
|
Each property setting entry is separated by a caret (^).
|
The <AttributeTypeContext> entry is required only for product-season and cost sheet objects, as these objects can exist on both the Product and Colorway types. If the property setting does not reference a product-season or cost sheet, then you must omit the <AttributeTypeContext> entry, but still enter all carets. The resulting property setting contains two side-by-side carets following the COPY entry.
^COPY^^<AttributeKey>
You can set the property setting to one of two values:
• A specific value, which all transferred attributes of this type have.
• No value (blank), which clears the attribute value and allows the user to manually enter a value for the transferred attribute.
The indication of a specific relationship type, such as MissyPetite is absent from this property setting.
Examples of Property Settings for Not Specifying a Relationship Type
• In this example, for all Constructioncomments attributes on the ConstructionInfo type class on the Construction type, the system enters a value of Copied Construction when no relationship type is selected. This property setting does not include an <AttributeTypeContext> entry because it does not reference a product-season or cost sheet object.
com.lcs.wc.construction.LCSConstructionInfo^Construction^COPY^^constructioncomments=Copied Construction
• In this example, for all specName attributes on the FlexSpecification type class on the Specification type, the system clears the original value and leaves the value of the copied attribute blank. This allows users to manually enter values for transferred attributes such as names, comment fields, and so on. This property setting does not include an <AttributeTypeContext> entry because it does not reference a product-season or cost sheet object.
com.lcs.wc.specification.FlexSpecification^Specification^COPY^^specName=
• In this example, for all margin attributes on the LCSCostSheet type class on the Cost Sheet type, the system enters a value of 60% when no relationship type is selected. Because this relationship type includes an <AttributeTypeContext> entry of PRODUCT, this setting only applies to cost sheets on the Product type.
com.lcs.wc.sourcing.LCSCostSheet^Cost Sheet^COPY^PRODUCT^margin=60%
This property setting includes an <AttributeTypeContext> entry.
|
|
Attribute context types must be entered in all capital letters, either as PRODUCT or SKU.
|
Property Setting for Specifying a Relationship Type
This property setting is used to specify the values for those attributes that are transferred when a relationship type is selected.
The basic form of the property setting to control attribute transfers specifying a relationship type is:
<TypeClass>^<TypeName>^COPY.<RelationshipTypeName>^<AttributeTypeContext>^<AttributeKey>=<value>
|
|
Each property setting entry is separated by a caret (^).
|
The <AttributeTypeContext> entry is required only for product-season and cost sheet objects, as these objects can exist on both the Product and Colorway types. If the property setting does not reference a product-season or cost sheet, then you must omit the <AttributeTypeContext> entry, but still enter all carets. The resulting property setting contains two side-by-side carets following the COPY.<RelationshipTypeName> entry.
^COPY.<RelationshipTypeName>^^<AttributeKey>
You can set the property setting to one of two values:
• A specific value, which all transferred attributes of this type have.
• No value (blank), which clears the attribute value and allows the user to manually enter a value for the transferred attribute.
The indication of a specific relationship type, such as MissyPetite must be present in this property setting.
Examples of Property Settings for Specifying a Relationship Type
• In this example, when a user selects the MissyPetite relationship type, for all constructioncomments attributes on the ConstructionInfo type class on the Construction type, the system enters a value of Copied Construction. This property setting does not include an <AttributeTypeContext> entry because it does not reference a product-season or cost sheet object.
com.lcs.wc.construction.LCSConstructionInfo^Construction^COPY.MissyPetite^^constructioncomments=Copied Construction
• In this example, when a user selects the MissyPetite relationship type, for all specName attributes on the FlexSpecification type class on the Specification type, the system clears the original value and leave the value of the copied attribute blank. This allows users to manually enter values for transferred attributes such as names, comment fields, and so on. This property setting does not include an <AttributeTypeContext> entry because it does not reference a product-season or cost sheet object.
com.lcs.wc.specification.FlexSpecification^Specification^COPY.MissyPetite^^specName=
• In this example, when a user selects the Missy-Petite relationship type, for all margin attributes on the LCSCostSheet type class on the Cost Sheet type, the system enters a value of 60%. However, because this relationship type includes an <AttributeTypeContext> entry of PRODUCT, this setting only applies to cost sheets on the Product type.
com.lcs.wc.sourcing.LCSCostSheet^Cost Sheet^COPY.Missy-Petite^PRODUCT^margin=60%
This property setting includes an <AttributeTypeContext> entry.
|
|
Attribute context types must be entered in all capital letters, either as PRODUCT or SKU.
|
