Integrations: connecting systems with explicit direction and evidence

An integration exchanges information between systems. Its design should identify which system is authoritative for each value, what event starts the exchange and how failures are resolved. A connection name alone does not define these responsibilities.

Inbound access allows another system to interact with the ERP. Outbound events inform another system about activity. These directions have different credentials, controls and operational evidence.

DNA's integration components

DNA's integration setup includes connection definitions, scoped API-key requests, webhook endpoints, event topics, field mappings and delivery logs. A connection can be created before an optional key or webhook succeeds. The wizard reports those partial outcomes separately.

Field mappings associate source and target fields. The reviewed save flow removes incomplete mapping rows before submission. Saving the remaining mapping does not prove that every intended field was mapped or that a complete business transaction has passed through the integration.

Keys and events

API-key controls include creation, rotation and revocation requests. Webhook controls include endpoint configuration, subscribed topics, enablement, signing-secret rotation and test-event requests. These operations need coordinated ownership between the ERP and the receiving or calling system.

A test event checks a particular exchange. It does not prove that every production event, mapping and business exception works. Verify the receiving system's result as well as the ERP-side response.

Delivery and replay

DNA's delivery log supports inspecting attempted deliveries and requesting replay. Re-queuing is not the same as successful processing by the destination. In the reviewed bulk replay flow, individual replay results are not assessed before the summary message, so each relevant delivery should be checked after a bulk request.

Before replaying, understand whether the destination can recognise repeated events. The lesson does not assume automatic duplicate prevention. A reliable integration has clear ownership, explicit mappings, monitored outcomes and a recovery process that preserves business correctness.