SigniQ v1.3.3 Release Notes
Date: 06-01-2026
Dear SigniQ Users,
We’re excited to announce SigniQ v1.3.3! This release focuses on improving validation, deployment instructions, and booking reliability, ensuring a smoother and safer experience for your scheduling operations.
Validation Improvements
Ensure email and phone validation at submit
What changed
- Email and phone fields are now validated when the form is submitted, not just on blur.
- Prevents users from submitting invalid data if they bypass field interactions.
Benefit
- Increased data integrity and reduced errors from incomplete or invalid form submissions.
Consistent validation logic across the application
What changed
- Unified validation logic for email and phone using a single utility function across all forms.
Benefit
- Ensures consistent input handling and reduces potential bugs due to inconsistent validation.
Allow only valid mobile numbers
What changed
- The validation function now accepts only valid mobile numbers.
Benefit
- Prevents invalid or malformed numbers from being submitted, improving reliability of notifications and SMS functionality.
Use validation at input time
What changed
- Email and phone fields are validated as the user types, not just after submission.
Benefit
- Provides immediate feedback to users, improving user experience and reducing submission errors.
Deployment & Configuration Updates
Update deployment instructions
What changed
- Deployment documentation is updated with automation steps
Benefit
- Makes deployments smoother and reduces the likelihood of setup errors.
Remove build parameter for Stripe key
What changed
- Stripe API key is now passed dynamically instead of being set as a build-time parameter. This allows super admin to configure tenants with their own stripe api gateways dynamically.
Benefit
- Simplifies deployment and allows flexibility to change keys without rebuilding the application.
Booking & Payment Fixes
Trigger booking event only on confirmation
What changed
- Booking-created/confirmed events are now triggered only after payment is completed.
Benefit
- Prevents premature notifications or booking confirmations if payment fails, improving reliability and reducing customer confusion.