WP Manifestindependent plugin directory
manifest / events / servsys-wordpress

ServSys

WordPress-based replacement for the ServSys field service management system

by Christopher Molnar · github.com/cmolnar65/servsys-wordpress

★ 0stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/cmolnar65/servsys-wordpress/archive/refs/heads/main.zip
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.
Readme github.com/cmolnar65/servsys-wordpress ↗

WordPress-based replacement for the legacy ServSys field service management system.

Development status

ServSys WordPress is under active development. The original Java ServSys repository remains the historical reference implementation; this repository is a new WordPress implementation and does not reproduce the legacy laptop/server synchronization architecture.

Current development target: v0.1.0

v0.1 planned scope

  • Customers and service sites
  • Equipment
  • Service calls
  • Service-call equipment relationships
  • Service charge lines
  • Completion codes
  • Follow-ups
  • Printable service report
  • WordPress roles and capabilities

Branches

  • main — protected release branch; merge only validated release-ready work.
  • develop — active integration branch for development.

Feature work should branch from develop and return to develop after testing.

Requirements

  • WordPress
  • PHP 7.4 or later
  • Composer 2 for development dependencies

Development

Install development dependencies:

composer install

Run PHP linting:

composer lint

Run unit tests:

composer test

GitHub Actions tests PHP 7.4 through PHP 8.5.

Architecture

ServSys uses custom relational WordPress tables for operational data and WordPress users, authentication, roles, capabilities, mail, media, and REST infrastructure.

Legacy synchronization fields and mechanisms such as servsync, laptop database replication, and server upload/download actions are intentionally not part of the new architecture. Modern offline/PWA support may be designed separately in a future release.

Phase 5 foundation

The current develop branch includes the first functional ServSys foundation:

  • Versioned database installation using the WordPress table prefix and dbDelta()
  • Customer, site, and customer-note tables with legacy migration identifiers
  • Customer and site repository/service layers
  • WordPress administrator capabilities for ServSys customer access
  • ServSys → Customers administration workspace with search, create/edit, activation state, multiple sites, and notes
  • Initial authenticated REST namespace at /servsys/v1/customers
  • Unit coverage for schema prefixing/relationships and capabilities

Equipment, service calls, inspections, agreements, pricing, legacy-data import, and offline synchronization remain outside Phase 5.

Phase 6 equipment management

The current develop branch extends the customer/site foundation with equipment management:

  • Upgrade-safe servsys_equipment table linked to both customer and site
  • Legacy equipment identifiers retained for future migration while obsolete servsync state is intentionally excluded
  • Equipment repository/service layer with customer/site ownership validation
  • ServSys → Equipment searchable administration workspace
  • Customer-site equipment tables with Add/Edit Equipment workflow
  • Equipment fields for type, brand, model, serial number, filter, refrigerant type, SEER, BTU output, notes, and active state
  • Equipment-specific WordPress capabilities
  • Unit coverage for equipment schema and capabilities

Service calls and service-call/equipment relationships remain outside Phase 6.