References Tabs (rule)

Before editing a system rule, ensure that no other users are using the system. After editing a system rule, close the PDXpert client and start it again.

Administrators open this using the Tools ➔ System Rules… menu.

Purpose §

Determines whether part and document records' References lists will accept child parts or documents.

Description §

True: Items of the specified class can be added onto the item's References list.

False: Items of the specified class can't be added onto the item's References list.

Data type §

True/False

Recommended or default value §

Parts §

If both checkboxes are cleared, then the References selection is not shown on part records.

References accept parts §

Default is True. Set as True to let part records reference other parts (for example, designed parts may identify tooling or fixtures).

A multi-level part relationship is normally shown as an assembly/components list on the BOM, not as References.

References accept documents §

Default is True. Set as True to part records reference documents (for example, assemblies may identify assembly instructions).

Documents §

If both checkboxes are cleared, then the References selection is not shown on document records.

References accept parts §

Default is False. Set as True if you let document records identify parts as references.

Because a document doesn't consume or otherwise rely on the existence of a part, this relationship is typically not allowed.

References accept documents §

Default is False. Set as True if you let document records identify other documents as references (for example, procedures may identify requirements).

Multi-level document references are not shown in standard reports or supported by the IPC-2570 "PDX" export standard.

Details §

Avoid cross-references where two records reference each other. You can easily discover a cross-relationship by looking at the referenced item's Appears On: References list.

Simplify the relationship by limiting which items can reference other items. Reference relationships should be single-level ("flat"), not multi-level ("deep"). Deep relationships require custom transforms to show, and cannot be exported in a PDX package.

2152