Conditions and Safety
Frontend validation conditions, backend-authoritative checks, and split-specific UI safety behavior.
👤 Sachin Sharma, Nilesh Bhusari📅 Updated: Mar 24, 2026🏷️ feature🏷️ frontend🏷️ validation🏷️ safety
UI validation conditions
- Dismissed tests are automatically removed from the test list available for splitting.
- Confirm action is disabled when no tests are selected.
- Client-side guard blocks selecting all tests in a single split action.
- API request button is disabled during submission to prevent duplicates.
Backend-authoritative checks
Frontend performs basic user-facing checks, while backend remains authoritative for:
- final eligibility validation,
- guarded-table restrictions,
- source restrictions and complex split constraints,
- attachment-category enforcement.
Support behavior
- Split uses existing Order Update context and does not require route changes.
- Existing translation keys and alert infrastructure are reused.
- Existing footer modal orchestration remains unchanged.
Decision alignment in UI
- Optional destination source selector is available in modal.
- Parent-retention rule is reflected by blocking full-selection split.
- Error handling surfaces backend message details when available.