Settings & Configuration
Completed
- Accessing General Settings
- Configuring Outgoing Email (SMTP)
- Access Groups, Record Rules & Security
- Language Management & Translations
- Automated Actions
- Developer Mode & Technical Menu
- Configuring Incoming Email (IMAP/POP)
- Scheduled Actions (Cron Jobs)
- Bundling Permissions Into Reusable Roles
- Email Templates
- System Parameters & Sequences
Developer Mode & Technical Menu
Developer Mode
Developer mode (also known as debug mode) unlocks advanced technical features that are hidden from regular users. It is essential for system administrators who need to customise forms, create automated rules, inspect system data, or configure security.
How to Enable Developer Mode
There are three ways to enable it:
- From Settings: Go to Settings > General Settings, scroll to the bottom of the page, and click Activate Developer Mode (wrench/spanner icon). The page reloads with developer features visible.
- URL Parameter: Add
?debug=1to any URL. Example:https://quickenerp.com/web?debug=1. This enables developer mode for your session. - Developer Tools (Assets): Add
?debug=assetsto enable developer mode with unminified JavaScript/CSS assets. This is useful for debugging UI issues but the page loads slower.
What Developer Mode Adds
1. Technical Menu
A new top-level Technical menu appears (in Settings or as a standalone menu). It contains:
| Menu Item | Purpose | Model (Technical Name) |
|---|---|---|
| System Parameters | Key-value configuration store. Override system behaviour without code changes. | ir.config_parameter |
| Scheduled Actions | Create and manage cron jobs for automated tasks. | ir.cron |
| Automated Actions | Define server-side rules that trigger on record changes (create/write/delete). | base.automation |
| Email Templates | Manage all system email templates – quotation, invoice, delivery, portal invitations. | mail.template |
| Views | Inspect and edit view definitions (form, list, kanban, graph, pivot, etc.). | ir.ui.view |
| Actions | Manage window actions, server actions, client actions, report actions. | ir.actions.* |
| Models | Inspect all database models, their fields, and relationships. Read-only view. | ir.model |
| Fields | View all field definitions across all models. | ir.model.fields |
| Security | Manage Access Control Lists (ACLs), Record Rules, Groups, and Security Policies. | ir.model.access etc. |
| Sequences & Identifiers | Manage numbering sequences and external identifiers (XML IDs). | ir.sequence, ir.model.data |
| Translations | View and edit translated terms. Export/import translation files. | ir.translation |
2. Edit View Option
On any form view, the Actions (gear) menu now includes Edit View. This opens the XML view definition, letting you:
- Add or rearrange fields in the form layout.
- Modify field attributes (readonly, required, invisible).
- Add custom buttons and logic.
- Changes apply immediately. No deployment or restart needed.
3. Field Tracking Configuration
Tracked fields show a history of changes in the chatter – who changed what and when. Enable tracking on any field from the field configuration in Technical – Fields.
4. Additional Context Menu Options
Right-clicking on many elements shows developer options:
- Inspect View – Shows the view architecture and technical IDs.
- View Metadata – Shows record metadata (External ID, model name, creation/modification details).
- Manage Fields – Opens the field configuration for the current model.
Caution
Developer mode gives access to settings that can break the system if misconfigured. Follow these rules:
- Only enable developer mode when you need to make technical changes.
- Disable it when you are done (click the "Deactivate Developer Mode" link at the bottom of General Settings).
- Never modify views or security rules unless you fully understand the implications.
- Take screenshots of default values before changing them.
- Test changes in a staging environment first (if available).
Commenting is not enabled on this course.