Use Official Scenarios in New Assemblies

Use this setting to determine which scenario gets included when a new assembly is created, or when a new part is added to an existing assembly. This can be useful to handle situations such as catalog parts which have a consistent standard list price, even when included in different assembly scenarios representing different production conditions. This preference provides the following settings:

• Always: The Official scenario of the child will be used unconditionally.

• When Component Exists But No Matching Scenario: The Official scenario of the child will be used only when the child component exists but does not have a scenario that matches the assembly.

• Never: A new scenario matching the assembly scenario will be created and rolled into the assembly.

The default is Never.

Note: If you used the older "true/false" preference in a version prior to 2015 R1, you must re-select this option since this preference now has three states. If you have never used this preference before, you should review your current Catalog Parts workflows with your aPriori Account Team or aPriori Support to determine how best to leverage this functionality.