This release introduces new API capabilities for external integrations, several usability improvements for work order management, and a fully restructured translation infrastructure. The updates aim to expand connectivity options for partners, improve daily workflows for office users, and lay a stronger foundation for multilingual support going forward. Below you will find an overview of the key changes included in this release.
New API Endpoints
A new set of API endpoints is now available, enabling external systems to retrieve data from PestScan via structured GET requests. Partners and integrators can now query lists of customers, employees, locations, work orders, visit types, and articles — with support for filtering by name, external ID, or PestScan ID. All endpoints support pagination, making it easier to handle large datasets efficiently.
Routes Always Visible in Setup
The Routes section under Setup > System is now always visible, regardless of whether the Planning module is enabled. Previously, this section was hidden unless Planning was active, which caused confusion for users setting up routes independently of that module.
Translation Infrastructure
A new translation system has been introduced under the hood. Translations are now managed via keyword-based lookups and loaded from file rather than a database table, improving performance and maintainability. This also enables faster release cycles for language updates going forward.
Bug Fixes
- Resolved an issue where the scheduler would run duplicate processes simultaneously.
- Fixed a bug preventing account managers from opening work orders.
- Corrected the employee dropdown on work order pages, which previously only listed technicians. All employees can now be selected as the primary assignee when creating or editing a work order — this applies to the fast creation page, the detailed creation page, and the work order edit page.
- Restored the missing print button for recommendations at location level.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article