In the fast-paced world of business, operational hiccups, like late shipments, low stock, or missing paperwork, are inevitable. The challenge isn’t preventing them entirely, but catching and resolving them before they escalate into costly problems. This is where a real-time Exception Desk becomes an invaluable asset, transforming your FileMaker solution from a simple system of record into an active watchdog for your live data. By surfacing issues as they happen and guiding the right person to a swift resolution, an Exception Desk shortens the feedback loop, reduces surprises, and brings clarity and accountability to your order and inventory management.
What It Is
A lightweight Exception Desk watches your live data and flags issues as they occur. Late ship dates, stockouts, duplicate POs, missing documents, or out-of-range values are surfaced automatically in a clean dashboard. Each exception opens a small, guided workspace where the right person can acknowledge, assign, and resolve it.
Why It Matters
Most teams discover issues too late, often at the end of the day or week, when options are limited and context is lost. A real-time Exception Desk shortens the feedback loop.
- Faster recovery with fewer surprises
- Less email and spreadsheet back-and-forth
- A clear audit trail of what happened, when, and who handled it, useful for stand-ups or customer conversations
How it Works (Conceptual Overview)
At a high level, the Exception Desk separates three concerns:
- FileMaker acts as the system of record. It evaluates rules, creates exception records, and tracks status and ownership.
- Claris Connect handles event-driven actions. When something important happens, it routes notifications, creates tickets, or contacts vendors.
- Claris Studio provides a lightweight browser-based interface so occasional users can acknowledge or resolve exceptions without needing a FileMaker license.
This keeps core logic and data in FileMaker, while extending reach to the browser and other systems only where it adds value.
What’s Under the Hood (Simple Anatomy)
- Rules stored as JSON in a Settings table, editable without schema changes
- A combination of event-driven checks on record edits and a nightly baseline scan
- An Exceptions log table with fields such as Type, Source Record ID, Status (Open, Assigned, Resolved), Owner, Notes, and Timestamp
- A Studio form linked to the Exception ID for quick acknowledgement and resolution
- One or more Connect flows that react to new or updated exceptions
Overview: A Simple End-to-End Example
To make this concrete, here is one realistic slice of the Exception Desk: a Stockout exception that is detected in FileMaker, routed through Claris Connect, and acknowledged in Claris Studio.
In this example:
- FileMaker evaluates inventory levels and creates an Exception record when stock falls below a threshold.
- Claris Connect reacts when that Exception becomes Open and sends a notification to Teams or Slack, optionally creating a ticket or emailing a vendor.
- Claris Studio provides a small form where an operations user can acknowledge or assign the exception, writing directly back to FileMaker.
The examples below show the minimum touchpoints for this flow. They are not a complete solution, but they illustrate where each piece of logic lives and how the components connect.
Connect Example (High Level)
Flow: New Open Exception (Stockout)
- Trigger: When an Exception record is created or when Status changes to Open (via Data API or webhook).
- Filter: Type equals Stockout and Status equals Open.
- Actions: Post to Teams or Slack with a link back to the Exception, optionally create a ticket, then write back notification details to the Exception record.
Example Touchpoints (Sample Code to Adapt)
Note on sample code
These examples are illustrative. Update layout names, table occurrences, field names, and privileges to match your solution. Always check Get ( LastError ) and review results with JSONFormatElements ( $$result ) while testing.
A) FileMaker script fragment: evaluate a rule and open an Exception
Example: Stockout rule
If [ $QuantityOnHand < $MinStock ]
New Record/Request [ Table: Exceptions ]
Set Field [ Exceptions::Type ; “Stockout” ]
Set Field [ Exceptions::SourceTable ; “Items” ]
Set Field [ Exceptions::SourceID ; $ItemID ]
Set Field [ Exceptions::Status ; “Open” ]
Set Field [ Exceptions::Notes ; “Quantity on hand below minimum stock level.” ]
Commit Records/Requests
End If
B) One-step update with the Data API: acknowledge or assign an Exception
Execute FileMaker Data API [ Select ; Target: $$result ;
JSONSetElement ( “{}” ;
[ “action” ; “update” ; JSONString ] ;
[ “layouts” ; “Exceptions_edapi” ; JSONString ] ;
[ “recordId” ; $ExceptionRecordID ; JSONString ] ;
[ “fieldData” ; “{ “Status”:”Assigned”, “Owner”:”Ops Desk” }” ; JSONObject ]
)
]
C) Simple JSON rule pattern stored in Settings
Settings::ExceptionRulesJSON example:
{
“rules”: [
{ “type”: “Stockout”, “expr”: “QuantityOnHand < MinStock” },
{ “type”: “LateShip”, “expr”: “ShipDate > PromiseDate” },
{ “type”: “DocMissing”, “expr”: “IsEmpty(COA_Received)” }
]
}
Your script can read this JSON, evaluate expressions, and create Exception records when conditions are met. Many teams start with hard-coded rules and move to JSON as the system matures.
Quick “Try It” Plan (2–3 Hours)
- Define three starter rules, for example, QuantityOnHand < MinStock, ShipDate > PromiseDate, or missing documentation.
- Create an Exceptions table with a simple list and form layout in FileMaker.
- Add a Studio form with Status, Notes, and Assign To.
- Wire one Connect flow to notify Teams or Slack when an Exception opens.
- Pilot with one product line or warehouse for two weeks.
Where It Fits
- Manufacturing and supply chain: stockouts, late suppliers, missing COAs or packing slips
- Service and field work: missed appointment confirmations, parts not staged
- Professional services: expiring SOWs, unapproved timesheets
- Healthcare and education: missing forms, past-due follow-ups
Conclusion
Real-time exception handling is less about automation for its own sake and more about timing and accountability. When FileMaker remains the system of record, and Connect and Studio extend it outward, teams can respond while context still exists and before small issues become larger problems.
Many teams like the idea of an Exception Desk but prefer help designing and implementing it cleanly. If that’s you, Kyo Logic can help you scope and build this pattern around your existing FileMaker system.
