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 478 of 478 synchronized guides.
The routine operating manual for staff who run Kiosk day to day — the core screens, records, and workflows to use once setup is complete.
Answers to the most common setup, access, workflow, and support questions for the Kiosk module, with troubleshooting and support guidance.
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 guidance counselors and clinic staff in ERPat School: manage student-support cases, work the confidential child-protection/anti-bullying safeguarding surface (RA 7610/RA 10627), and handle restricted, audited learner health records.
Guide for the ERPat system administrator running the School module: enable it and run per-tenant migrations, grant and separate permissions, configure portals and the default grading policy, provision portal logins, and keep the module healthy across tenants.
Standalone ERPat Timeline module. Controller, model (Posts_model, table 'posts'), views, routes and menu are owned by this package and loaded through the HMVC compatibility layer. Slug 'timeline' matches the legacy module_timeline active-setting.
How administrators keep Tools Hub secure and reliable: permissions, menus, settings, public pages, API surfaces, migrations, and change management.
A compact reference of the screens, data records, routes, permissions, and supporting files that make up the Procurement module package.
Step-by-step SOPs for the Movements module: record and reverse employee movements, publish internal openings, run the candidate pipeline, and apply through the staff internal job portal.
Data and screen reference for the Movements module: all six database tables and their key columns, controllers and routes, cron jobs, system-log events, statuses, permissions, and the mobility policy rule engine.