Customizing Product Family Matrix Editor
You can launch the Matrix Editor for the following Product Family objects:
• A single Product Family
• One or more managed variant specifications
• One or more variant baselines
The action to launch the Matrix Editor for the selected variant specifications or variant baselines, or both is available from the following areas:
• The Actions menu on the Variant Baseline information page and the Variant Specification information page
• Tables that display and allow you to select variant baselines and managed variant specifications
• The Folder Browser page
• The Advanced Search table
• The Baseline Objects table for a variant baseline
• The related Variant Specifications table for a part
If the Matrix Editor is launched with initial parts such as module variants, configurable modules, lower level parts (for example, from the folder browser), then a Path Filter is created for those parts.
Adding Support to Launch Matrix Editor
For information on how to customize actions, see
Action Framework for Windchill Client Architecture.
You can use the following actions to add launch points for the Matrix Editor:
|
Action Name
|
Action Type
|
Description
|
|
openInMatrixEditorRMB
|
productfamily
|
Action to use in the right mouse button that is a single-select location such as a right-click option in the Product Family Structure Browser.
|
|
openInMatrixEditor
|
productfamily
|
Action to use in a multi-select context such as a tool bar.
|
Passing in Parts to use as Path Filter to Launch Matrix Editor
You can customize the Launch Matrix Editor action by passing in parts that must be applied as path filter to the configurable structure. Paths to all occurrences of those parts must be defined within the path filter. To define the path filter, the configurable structure must be known. For this reason, the Matrix Editor must be launched with a pre-selected list of variant specifications (or all variant specifications of a variant baseline) when passing in parts.
Implementation Guidelines
1. Variant baseline, variant specification, or both, must be included in the selected items. If parts are included in the selected items list:
◦ Use the WhereUse mechanism to search the selected part from the configurable structure to create path based on the related variant specification and configurable module (root parent).
◦ Add path to path filter, then add it to the navigation criteria to process.
Configurable structure must display only the selected part with its skinny path.
2. Build the path from LaunchProductFamilyMatrixEditorTag.java, pass it to the Product Family Browser controller, and finally add it to navigation criteria.
3. Pass the selected parts and variant specifications and/or variant baseline to the Product Family Browser controller. The controller then processes them to find the path and builds path filter. Add it to the navigation criteria.