Configuration and connected sources
The configuration map explains how saved object types, integrations, mappings, actions, events, Apps, automations and recipes connect. It is useful when designing a workflow or investigating which configuration supplies a record.
Inspect the configuration
- Open Types & configuration in Nexus.
- Choose whether to include configuration or show object types only.
- Select a type or configuration item and inspect its fields and grouped connections.
- Follow a connected item or focus/expand its neighborhood to examine its use.
- Use the named definition/editor/configuration destination for the change you intend.
Use search and category filters to reduce the visible map. Show everything returns to the accessible configuration overview. A display-limit message means additional configuration may exist beyond this map.
Arrows describe recorded setup: an App uses a type, an integration provides objects, a mapping maps between them, or an event triggers a configured workflow. They do not prove a particular record was imported or an automation executed.
Build models in their existing editors
Nexus derives its map from authoritative configuration; drawing or dragging cards does not define manufacturing relationships. Use Operations Studio to configure materials/BoMs, work centers, routings/recipes, Apps and automations. Use the object definition/configuration destination when your accessible Factory Model type provides it.
Follow each editor's save, publish or apply workflow. A saved draft and a published operational definition are different states. Refresh Nexus after the change and verify the resulting saved reference. Creating a definition alone does not add an individual-record reader, authorize actions or import external data.
Source and Ennea values
On an individual record, Connected sources can show external identity, observation time, freshness and field behavior. Compare Source with Ennea rather than assuming they must always match.
| Field behavior | Interpretation |
|---|---|
| Controlled by the source | External authority determines the field according to its published mapping |
| Copied on import | The source supplied the imported value; this is not continuous synchronization |
| Managed in Ennea | Ennea owns the operational value |
| Calculated by a recipe | A configured calculation supplies the result |
A field may state that it refreshes when source data changes. This describes configured behavior, not proof that a remote source is reachable now. “Older source observation” or unavailable information needs reconciliation with the integration owner.
Connected actions
Source context can list connected actions and their current preview readiness. A listed action is not an executed write. Konnie checks current permission and required approval before sending through the configured action workflow.
Ambiguous identity or missing source authority blocks action readiness. A completion report can require a completed order with produced quantity. Resolve the displayed condition in the owning source/configuration before asking for another preview; a model answer cannot supply missing authority.
Troubleshooting
If an App or automation connection is missing, inspect its saved references and publication state in the editor. If an integration is disabled or setup is required, complete its secure setup and test in Integrations. A draft connection does not establish network access or send external records.
If counts differ from another screen, check map filters, scope, access and truncation. Configuration counts and operational record counts measure different things. When source values differ, preserve the recorded observation and review field authority before manually changing a business record.
See ERP and API integration, automations, publishing and governance and approvals.