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 9 of 478 synchronized guides.
Diagnose a stuck Automation Center: nothing ever becomes due, a new type will not appear in the builder, everything moved to Needs review, a run says success but changed nothing — plus the glossary and what to capture before escalating.
The ERPat Automation Center lets administrators build scheduled rules that approve routine work automatically — with a preview before anything changes, an Observe mode that mutates nothing, and a reason code recorded against every single record.
Work the Automation Center day to day: the five tabs, the five-step builder wizard field by field, previewing against real records, publishing in Observe, promoting to Live, cloning, pausing, and reading a finished run.
How a module developer contributes a new automation type: the three files you ship, the declarative sidecar the registry collects, the handler and condition-provider contracts, the rule engine's allow-list, and the rule that every mutation must go through the owning module's own service.
Look up the Automation Center's three tenant tables and their columns, the two unique indexes that make runs idempotent, every route and its permission gate, the seven audit events, the helper functions, and the full module file map.
Switch the Automation Center on safely: confirm the cron runtime is ticking, run the migrations, verify the engine card, grant the ten permissions, and build a first automation that only observes until you trust it.
Who may let ERPat act on its own: the ten Automation Center permissions, why going live is a separate grant, how publisher authority is revalidated every tick and fails closed, the System actor that signs unattended approvals, cron scheduling, and the audit trail.
The verification record behind this guide: which source files were read, the milestone evidence including the byte-identical Observe inertness proof and the capped 25-of-120 live run, everything M4 and M5 have not shipped, the declared-but-unread config keys, and all ten named debt items with their owners.
What happens to your automation handler at run time: the eight-step lifecycle from cron tick to audit row, the executor-versus-handler ownership split, idempotency keys, chunk budgets and caps, resumable cursors, and how a run ends.