VSN-2004 : Defining backend related to first phase validation process of prepared passengers.

MR Description: First Phase Validation Feature for Prepared Passengers

Overview

This merge request introduces the first phase validation feature for prepared passengers. The feature aims to enable the system to efficiently and accurately mark passengers as validated during the first phase of the validation process. This implementation covers all aspects of the backend, including the API endpoint, service layer, database query, and controller exposure, ensuring full end-to-end functionality.

The goal of this MR is to improve data integrity and provide a clear mechanism for tracking the validation state of each prepared passenger, which is essential for subsequent workflows and reporting.

---

Detailed Changes

1. Endpoint Definition

• A new REST API endpoint was introduced to handle the first phase validation process.
• This endpoint is designed to receive requests related to the validation of prepared passengers and forward them to the service layer.
• The endpoint ensures proper request validation and standardized response formatting.

2. Database Update Query

• A custom update query was defined to set the validationStatus property of prepared passengers to true.
• This query ensures that only the intended passenger records are affected, maintaining data consistency.
• The query is optimized to handle batch updates efficiently in case multiple passengers need to be validated simultaneously.

3. Service Layer

• A dedicated service method for the first phase validation was introduced.
• The method signature was defined to accept multiple prepared passenger identifiers and perform the necessary validation logic.
• The service implementation ensures that:
  • The validation status is correctly persisted in the database.
  • All business rules for the first phase validation are respected.
  • Errors are handled gracefully, providing meaningful messages in case of failures.

4. Controller Exposure

• The validation functionality is exposed via the controller, making it accessible to client-side components and external integrations.
• The controller is responsible for receiving the request, invoking the service method, and returning a structured response.
• This design ensures a clear separation of concerns and follows best practices for REST API architecture.

5. Changelog Update

• All changes related to this feature were recorded in the project changelog.
• This ensures proper documentation for release notes and provides traceability for future development and maintenance.

---

Benefits and Impact

• Data Consistency: Prepared passengers’ validation status is accurately updated in the database.
• Maintainability: Well-structured service and controller logic simplifies future modifications or enhancements to the validation process.
• Scalability: The service method is designed to handle bulk validation efficiently.
• Observability: Changes to validation status are fully traceable, supporting auditing and reporting requirements.
• API Accessibility: The feature is exposed through a standard REST endpoint, allowing integration with front-end applications or other systems.

---

Summary

This MR fully implements the first phase validation feature for prepared passengers and provides a robust and maintainable foundation for the validation workflow. The following components were added or updated:

1. REST API endpoint for first phase validation.
2. Database update query to set validationStatus to true.
3. Service method signature and implementation handling validation logic.
4. Controller exposure for API access.
5. Changelog update to document the feature.

These changes together ensure a complete, observable, and efficient first phase validation process, improving both data integrity and user workflow.

Closes VSN-2004