-
joelthomastrenser released this
2026-06-19 18:05:36 +05:30 | 0 commits to main since this releaseNew Features
Shared Memory DataStore
- Replaced the existing in-memory DataStore with a shared-memory implementation using Windows File Mapping.
- Added support for sharing application data between multiple running instances.
- Created separate mappings for users, notifications, services, bookings, invoices, payments, and other entities.
Binary Data Storage
- Added binary serialization for all major entities.
- Introduced record tracking to handle new, modified, and deleted records.
- Added automatic growth and shrinking of mappings when required.
Refactoring
DataStore Changes
- Refactored DataStore to use shared memory instead of local process memory.
- Added generic helper functions for loading and saving records.
- Updated application startup and shutdown to initialize and clean up shared-memory resources.
Synchronization
- Added a global mutex to synchronize datastore operations across processes.
- Added remapping logic to detect mapping size changes made by other instances.
Bug Fixes
- Fixed issues with data not being shared correctly between multiple application instances.
- Improved reliability of record updates and deletions.
- Fixed stale mapping issues when mappings were resized by another process.
Downloads
-
2026-06-01 19:04:55 +05:30 | 59 commits to main since this releaseNew Features
-
Multi-Stage Technician Job Progression — Technicians can now move jobs through multiple stages (STARTED → IN_PROGRESS → COMPLETED). Invoices are generated only after all jobs associated with a booking are completed, with automatic customer notifications to improve transparency and ensure accurate billing.
-
Admin-Level Invoice Payment Completion — Payments now follow a two-stage process. Customer payments update invoices to PAID, while administrators finalize them as COMPLETED. This improves payment tracking, maintains accurate records, and provides real-time customer notifications.
Bug Fixes
- Fixed an issue where customers received duplicate notifications when an assigned technician was removed.
- Prevented creation of duplicate usernames across active, disabled, and deleted user accounts.
- Fixed authentication conflicts caused by the reuse of deleted or disabled usernames.
- Improved booking cancellation handling when customers or technicians are removed from the system.
- Updated cancellation logic to correctly process bookings in the IN_PROGRESS state.
- Improved notification handling during booking and job cancellation workflows.
Downloads
-
-
2026-06-01 19:02:55 +05:30 | 72 commits to main since this releaseThis release includes features that allow users to:
-
Secure Access & Session Management — Role-based login and logout, password changes, and centralized session handling for Administrators, Customers, and Technicians.
-
Full Account Lifecycle Management — Create, update, and remove Technician and Customer accounts; manage user profiles, technician assignments, notification retrieval, and maintain a guaranteed default administrator account.
-
End-to-End Service Workflows — Create and remove services, manage combo packages, assign jobs to technicians, track job cards, manage service bookings, update job progress through multiple stages, complete services, cancel bookings or jobs, and send service-related notifications.
-
Integrated Billing & Payments — Generate invoices for completed services, view customer invoice history, process payments using multiple payment modes, confirm payments through an administrator approval workflow, send payment reminders, and deliver real-time updates using the Observer pattern.
-
Complete Inventory Control — Add inventory items, restock existing inventory, remove obsolete stock, check item availability, monitor stock levels, and automatically generate low-stock alerts for administrators and technicians through Observer-based notifications.
-
Unified Notification System — View notifications across all user roles, configure notification preferences, and receive alerts for service updates, booking confirmations, payment reminders, invoice generation, technician assignment changes, and inventory warnings, all powered by the Subject–Observer pattern.
Downloads
-