706 - From submission to action

• 701An automation that answers a requestWhat an endpoint is, the request a handler is handed and the answer it returns, who binds it, the limits a request runs under, and what a caller is told.
• 702A lookup a partner system callsThe three access modes, API keys and per-caller limits, one audit row per request, refusals by reason, signed tokens, and the Endpoints page.
• 703Your first formA form the agent writes: fields, live choices, field-by-field refusals, the checks the platform runs first, the hosted page, and submissions as a table.
• 704Putting the form on your site, or in a reportEmbedding in an asset and on an allowed site, named bot checks, the honeypot, and the minimum fill time.
• 705Sensitive fieldsEncryption before storage, who reads in clear and where, audited reads, exports, and why a file field cannot be sensitive.
• 706From submission to actionAn automation that runs once per submission, validation against live data, bursts and failures, and writes to other systems.
• 707Capstone: the supplier form end to endThe demo tenant’s supplier program assembled: form, page, table, intake automation, and a report joining applications to the warehouse.

def intake(event):
    """Checks one supplier application against the warehouse and posts it to the operations feed."""
    values = event["payload"]["values"]
    store = platform.query(
        "SELECT s.store_name, s.city, s.state, s.manager_name, r.region_name FROM warehouse.public.stores s " +
        "JOIN warehouse.public.regions r ON r.region_id = s.region_id WHERE s.store_id = :id",
        params = {"id": int(values["pilot_store"])}, connection = "acme",
    )["rows"][0]
    category = platform.query(
        "SELECT c.category_name, count(p.product_id) AS products FROM warehouse.public.categories c " +
        "LEFT JOIN warehouse.public.products p ON p.category_id = c.category_id " +
        "WHERE c.category_id = :id GROUP BY c.category_name",
        params = {"id": int(values["category"])}, connection = "acme",
    )["rows"][0]
    platform.notify(
        channel = "ops-events",
        title = "Supplier application: " + values["company_name"],
        body = ...,  # company, category and products carried, contact, pilot store and manager,
                     # volume, first delivery, files attached, "Tax ID: received, encrypted"
        data = {"kind": "supplier_application", "event_id": event["id"], ...},
    )

def main():
    """Handles the supplier application this event run was made for."""
    if run.event == None:
        fail("acme-supplier-intake runs once per stored application; start it by submitting the supplier-onboarding form")
    platform.result(intake(run.event))

→ manage_script
  { "command": "update", "name": "acme-supplier-intake",
    "event_source": "form-supplier-onboarding", "exclusive": "queue" }

← { "status": "updated", "version": 1,
    "message": "Saved, and this version is what runs now ..." }

id

The stored event’s id, the one the run is made once for.

type, key

form_submission, and the submitter’s address on a form that requires sign-in.

received_at

When the source received it.

source

form-supplier-onboarding.

payload

The submission: values (sensitive ones as ciphertext, files described), the fields in order, and the submitter.

→ manage_script get_run   acme-supplier-intake

← { "trigger": "event",
    "event_source": "form-supplier-onboarding",
    "event_id": "345829bdb1f4a944cf0d3eff46783698",
    "status": "succeeded", "duration_ms": 431, "queries": 2,
    "result": { "company": "Northfield Paper Goods",
                "category": "Paper Products", "region": "Southwest" },
    "log": "notify: send to ops-events: accepted for delivery" }

  what the operations feed received
  title  Supplier application: Northfield Paper Goods
  body   **Northfield Paper Goods** applied to supply **Paper Products**
         (207 products in the category today).
         - Contact: Grace Okafor, [email protected]
         - Pilot store: ACME Store #254, Fairview, TX (Southwest; manager Elizabeth Garcia)
         - Expected annual volume: $350000
         - Certificate of insurance: 1 file attached
         - Tax ID: received, encrypted
  link   the run's page in the portal

applications stored, 37 event runs

37

runs failed

0

pending in the queue

0

pending runs the queue holds before skipping

100

1. 1

   One event, one run

   A run is made once per automation, source, and event id. A second server noticing the same submission makes no second run.

2. 2

   Never inside the person’s request

   The run is queued when the submission is stored and executes afterward, so a slow or failing automation never slows the form or loses a submission.

3. 3

   A failure alerts and is not replayed

   A failed run is recorded with its cause and its owner is told. The platform does not run it again on its own, and the next submission still runs.

4. 4

   A burst is bounded

   An automation holds at most 100 pending event runs. A submission past that is recorded as skipped, with a reason saying it is still in the source, and the Events section counts skips for seven days.

5. 5

   One at a time when asked

   An automation set to run one at a time runs its event runs in the order they arrived; an event run waits rather than being refused.

def already_applied(company):
    """Reports whether an application from this company is already stored."""
    rows = platform.query(
        "SELECT count(*) AS n FROM scratch.uploads.webhook_form_supplier_onboarding " +
        "WHERE lower(trim(json_extract_scalar(payload, '$.values.company_name'))) = lower(trim(:company))",
        params = {"company": company}, connection = "acme",
    )
    return rows["rows"][0]["n"] > 0

def form_submit(req, values):
    errors = {}
    ...
    if already_applied(values["company_name"]):
        errors["company_name"] = "An application from this company is already with the vendor team. " +
                                 "Reply to its confirmation instead of applying again."
    if errors:
        return {"errors": errors}
    return None

form_submit

before storing

Checks that decide whether the submission is acceptable at all, answered to the person on the page: a malformed value, a repeat, a store that is not taking suppliers. Keep them quick; the person is waiting.

the event run

after storing

Everything that acts on an accepted submission: a post to a channel, a lookup that enriches it, a write to the CRM or the ERP through an API connection. A slow or unavailable system delays the run, never the person.