Document · 1 / 6
Nexa is the interface; ECAP coordinates the work
The current ECAP application uses a React/Vite frontend served through Cloudflare Pages. Pages Functions handle edge routes and configured backend integrations. The earlier Issistant demonstrator and product-design brief are historical design inputs, not the deployed runtime specification.
- 01Nexa UI
- 02Pages Functions
- 03Configured backend
- 04ERP / services
Frontend
Forms, navigation, previews, contextual Help and AI-assisted interaction.
Backend boundary
Authorization, validation, durable state and governed external execution belong on the server.
Document · 2 / 6
Data follows company and environment
Carry the authorized company and release lane through reads, edits, linked records, messages and connector calls. Do not infer authorization from a visible link or client-side role alone.
Scoped records
Keep source documents, extracted values, approval history and sync results attached to the correct records.
Storage
Existing services use their configured storage; do not replace unavailable data with invented success or sample records.
Isolation
Avoid cross-environment credential or data fallback. Verify deployment isolation before making availability claims.
Document · 3 / 6
Keep financial execution behind explicit controls
For A/P, approval and posting are separate transitions. Server validation, permissions, decision history and connector results determine the outcome.
- 01Saved draft
- 02Validation
- 03Approval decision
- 04Explicit posting
SAP Business One
Use the configured Service Layer connection and company context. Handle actual error responses and ambiguous outcomes carefully.
Retry control
Check existing ERP references/results before retrying. Never fabricate a posting ID or assume HTTP success means business success.
Document · 4 / 6
Ground AI in the available evidence
Nexa can help find records, summarize the current context and suggest next actions. A useful answer identifies its source and limitations; connector failures remain visible.
Inputs
Authorized record data, company configuration and relevant supporting documents.
Controls
Preserve permissions, approval rules and explicit financial writes.
Outputs
Explain recommendations and allow the user to inspect the supporting record.
Document · 5 / 6
Release through the controlled environments
The active GitHub repository is David-at-GitHub/ECAP. Main builds through Cloudflare to Dev. Dev-to-Test and Test-to-Prod promotion remain owner-controlled; a query parameter alone is not proof of independent deployment.
- 01Scoped change
- 02Checks & review
- 03Merge → Dev
- 04Owner promotion
Evidence
Tie deployment proof to the exact merged commit and test the affected live behavior.
Availability
Preserve sessions and approved releases. Planned downtime requires explicit prior approval and an agreed window.
Document · 6 / 6
Maintain documentation with the product
These public walkthroughs and guide PDFs share a dated content source. In-app ? → Docs supplies the form-specific procedures. Public resources must load without a business-data session or a live ERP connection.
Embedded resources
Serve the bundled Learn documents directly; avoid page-to-page redirect loops and nested application shells.
Supportable links
Keep legacy aliases, direct-open actions and real PDF downloads available.
Verification
Check resource type, content revision, playback, keyboard operation and narrow layouts; record any unverified device behavior.
Illustrative guide · No live records or business actions. Play advances every 12 seconds.