Yashas
1669bb755d
Two screens over Zino app 583:
Place a call — lead name, model, and the two numbers that matter: the
customer Aria dials, and the colleague the transfer bridges to. Submits the
Add Lead workflow activity as the signed-in user; the workflow's trigger
places the call server-side, so the zvk_ agent key never reaches the browser.
Live monitor — polls the leads record view every 3s. "Transferred to human"
is call_end_reason == handover, called out on its own because it is the thing
the demo exists to show.
src/api.ts deliberately bypasses two SDK methods; both are SDK bugs:
- workflows.startWorkflow() posts workflow_id, but core's StartRequest reads
workflow_uuid and rejects the call.
- views.getTabularView() does GET /view/recordview, the legacy unscoped route;
the app-scoped one is POST /app/{id}/view/recordview with the query in the
body.
Auth still goes through the SDK, so there is one token and one session.
Base URL is the root, not an app path: login is /usr/login while the app APIs
are under /app/583, so they sit at different depths.
Frontgen scaffold generated by the service's own ScaffoldReactProject, so the
build pipeline conventions (relative base, BASE_HREF placeholder, runtime
config.js) are byte-identical rather than reimplemented.
vite build + tsc -b both clean.
9 lines
420 B
Plaintext
9 lines
420 B
Plaintext
# Local development only (`npm run dev`). Reference for the values
|
|
# `npm run dev` reads from .env; nothing here is used by a deployed build.
|
|
#
|
|
# In a deployed environment these values come from config.js, which the server
|
|
# writes when it places the build. Do not commit environment-specific values —
|
|
# one build is promoted across environments unchanged.
|
|
VITE_ZINO_API_URL=http://localhost:8085
|
|
VITE_ZINO_MOCK=false
|