| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 3244 |
| Technical Name |
process_guide_engine |
| License | OPL-1 |
| Website | https://odiflux.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 3244 |
| Technical Name |
process_guide_engine |
| License | OPL-1 |
| Website | https://odiflux.com |
Process Guide Engine
In‑app guided tours and a contextual Help side panel for SOPs. Train your users inside Odoo — no videos, no PDFs, no context switching.
Why Choose This Module?
One unified enablement suite that covers authoring, delivery, and on-screen reference material — for Community and Enterprise.
|
🧭
Visual Step CaptureClick the real button, field, or menu — the Step Builder records a stable selector automatically. No CSS hunting, no code. |
🕚
Systray LauncherA compass icon in the systray surfaces every tour that matches the current screen. Tours can also auto-start for first-time users. |
💭
SOP Help CenterA docked Help tab opens a slide‑in panel with the right Standard Operating Procedure for every model and view type. |
|
🔗
SOP ↔ Tour LinkingLink an SOP to a tour; users press Play tour straight from the Help panel to run the guided walkthrough on the same screen. |
📊
Progress TrackingPer-user, per-company progress records: current step, completed, skipped, plus start and finish timestamps. |
🔒
Scoped & SecureRestrict tours and SOPs by model, view type, module, company, or user group. Three ready-made security roles. |
Requirements
No Python packages. No external API. No cloud dependency.
base, web, and mail. Works on Community & Enterprise. No licensing impact.
How It Works
Four actions cover every rollout: author the tour, capture its steps, publish with rules, run on the real screen.
|
✏️
AuthorCreate a tour, pick a model & view scope. |
🧭
CaptureOpen Step Builder, click each control on the live screen. |
📱
PublishSet companies & groups, publish; it's live immediately. |
▶️
RunUsers launch from the systray or a tour auto-starts. |
Step 1
Author Your TourIn the Process Guides app, create a tour. Choose its scope (model + view type, or entire module), the start mode (manual, automatic, or both), plus optional company and group restrictions. Kanban by Draft, Published, and Archived keeps your catalogue organized. |
|
|
Step 2
Capture Steps VisuallyPress Open Step Builder, then click the real controls on a live screen. Each hover outlines its target in green; each click records a step with a stable selector, title, and tooltip position. Esc or F9 pause capture; Finish returns to the tour form. |
Step 3
Users Launch In One ClickA compass icon in the systray lists every published tour that matches the current screen. Alternatively, an Automatic start mode runs the tour on first visit. A step counter (e.g. 1 / 7) and Previous / Next / Skip controls put the user in charge. |
|
Help Center & SOPs
Tours are best when users need to do. Sometimes they need to read — the rules, the checklist, the reference. The Help Center puts the right SOP on every backend screen, and can launch a linked tour on the same page.
Step 4
The Docked Help TabA vertical Help tab is docked on the right edge of every backend screen — Quotations list, Sales Order form, custom dashboards. One click slides in the Help Center panel filtered to SOPs that match the current model, view, company, and user group. |
|
|
Step 5
Read & Run — Same PanelThe panel shows each matching SOP with its one-line summary and an Includes guided tour tag when a tour is linked. Click a row to read the full HTML body; press Play tour in the footer to launch the linked walkthrough on the same screen. Close with ×. |
Step 6
Author SOPs In OdooManagers open Process Guides → SOPs → New. Set Target Model, View Type, Companies, Allowed Groups, Priority, and optionally a Linked Tour. Author the body in the Odoo rich‑HTML editor — images, headings, links, all stored in the database. |
|
Admin Configuration
Three security roles, per-record targeting, and built-in per-user progress rows.
|
1
3 Security RolesUser (runs), Manager (authors), Admin (user-form shortcut). |
2
TargetingScope by model + view type, by module, or globally. Company + group filters. |
3
Progress RowsPer-user, per-company completion state, current step, and timestamps. |
4
LifecycleDraft → Published → Archived for both tours and SOPs, with validation. |
Built For Production
|
⚡
Database-AuthoredTours and SOPs live as Odoo records — versionable, exportable, migratable. No static files, no re-deploys. |
🔑
Record-Rule AwareEvery tour and SOP respects Odoo's multi-company and group rules — users only see what they're allowed to. |
📅
Sample Content IncludedShips with an example tour and three SOPs (global, Tour, SOP) so your team sees the flow immediately after install. |
Technical Information
|
Odoo Version
19.0
|
License
LGPL-3
|
Category
Productivity
|
Dependencies
base, web, mail
|
pip install, no external API. Community & Enterprise compatible.
Need Help or Customization?
Odiflux is here to help with SOP templates, tour authoring workshops, and any custom enablement requirements.
Visit odiflux.com →Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module