Menyiapkan Studior ERP…
Menyiapkan Studior ERP…
Studior ERP keeps the in-app workflow as the source of truth: Pusat Kerja shows what each role should do next, project gates prevent out-of-sequence work, and notifications point users back to the owning ERP surface instead of creating parallel queues.
1. Schema and build: run Prisma validation, targeted specs for changed areas, and production build.
2. Pusat Kerja: login by role and confirm next actions, locked reasons, notification handoff, and direct action routes.
3. Phase 3: use PRJ-2026-009 for active production, material, QC, RAB Tukang, kasbon, actual cost, and dashboard margin checks.
4. Scheduling sandbox: use PRJ-2026-010 to test Timeline Canvas template loading, draft edit, review, and publish.
5. RAB Tukang: verify project finance, `/finance?tab=rab-tukang`, `/team-tukang`, Tim Tukang assignment, review result, approval, and payment summary.
6. Phase 4 closeout: use PRJ-2026-011 to check signed BAST, paid final settlement, active warranty, and Owner closure evidence.
7. After-sales: use PRJ-2026-012 and service tickets SR-2026-011/012/013 to test intake, assignment, warranty validation, resolution, and follow-up routing.
8. WhatsApp: start with `WHATSAPP_PROVIDER=DRY_RUN`, trigger reminder and delivery cron once, then inspect `/settings/notifications` before enabling a live provider.
If a page shows "Tahap Belum Tersedia" or a locked action, that is expected when workflow gates are not met. The UI should explain the missing gate, current step, and where the user should continue. For production readiness, keep WhatsApp in dry-run until queue behavior, provider metadata, and admin filters are verified.