The integration dashboard should tell the record’s story
An error count tells operations that something needs attention. A useful integration experience explains which business record is affected, what happened to it, and what can safely happen next.
An operations colleague rarely opens an integration dashboard just to admire the activity. There is usually a question to answer. For a hypothetical example, an account update has not appeared in the CRM. The dashboard shows several colored indicators and a count of failed messages. It confirms that something needs attention, but it does not yet answer the colleague’s question.
Which message belongs to this account? Did the update leave the ERP? Was it rejected, delayed, or processed without an acknowledgement? Is there a correction to make, or would trying again create another problem?
The gap lies between displaying system activity and explaining a business event. Recent GCG work on an ERP-to-CRM administration experience explored ways to close that distance through visual flows and record detail. The implementation was validated in a non-production environment.
Start with a record someone recognizes
Technical identifiers are necessary for tracing work across systems, but they are rarely the best starting point for a business user. A dashboard becomes more useful when it connects those identifiers to recognizable record labels and types.
For example, someone investigating an account should be able to identify the relevant account record before navigating into its processing detail. The internal reference remains available when a technical teammate needs it. The two forms of identification serve different moments in the investigation.
The non-production interface work included business record labels and access to record-level detail from the visual flow. That changes the purpose of the visualization. Instead of being a decorative representation of connected systems, it becomes an entry point into the work moving between them. The design question is whether a user can recognize the thing they are looking for and move directly toward an explanation.
Turn the flow into a sequence of evidence
A line between ERP and CRM describes an intended relationship. An operator investigating a particular record needs a more specific story: which steps were attempted, what happened at each step, and which facts are still unknown.
The detail view can connect a record to its relevant status, timing, and processing context. Where attempt history is available, it should distinguish the latest state from earlier events. A record that recovered after an interruption has a different story from one still waiting for an answer, even if both appeared in an error count earlier.
The interface should be careful with the meaning of visual states. A colored dot can invite inspection, but its label and detail need to explain what the color represents. ‘Sent’ should not imply ‘accepted by the destination’ unless the underlying evidence supports that conclusion. The most useful visual treatment makes the system’s knowledge clearer instead of making an uncertain process look finished.
Make investigation comfortable for real people
Integration tools are often used while someone is already handling an exception. Dense diagrams, tiny targets, and disappearing details add friction at the moment the user needs to concentrate on the business problem.
The recent interface work addressed practical interaction details alongside the visual presentation: record detail could be opened from flow elements, grouped records could be selected, and keyboard and close behavior were considered. These details matter because a flow may represent several records and several possible paths through the information.
Movement also needs a purpose. An animated flow can communicate activity, but it should not compete with a person reading record detail. Pausing replay while someone inspects information gives the investigation a stable surface. The broader principle is to treat the diagram as a working interface. Its labels, focus behavior, spacing, and detail panels deserve the same care as the operational data they present.
Find the business record inside the flow
Record journey
- Recognize the record
A generic business label is more useful to the reader than an isolated technical ID. - Open the context
The selected record stays connected to its type, route, and available evidence. - Choose an investigation
Inspect destination evidence before treating a sent record as a confirmed outcome.
Select the record, then inspect what is known
Account A is selected in the flow between ERP and CRM. The open drawer puts the record type, source, destination, and available evidence in one place. Its evidence says “Sent”, while the destination remains “Awaiting confirmation”. Read those labels together: sending the record has not yet established what the CRM did with it. “Inspect destination evidence” therefore makes sense as the next action. The drawing keeps a recognizable business record in view while the operator investigates its technical journey. That is what makes the diagram useful beyond showing that two systems are connected.
Put a decision at the end of the story
Visibility is valuable when it helps the operator decide what to do next. Sometimes the correct action is to wait for a known pending step. Sometimes a business value needs correction. Sometimes the integration needs reconciliation before any request is repeated.
A recovery action should follow the permissions and rules of the underlying process. The interface should make its scope clear: which record will be affected, what the action requests, and what evidence will show the result. A prominent Retry button cannot compensate for an undefined retry policy. This is guidance for the wider operational design, rather than a claim that every recovery capability was part of the non-production implementation.
A useful review starts with a person’s question and ends with a supported decision. Follow one record from its recognizable label through the available evidence to its appropriate next step. When that path is coherent, the dashboard does more than report traffic. It helps the organization understand the work moving through its systems.
Images are original conceptual illustrations, not photographs of a client project.