VSN-1965 : Correcting validation integration to align with newly Introduced changes in the backend.

Merge Request – Validation Flow Enhancement and Validator Email Integration

Overview

This Merge Request introduces a significant enhancement to the prepared passenger validation workflow by integrating the validator's email across the full processing chain, from the frontend through to the backend service call.

Primary goals:

• Enable clear traceability of validation actions.
• Establish a foundation for auditability and accountability.
• Prepare the system for future extensions such as signatures, logging, and validation history.
• Improve technical consistency and user experience.

---

Scope of Changes

1. feat(validation): Defining validator email

Introduces the validator email within the store method signature.

Changes:

• Added validatorEmail as a parameter in the store method.
• Defined the parameter as a key input in the validation process.

Outcome:

• The backend now receives a reliable identifier for tracking the validator.

---

2. fix(path): Fixing validation path

Adjusts the validation endpoint to support the newly introduced parameter.

Changes:

• Corrected the validation API path to properly include and forward validatorEmail.

Outcome:

• The validation flow remains functional and aligned with the updated data requirements.

---

3. refactor(validation): Validation implementation update

Adapts the internal validation logic to the new data structure.

Changes:

• Updated the validation logic to handle validatorEmail.
• Aligned method signatures across the validation flow.
• Prepared the implementation for future enhancements such as audit logging and signatures.

Outcome:

• A consistent and maintainable validation implementation.

---

4. refactor(validation): Passing validator email

Ensures end-to-end propagation of the validator email.

Changes:

• Updated the flow from frontend to store to API to pass validatorEmail.
• Standardized parameter handling across layers.

Outcome:

• Reliable transmission of the validator email through the entire validation process.

---

5. refactor(validation): Corrections and improvements

Applies technical fixes and improves user experience.

Changes:

• Corrected the local storage key name from email to userEmail for clarity.
• Triggered the snackbar message before the API call to improve perceived responsiveness.

Outcome:

• Clearer data semantics and a more responsive user interaction.

---

6. feat(env): Gateway path

Updates the gateway context path to the remote environment.

Changes:

• Switched the gateway path from a local value to a remote one.

Outcome:

• Alignment with the target infrastructure and deployment environment.

---

Impacts

Functional

• Validator identity is now traceable throughout the validation process.
• Validation workflow is enriched and more transparent.
• Improved responsiveness in the user interface.

Technical

• Unified method signatures.
• Stabilized API routing.
• Architecture prepared for upcoming features such as:
  • audit logging,
  • validation signatures,
  • validation history tracking.

---

Backward Compatibility

• No functional break for future validations.
• Previous flows lacking validatorEmail require adaptation to maintain compatibility.

---

Next Steps (Recommendations)

• Persist validator email into an audit log or history table.
• Display validator identity in validation result views.
• Introduce signature or hash generation based on validator identity.

---

Conclusion

This Merge Request strengthens the validation workflow, enhances traceability, improves technical consistency, and prepares the system for future compliance-oriented capabilities.

Closes VSN-1965