Use Knowledge Thread to investigate the connected information around an origin object. It presents objects and typed relationships as a graph so you can trace product context, inspect dependencies, and review supported impact analysis. The scope comes from the origin, traversal settings, included relationships, and data you can access.
Start an investigation
- Open Knowledge Thread and drag in the object you want to use as the origin.
- Confirm the origin’s identity and choose Explore to inspect its relationships.
- Review traversal direction, depth, and included relationship types before broadening the graph.
- Choose Network, 2D, or 3D to use the presentation that best fits the investigation.
- Select a node and inspect its object details and relationship context. Use graph navigation controls to keep the relevant connections in view.
Control what you are investigating
Direction determines which paths are followed from the origin. Depth limits how far the exploration travels. Begin with a small scope and increase it when you need additional context.
The scope navigator lists objects included in the loaded graph. Use Find an object to narrow that list and select a particular record. Graph details provides further information about the loaded network and the current selection.
Highlight and Filter serve different purposes. Highlight helps locate matches within the graph, while Filter narrows the visible graph using available type, lifecycle state, or attribute criteria. Review active filters before concluding that a connection is absent.
Review impact in Simulation
Switch to Simulation when you need the supported impact-analysis view for an appropriate change context. Review the origin, scope, and available simulation controls before interpreting the result.
Treat potential impact as a question to investigate against the connected evidence. A relationship can show a dependency without proving that the related object requires modification. Review the selected object’s details and the basis of any impact classification.
Exploring or simulating the graph does not itself approve a change or advance lifecycle states. Use the relevant object commands or Change Cockpit actions for managed updates. Relationship Manager provides a separate way to inspect and, when permitted, change connections.
Troubleshooting
If only the origin appears, check traversal direction, depth, and included relationships. An empty relationship selection can intentionally leave only the origin. Confirm that the expected connected objects are accessible.
If the view is crowded, reduce depth, narrow the included relationships, or use the scope navigator. If the result seems incomplete, clear graph filters and compare with the object’s actual relationships. Recheck the loaded scope before using the graph as evidence for a change decision.
Related articles
How to Use the Relationship Manager in Nora IPLM | Change Order
