| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Field Service (industry_fsm)
• Timesheets (timesheet_grid) • Project (project) • Discuss (mail) • Employees (hr) |
| Lines of code | 410 |
| Technical Name |
manatec_fsm_coordination |
| License | OPL-1 |
| Website | https://www.manatec.de |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Field Service (industry_fsm)
• Timesheets (timesheet_grid) • Project (project) • Discuss (mail) • Employees (hr) |
| Lines of code | 410 |
| Technical Name |
manatec_fsm_coordination |
| License | OPL-1 |
| Website | https://www.manatec.de |
manaFSM: Field Service Management Coordination
Professional coordination of service dates with your customers.
This module extends Odoo Field Service (FSM) by adding a structured coordination of planned task dates with customers, including email templates with a confirmation link, token validation, and automated state logic. In many Field Service processes, the coordination for planned service dates happens manually via telefone or e-mail. This is prone to errors from the manual transmission, lacks documentation and is hampered by unclear feedback.
With manaFSM, scheduling as service task is extended to include a comprehensible and documented coordination.
Task Scheduling with manaFSM
Once a task has been scheduled in Odoo, you can send the customer an email with an individualized confirmation link.
This confirmation can:
- Be triggered directly from the Button in the E-Mail
- Happen via an external landing page
- Confirmed or rejected by the customer
The customer feedback is processed directly in Odoo, displayed prominently and documented in the chatter.
Automated Logic on Re-Scheduling
If a scheduled and coordinated service is changed later, if the shift in the scheduling exceeds a user-definable time interval, the coordination confirmation is reset automatically. This prevents a service date from being considered "confirmed" by the customer after such an extensive shift. The coordination has to be performed again, for a clean, transparent and documented process.
Safe Token Logic and Validation
The module uses hashed tokens to ensure the scheduling coordination is reliable, comprehensible and safe against unauthorized access. Each confirmation request has its own one-time use token for the individualized link, preventing both third-party access to the confirmation interface and ensuring that each confirmation link is only used once. If a customer attempts to re-use a link or uses a faulty token, they are redirected to landing pages communicating clearly why their request is invalid.
With this safety feature, scheduling confirmations can be relied upon during further planning. This prevents miscommunication and ensures that both customer and service teams can feel sure about the actual state of the service date as confirmed or rejected.
Company-Dependent Configuration
The coordination logic can be configured separately for each company in the Odoo system. This allows for separate processes with each company, tailored to their individual needs.
Changelog
- Initial Implementation
Contact & Support
Do you like this module?
Try out our other apps!
Challenges with this module, wishes for more functions or questions about Odoo? Contact us!
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