PDXpert PLM Software
On-line Help Guide
This help topic describes the current PDXpert PLM release. Earlier releases may be different. To view your release's version of this topic, open PDXpert and press the F1 key or select the Help menu.
A change form's Affected tab lists those items that are impacted by the release of the change.
When an implementing change is approved and released, the listed items are released or canceled, and child items listed on their parents' Markup tabs are added on or taken off the lists. With a non-implementing change (or informational change), the status of items shown on the Affected tab is not altered as a result of the change form being approved and released.
Limit the number of items on the Affected list. It's easier to verify that your list is accurate, and reviewers are more careful checking a tightly-focused set of items.
How items are automatically added—
Add an item to the change form by dragging it from the Item Explorer, and dropping it into the Affected list.
When you add an item to the Affected list of a non-implementing change, PDXpert does not add any other items automatically.
When you add an item to the Affected list of an implementing change, PDXpert looks at the item's BOM, References and Sources lists to decide what other items should be automatically added:
If you add a parent item that has a BOM, source or reference child item with a pending iteration, then that child is automatically added to the Affected list. You can manually remove any released child with a pending iteration from the Affected list.
PDXpert then examines all child items that it has automatically added to the Affected list. If the child item has a BOM, source or reference child item (a "grandchild") that has never been released, then that grandchild item is automatically added to the Affected list. This process is repeated for each lower level until all automatically-added items have been examined, and all never-released items have been added.
You must explicitly agree to include lower-level pending iterations that are not visible on the parent you add. That is, you must manually add to the Affected list any previously-released grandchild with a pending iteration.
Before routing the change for approval, you should always review the Affected list to verify that PDXpert is doing what you intend.
An item already on a change form should be re-dropped onto the Affected list each time you modify the item's BOM, References or Sources lists.
Conflicts may arise when a child item (a) is already listed on another change form, (b) has no pending or released iteration available, (c) is currently being edited, or (d) has been revised after the parent item has been added to the change form. To resolve these conflicts, fix the underlying problem and then re-drop the parent item onto the Affected list to correctly add the child item's iteration.
The most efficient way to ensure your intended changes get onto a change form's Affected list is to work from the bottom of your revised product structure to the top. That is, add each higher level revised item onto the change only after you've added all lower-level iterations.
There may be times when a previously-released item has an incomplete pending iteration, and you don't want it added automatically to any change forms. In this case, create a separate implementing change and add the item to the Affected list. When its parent items are later added to other change forms, the pending iteration is already on a change form and therefore unavailable for automatic inclusion.
Affected list content—
If you have a preferred sorting order for the affected items, you can sort the list using the appropriate context menu command (for example,), and then select the menu item to lock-in the order. (Line numbers cannot be edited after the change has been routed.)
A part or document can be dragged from the Affected list to any other location that accepts the item. Only one item at a time can be selected and dragged.
If permitted by the change form definition, you can add dispositioning information to an affected item by selecting Add Disposition Cost from the item iteration's context menu.
- The dispositioning action or classification.
- The location of the items to be dispositioned (as of the date shown in the Quantity).
- Recurring activity—
- Mark this checkbox if the activity represents an expense for all future items, such as a per-unit licensing fee or tooling amortization cost.
- The number of items to be dispositioned, their units, and the date of the item count.
- Unit cost—
- The unit cost for each item to be handled in accordance with the disposition instructions at the specified location.
- Subtotal cost—
- The total cost for the current dispositioning activity is calculated by multiplying the quantity by the unit cost.
- Assigned to—
- You can assign the activity to a particular person, who can then view the assignment in the Tasks tab of the Item Explorer.
- Target completion—
- Specify the date when the dispositioning activity should be done.
- Actual completion—
- The assigned person can update this (as well as the quantity and unit costs fields) after the change form has been released to indicate when the actual dispositioning activity was completed.
- Instructions for performing the dispositioning activity.
Help Guide Contents [PDF]
- 0001. Welcome!
- 0002. Help conventions
- 0100. PDXpert Application Server
- 0101. Server overview
- 0200. How to...
- 0300. Console reference
- 0400. How to start the PDXpert client
- 0500. Program concepts
- 0600. How to set up PDXpert
- 0700. How to use the Item Explorer
- 0800. How to use the Collection Explorer
- 0900. How to work with documents
- 0901. Manage documents
- 1000. How to start a document
- 1003. Fill in the new document
- 1004. Add or remove references
- 1005. Save your document
- 1006. Remove your document
- 1007. Release your document
- 1008. Manage a released document
- 1009. Revise a released document
- 1010. Cancel a released document
- 1100. How to work with parts
- 1101. Manage parts
- 1200. How to start a part
- 1203. Fill in the new part
- 1204. Add, modify or remove BOM parts
- 1205. Import a CAD BOM
- 1206. Add or remove approved sources
- 1207. Add or remove references
- 1208. Save your part
- 1209. Remove your part
- 1210. Release your part
- 1211. Revise a released part
- 1212. Manage a released part
- 1213. Cancel a released part
- 1300. How to revise multiple markups
- 1400. How to work with change forms
- 1401. Processing a change
- 1402. Originate a new change form
- 1403. Analyze a submitted change
- 1404. Fix change processing errors
- 1405. Remove your change form
- 1406. Review a routed change
- 1407. Resolve an on-hold change
- 1408. Analyze an accepted change
- 1409. Use a released change
- 1410. View a completed change
- 1411. Analyze a stopped change
- 1412. View a rejected change
- 1413. Remove a canceled change
- 1414. Return a submitted change
- 1500. How to work with file attachments
- 1600. How to report, import & export
- 1601. Create a report
- 1602. Export a PDX package
- 1603. Use the Report/Export Wizard
- 1700. Import & update items
- 1701. Initialize your PLM database
- 1702. Use the External Data Importer
- 1703. Item Master import
- 1704. Iteration-level relational imports
- 1705. Bill of materials import
- 1706. References import
- 1707. Revision files import
- 1708. Sources import
- 1709. Item-level relational imports
- 1710. Item files & links import
- 1711. Materials import
- 1712. Groups collection import
- 1713. Materials collection import
- 1714. Organizations collection import
- 1715. Persons collection import
- 1716. Custom collection import
- 1800. View & export via ODBC
- 1801. View database objects
- 1802. Create an ODBC connection
- 1803. ItemViews reference
- 1804. ReferencePairViews reference
- 1805. SourcePairViews reference
- 1806. SourceItemMasterView reference
- 1807. StructurePairViews reference
- 1808. ChangeViews reference
- 1809. ChangePairViews reference
- 1810. FilePairMasterView reference
- 1900. How to perform other tasks
- 2000. Menu reference
- 2100. Item Explorer reference
- 2200. Document window reference
- 2300. Part window reference
- 2400. Change Form window reference
- 2500. System Rules reference
- 2501. System Rules window
- 2502. General: Copy files to snapshot
- 2503. General: Item uniqueness definition
- 2504. General: Reviewer's comment required
- 2505. Default File Access
- 2506. Password Policy
- 2507. References Tabs
- 2508. BOM: Allow duplicate parts
- 2509. BOM: Lock part default unit of measure
- 2510. BOM: Allow partner parts
- 2600. Collections reference
- 2601. Managing collections
- 2602. Custom attributes
- 2700. Places/Organizations/Persons
- 2800. General
- 2900. Documents
- 3000. Parts
- 3100. Changes
- 3108. Custom collections
- 3200. Other reference topics
- 3300. Software licenses & legal notices