Learn how to use active ERPat modules through role-based instructions, standard operating procedures, field legends, standards, compliance reminders, and step-by-step workflows. Every guide is synchronized from the owning module and versioned whenever its instructions change.
Showing 395 of 395 synchronized guides.
Evidence gathered from the current Ticketing module files — controllers, models, configs, and migrations — before writing these user guide pages.
Guide for front-desk and gate-security staff in ERPat School: issue a visitor pass, check visitors in and out at the gate with each scan logged, and revoke a pass — the child-safety front line.
How grading works in ERPat School: the class record (section+subject+term), encoding Written Work / Performance Task / Quarterly Assessment, the config-driven engine that runs DepEd Order 8 s.2015 and MATATAG DO10 s.2024 side by side, transmutation and descriptors, and the draft→submitted→approved→released governance.
Guide for parents and guardians using the ERPat School parent portal: how to sign in, why you see only your verified children and only released grades, and how to read your child’s grades, attendance summary, and enrollment.
Guide for the principal or school head in ERPat School: approve and release quarter grades (a duty held separately from encoding), generate SF9 report cards, oversee enrollment and compliance, and review the audit trail of sensitive actions.
The evidence base for the ERPat School user guide: the live module files this documentation was written from — the module manifest, controllers, the grade engine and LIS validator libraries, config (permissions, menu, routes, system logs), and migrations — with what each proves.
How to stand up the ERPat School module: enable module_school, run per-tenant migrations, grant role permissions, seed the school year and sections, and take one learner from enrollment to a released report card.
A compact reference of the screens, data records, routes, permissions, and supporting files that make up the Sales module package.
A practical first-run checklist for enabling Sales, granting the right permissions, preparing your starter data, and training the first users.
Evidence gathered from the current Sales module files — controllers, models, configs, and migrations — before writing these user guide pages.