Settings & Configuration

General Settings Panel

The General Settings panel is the central configuration hub for Quickenerp. Every global setting – from company details to module-specific toggles – is managed here.

Navigation

Go to Settings > General Settings. This opens a single long form page organised into collapsible sections by module.

How Settings Are Organised

The page is divided into sections. Each section corresponds to a module and contains relevant toggles, dropdowns, and fields:

Working with Settings

• Toggles – Click a toggle switch to enable/disable a feature. Changes are saved immediately.
• Dropdowns – Select a value from a predefined list. Some are dependent on other settings (e.g. "Default Tax" only appears if a fiscal position is selected).
• Text/Number Fields – Enter values directly. Some fields require a page reload after saving for the change to take effect.
• Related Settings Links – Some settings have a "Configure" link that opens a separate configuration page (e.g. "Chart of Accounts" – "Configure" opens the full chart of accounts list).

Recent Settings Improvements

• Search Settings – Use the search bar at the top of General Settings to find any setting instantly. Type "currency", "tax", "email", etc.
• Settings Visibility – Only settings for installed modules appear. If a module is not installed, its settings section is hidden, keeping the page clean.
• Company-Specific Settings – In multi-company setups, settings can be configured per company. The settings page shows a company selector at the top if you have access to multiple companies.
• Auto-Save – Most settings save automatically when you change them. A green "Saved" indicator briefly appears at the top of the page. Some critical settings still require an explicit Save button.

Settings vs Configuration Menus

Not all settings are in General Settings. Module-specific configuration is often in the module's own Configuration menu:

• General Settings – Global toggles and high-level defaults.
• Module – Configuration – Specific records (e.g. Sales – Configuration – Price Lists, Sales Teams, Shipping Methods).
• Technical Menu (Developer Mode) – Low-level system settings (Scheduled Actions, Automated Actions, System Parameters).

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:

1. 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.
2. URL Parameter: Add ?debug=1 to any URL. Example: https://quickenerp.com/web?debug=1. This enables developer mode for your session.
3. Developer Tools (Assets): Add ?debug=assets to 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:

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).

Scheduled Actions

Scheduled actions (also called cron jobs) run automated tasks on a repeating schedule. They handle periodic maintenance, data processing, and automated communications.

Navigation

Go to Settings > Technical > Scheduled Actions (developer mode required).

Important System Scheduled Actions

Creating a Custom Scheduled Action

1. Click Create.
2. Name – e.g. "Daily Sales Summary Email".
3. Model – The model the action works on (most system actions use ir.actions.server).
4. Execution Frequency:

• Number of Calls – Run a fixed number of times, then stop.
• Do Not Repeat – Run once.
• Repeat Every – Run on a recurring schedule. Specify interval (Minutes, Hours, Days, Weeks, Months).

Cron Monitoring

The list view of scheduled actions shows:

• Status – "Done", "Running", or "Failed". Red background indicates a failure.
• Last Execution – Timestamp of the last run.
• Next Execution – When the next run is scheduled.
• Progress – For long-running crons, shows progress information.

If a cron fails, click the failed status to see the error details in the server logs. Common causes: Python errors in the action, unavailable network resources, or database locks.

Best Practices

• Schedule heavy operations during off-peak hours (e.g. 2:00 AM).
• Avoid running crons too frequently – a "Repeat Every 1 Minute" cron that takes 30 seconds may overlap with itself if it starts a second instance before the first finishes. Quickenerp prevents this by checking that the previous instance has completed before starting a new one.
• Test new crons by setting "Number of Calls" to 1 and a "Next Execution" of 2 minutes from now, then verify it runs correctly before making it recurring.