ig.creator:products:virtual
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
ig.creator:products:virtual [2019/04/16 17:26] – eb_ig | ig.creator:products:virtual [2024/04/04 08:04] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Virtual Products ====== | ||
+ | |||
+ | Sometimes, it is useful to introduce additional products that are **not** present in the original commercial data, i.e. to simplify 3D modeling or use in ICOM. Such products are called **Virtual** or **Base Products**. | ||
+ | |||
+ | A regular Product has a representation in the Commercial Data as well as a 3D representation. Alternatively it may be mapped to another product that provides the (parametric) 3D representation. That product is called **Virtual** or **Base Product**. | ||
+ | |||
+ | As part of the definition of a mapping of a Product to a Virtual/ | ||
+ | |||
+ | The main purpose of Virtual Products is to simplify 3D data creation by introducing higher levels of configuration, | ||
+ | |||
+ | **Note** | ||
+ | |||
+ | * If a Product has an own 3D representation, | ||
+ | * If identical property keys are used both in the mapping and in the commercial data, the first ones will be overridden by the later of which. Better avoid this! | ||
+ | * The IG.ICOM.Server and IG.GFX.Server will use the mapping information from IG.Creator to support Virtual Products, too. | ||
+ | |||
+ | |||