Design Family

Definition

Design Family is a parent object that manages basic product information (design name, brand, etc.), under which update history and specific asset definitions are linked in the form of Design Version.

Structure Overview

The object structure on Salesforce is as follows:

• 📦 Design Family (Parent): Management of design name, brand information
  • 📄 Design Version (Child): Update history, Chunk ID, Active flag
    • 🎨 Define Material: Material definition for each slot

Role of Each Object

1. Design Family

Manages the “identity” of the product.

• Management Items: Design name (each language), Vendor Brand (brand name), etc.
• Role: Functions as the parent of all versions.

2. Design Version

Manages design “updates” and “assets (Chunks)”.

• Relationship with Chunk: Chunk ID is granted to Design Version.
  • When a design is updated and becomes a new Version (e.g., 0.0 -> 1.0), a new Chunk ID is issued.
  • This allows the app side to download only the latest Version (Chunk), enabling efficient updates.
• Management Items:
  • Revision Count: Update count (e.g., 0.0)
  • Chunk Id (Short): Asset download ID
  • Active: Whether it is currently active
  • Debug: Whether it is for debugging

Green frame: Design Family / Red frame: Design Version (Salesforce screen)

3. Define Material

An object that defines “which material can be applied to which slot”.

• Lookup: References both Design Version and Product Attribute.
• Role: Maps Product Attribute (choices users can select) to Design Version (shape) and determines specific materials (Fabric, Wood, etc.).

Define Material screen: Slot definitions like Element0, Element1

Registration Criteria

When creating a new Design Family, determine the scope considering the following technical structures.

1. Identity of Material Structure

Meshes belonging to the same Family (Version) must conform to the slot structure (Element0, Element1…) defined in Define Material. Variations that can be managed with a common slot definition (such as size differences) are managed under the same Family/Version.

2. Efficiency of Chunk

Chunks are generated per Design Version.

• Merit of grouping: If related products (such as sofa and ottoman) are included as Mesh variations within the same Version, they can be batch downloaded with a single Chunk ID.
• Case for separating: Completely different designs or products not used simultaneously should be managed as separate Families (separate Chunks) to prevent unnecessary downloads.