Use configurations to maintain a common set or series of designs. You can control configurations with one primary file.
- Use View representations to save display configurations that you can recall by name when you work on the component.
- Use Positional representations to configure an assembly in different positions and states.
- Use Level of Detail representations to load only specified components in the display and memory. Suppressed components participate in the BOM, but do not display or consume memory.
- Use iFeatures to create families of commonly used features.
- Use iParts and iAssemblies to create product configurations controlled by a master model. Each member has their own part number and other properties and is stored in a separate file that can be managed and released.
The following settings for iParts and iAssemblies determine how they react to edits.
Note: Delete is a global operation for both Edit Factory Scope and Edit Member Scope. To remove a feature or component from the active member, enable Edit Member Scope and use Suppress or Exclude in the table.