Explore records, Activity and Trace
Use individual-record exploration to answer a concrete question, such as which operations belong to a production order or where its output is currently placed.
Find and focus a record
- Select the intended site/environment and open Nexus.
- Choose Find a record. Search all supported records or select an object type first.
- Search using a known name, code or reference, then open a matching record.
- Check the central record's identity and current facts before exploring neighbors.
- Select a connected node to inspect it. Choose Explore this record to load that record's own map and context.
The finder shows up to 10 matches per type. Refine the query when you cannot see the intended record. Direct View in Nexus links use the persisted record identity and avoid ambiguity between similar order numbers.
Use navigation history or the visible path to return to an earlier focus. On smaller screens, List can be easier to inspect than the map. Zoom and fit controls affect presentation, not retrieved data.
Read connections accurately
The inspector groups available connections into Relationships, Events, Used by, Uses, Integrations and Actions. Expand the relevant group and read its directional label.
For a production order, inspect its operations and splits. Distinguish eligible work centers from saved assignments. Follow customer positions for demand and child orders for components. For a Material Object, inspect producing order/operation/split and current holder placement. Current placement does not reconstruct full assembly or transformation lineage.
Selecting a neighbor keeps the central record's Activity, Documents and Trace context. To see the neighbor's history, explicitly explore it as the new center. This prevents attributing the central order's activity to every selected node.
Details and documents
Details provides current accessible facts, their source and read/update timing where available. Open source or a named destination opens the authorized owning workflow. A link can fail if access or the source changed since retrieval.
Documents lists recorded document links for the focused record. It does not search every file for matching text. Open the linked source to inspect the document and its own permissions.
Activity
Activity shows retained events connected to the focused record. Use it to inspect observed changes and available run links. No displayed activity can mean absent source support, access restrictions, retention limits or no recorded event; it does not prove nothing happened.
A current status and a recorded historical event answer different questions. Neither a matching timestamp nor a current record relationship proves that an event caused another.
Trace
Trace follows explicit recorded cause/trigger/result links and authorized automation runs. Read each step's status and destination. A completed automation run is evidence of that run's recorded completion, not independent confirmation of every intended external effect.
The view is bounded: it follows up to three causal hops, 60 events and 20 automation runs. Missing preceding causes and unlinked events are reported; Nexus does not infer links from timestamps, shared correlation IDs or configured bindings. Use the source run/activity record when you need more evidence.
Coverage and recovery
Coverage explains available, partial and unavailable information. Retrieval limits, unsupported readers, missing identities and inaccessible sources can make the picture incomplete.
| Situation | What to do |
|---|---|
| No accessible records | Check type, search, site/environment and source access |
| Type structure available, records unsupported | Use the source application; record support is not supplied by merely defining the type |
| Matching records need identity setup | Ask the administrator to reconcile canonical identities; do not duplicate business records |
| Record unavailable | It may be removed, restricted or in another scope; open another record or the legitimate source |
| Context failed, map still available | Continue inspecting relationships or retry history/documents separately |
| View reached a limit | Explore a connected record to narrow focus and inspect Coverage |
| Source facts seem outdated | Inspect observation/read times and refresh the source/map |
For support, provide object type, record identifier, site/environment and the visible limitation/error. Do not interpret hidden records as zero activity or a complete count.
See order networks, Material Flow and configuration and sources.