General Principles
All the engineering connections (MCX) that describe a same set of fastened parts (stacking) lead to the creation of a new product of type BundleFastener. The linked fasteners are “moved” under the bundle, the MCX are deleted, and a new PLMConnection describing the stacking is inserted under the bundle
The migration manages products with a configuration context and fastener instances with
effectivity. If the parent product of fastener instances has a configuration context, then
this configuration context is duplicated, points to the same configuration model, and is
placed under the bundle reference. If a fastener instance has an effectivity, the
effectivity is also “moved” under the bundle.
About Migrated Fastener Instances
During the migration process, the fastener instances are in fact recreated, as there is no way in the native app to change the parent of an existing instance. The instances are 'moved' using the Cut-Paste functionality. This means that all the attributes, custom attributes and extensions of the instance are duplicated on the new fastener instance.
Some new attributes introduced with the new Bundle model are also valuated. These new attributes are:
- V_ModelVersion=1. This attribute is set on fastener that are created under a bundle reference
- V_FastenerLocationMethod=Explicit_0_S or Curve_0_S for Beads. This attribute indicates that the location of the fastener is explicit with no associativity with geometry.
The following attributes were set on the MCX and are now set on the fastener instance:
- V_ExcludedRules
- V_SymbolID
