SigniQ v1.4.17 – Release Notes
Date: 05-08-2026
This release improves retention reminders, subscription visibility, holiday availability, review links, short‑link handling, and overall UI stability. It also adds new failover documentation and build improvements.
Retention improvements
What changed
Retention now has reminders fully enabled, sending both due and overdue reminders automatically. Staff can configure retention reminder timings as needed for each service or asset.
Why it matters
Retention follow‑ups are now consistent and timely, helping customers return on schedule with minimal manual effort.
Subscription visibility
What changed
Subscriptions are now grouped by SMS and Email with clear status indicators. All subscription entries are shown even if the staff member has left, marked as “unknown”.
Why it matters
Teams get a complete and accurate view of all notification subscriptions.
Holiday hours & availability
What changed
Holiday hours are now included correctly when showing service availability. Only dates with actual availability are shown. Weekly slot grouping is now accurate.
Why it matters
Booking calendars are more accurate, especially around holidays and special dates.
Review system fixes
What changed
Review URLs now use the correct t= parameter.
Review processing updated to use standard API paths.
Why it matters
Review links work reliably and are easier to maintain.
Short‑link system
What changed
A new short‑link system is now used for all URLs shared with customers, especially for SMS. Supports both http and https, with paged loading for large lists.
Why it matters
Links are shorter, cleaner, and more reliable across SMS and other channels.
Employee management
What changed
Employee duplicate validation now checks against all team members. Team data refreshes on every update.
Why it matters
Prevents invalid employee entries and improves data accuracy.
Availability UI fixes
What changed
Week numbering is now consistent. Edit settings no longer close on double‑click.
Why it matters
The UI feels more stable and predictable.
DB failover documentation
What changed
A new document explains how to switch to a standby database instance when the primary fails.
Why it matters
Teams have clear guidance for safe failover handling.
Build & repo cleanup
What changed
New CI build script added. Local build script renamed. Unwanted DB dump removed. Linting errors fixed.
Why it matters
Builds are cleaner, faster, and easier to maintain.