The ConfirmDate web service is the finalization step within the Booking module. It is invoked by the external system (e.g., Middleware, Customer Portal) to notify the platform that the customer has officially accepted the TEMPORARY time slot proposed during a FirstDate or FurtherDate call.
Upon successful execution, this service permanently locks the capacity, officially assigns the schedule to the Work Order, and transitions the appointment into a SCHEDULED status.
Input Validation & Error Handling
When the ConfirmDate call is received, the Booking module performs strict data validation to prevent data corruption or double-booking. If any of the following checks fail, the system blocks the confirmation and returns a specific error:
-
ID Mismatch: The system cross-references the external request ID (
requestCode) with the internal Appointment ID (ID_APPUNTAMENTO). If they do not match the expected record, it returns:"Incorrect Appointment". -
Slot Mismatch: The system verifies the submitted
slotId. If it does not belong to the targeted appointment, it returns:"Incorrect Slot". -
Duplicate Confirmation: If the targeted appointment has already been successfully processed and is no longer temporary, it returns:
"Error: existing appointment".
System Impact & Status Updates
The most significant system impact of the ConfirmDate service depends on the history of the booking. The system handles standard confirmations differently from rescheduling confirmations to ensure no capacity is accidentally lost.
|
Booking Scenario |
System Logic & Execution Behavior |
|
Standard Confirmation
(Path: OR (Path: |
Direct Status Update.
The single |
|
Rescheduling Confirmation
(Path: |
Swap and Capacity Release.
In this scenario, the WO temporarily holds two appointments (the originally confirmed one, and the new temporary one). Upon this call:
|