Design evidence
The industry practice and in-repository evidence behind how prompts behave: clickwrap enforceability, survey frequency capping, and the defects fixed during the move.
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 7 of 478 synchronized guides.
The industry practice and in-repository evidence behind how prompts behave: clickwrap enforceability, survey frequency capping, and the defects fixed during the move.
Permissions, audience targeting, when prompts are deliberately suppressed, the audit trail, and where survey data physically lives in a multi-tenant install.
Write prompts people actually answer, choose when to bump a survey version, read the response ledger, and keep optional surveys from turning into nagging.
Answers for when the tab is missing, a published survey is not prompting anyone, the Agree button stays greyed out, or mobile rating submissions start failing.
Switch Surveys on, run its migrations, grant the right permissions, and publish your first optional survey and required consent prompt step by step.
Every page, form field, question type, database table, route and API endpoint the Surveys module ships, with the CLI commands used to manage it.
What the Surveys module does, who it is for, and how optional feedback prompts differ from required consent walls. Start here before setting one up.