This PR ensures time fields are required when dates are set, using Oqtane validation and dynamically toggles the required attribute on time inputs when their corresponding date fields have values. Benefits:
- Uses Oqtane's validation for a polished UX.
- Reduces custom validation code.
- Aligns with our internal form logic.
- Tested across all date/time scenarios—works flawlessly!
**Testing Confirmed:**
- Date + Time Provided → Saves successfully.
- No Date + No Time → Optional (no validation).
- Date + No Time → Browser blocks submission with icon error.
This PR addresses an issue where null date/time values could cause exceptions when processing job scheduling.
Changes Made:
- Added proper null checks for _startDate, _startTime, _endDate, _endTime, _nextDate, and _nextTime
- Improved parsing safety for _retentionHistory using int.TryParse()
- Added validation to fail early with meaningful error messages
Impact:
Prevents NullReferenceException and InvalidOperationException when date/time fields are missing
* Refactoring
* Refactoring
* Check for a valid email.
* Fixed missing character.
* Moved logic to the Utilities class.
* Rename template .sql file
* Modified null and empty string check.
* Check for a valid email.
* Fixed missing character.
* Moved logic to the Utilities class.
* Added Favicon support, Progressive Web App support, page title and url support, and private/public user registration options
* Refactoring
* Refactoring
* Check for a valid email.
* Moved logic to the Utilities class.
Co-authored-by: Aubrey <aubrey.b@treskcow.tech>
Co-authored-by: MIchael Atwood <matwood@dragonmastery.com>
Co-authored-by: Shaun Walker <shaun.walker@siliqon.com>
