VISUAL JOURNEY · A FICTIONAL REFUND
One refund.
Four ways to see it.
The records look right. The work still stops. Explore what each view reveals, then change one condition and see what happens.
Keep the example. Change the conditions.
Example conditions, not company policy. Other required checks are assumed to pass in this small demonstration.
Select a node below to explore its responsibility and first check. The text list provides the same information as the drawing.
WHAT CHANGED?
Take a better question to your team
A Product Owner could share the decision view with an admin to discuss where business approval should be checked. This is a suggested use, not an observed customer outcome.
How these views relate to ERD, BPMN and decision models
Records: an ERD describes entities and relationships. This conceptual view is not a Salesforce org schema and does not specify actual fields or cardinalities.
Process: BPMN provides a formal process notation. Our teaching flow shows work order; it is not a complete BPMN diagram.
Decisions: DMN models business decisions and rules alongside process models. This example is not executable or standards-conformant DMN.
Tekin Method vocabulary: decision topology means connections among decisions, evidence and responsible roles here. Control nodes mark checks; intervention points mark possible changes to investigate. Decision space means available options under the conditions. These teaching terms do not replace the standards.
Primary references: Salesforce ERD notation, OMG BPMN, OMG DMN.
No systems are inspected, no refund is issued and no policy is verified. This browser-only teaching model is not a validated Agentforce implementation. No PDF is needed to explore or share it.