These are illustrative scenarios showing how the products are used, not customer case studies.
The same sequence, twice
Today
- Event arrives
- Payload lacks the context
- Routed to a person
- Person looks it up
With SynaptaGrid
- Event arrives
- Step reads the record
- Condition picks the path
- Result written back
The situation
Whether to approve, escalate or route usually depends on something that is not in the event: the current status of the related record, whether the stock exists, what the customer is entitled to. A tool that cannot ask does the easy half and hands the rest to somebody’s inbox.
How it is approached
A step reads a record at the point of use, so a decision is made on the current state and not on the snapshot that started the run. That includes records that live in your own systems and never move here. Results are written back onto the record. Step inputs are mapped from the event, an earlier step’s output, the record, a fixed value or a computed one, and the mapping is compiled when the trigger is armed, so what runs is what was checked.
What changes
The process makes the decisions that depend on a lookup instead of stopping at them. The record shows which state it is in and the history of every run that touched it.