[skip ci] Updates

Author: concur-docs-machine

api-reference/direct-connects/hotel-service-4/images/diagrams/hotel-modify-recover.puml

@@ -0,0 +1,22 @@
+@startuml hotel-modify
+
+participant "User" as user
+
+participant ConcurHotel as cHotel #Lightcyan
+participant "CHSSupplier" as supply #LightBlue
+
+activate cHotel
+loop until booking status is `RESERVED` or transaction timeout
+  cHotel->supply++: Read reservation
+  supply --> cHotel--: Return reservation
+end
+cHotel -> cHotel: Validate that the returned dates match the\nnew dates
+alt Dates do not match
+  cHotel -->user: Notify user that hotel booking\nwas not modified
+else
+  cHotel -->user: Notify user that hotel booking\nhas been modified
+end
+deactivate cHotel
+
+
+@enduml

api-reference/direct-connects/hotel-service-4/images/diagrams/hotel-modify.puml

@@ -5,20 +5,29 @@ participant "User" as user
 participant ConcurHotel as cHotel #Lightcyan
 participant "CHSSupplier" as supply #LightBlue
 
-user -> cHotel++: Check if hotel booking can be modified
-cHotel -> cHotel:  Determine if hotel booking supplier supports modify\n and booking has `isModifiable` true
+activate cHotel
+user -> cHotel: Check if hotel booking can be modified
+cHotel -> cHotel:  Determine if hotel booking supplier supports modify\nand booking has `isModifiable` true
 alt modify not supported
-     cHotel --> user--: Notify user that hotel cannot be modified
+     cHotel --> user: Notify user that hotel cannot be modified
 end
+cHotel --> user: Present modify option
+deactivate cHotel
 
-cHotel --> user--: Present modify option
 user -> cHotel++: Provide new dates for hotel booking
-cHotel -> supply++: Reshop (rate-details) for new dates for booked hotel and rate plan
+cHotel -> supply++: Reshop (rate-details) for new dates\nfor booked hotel and rate plan
 supply --> cHotel--: Return new rate details
 cHotel --> user--: Present new rate details
+
+
 user -> cHotel++: Review and confirm new rate details
+
 cHotel -> supply++: Modify hotel booking with new rate plan id and dates
+note left of cHotel: If there is a timeout or\na status PENDING_CONFIRMATION\na recovery process will be started.
 supply --> cHotel--: Return confirmation of modified hotel booking
-cHotel --> user--: Notify user that hotel booking has been modified
+
+cHotel -->user: Notify user that hotel booking\nhas been modified
+deactivate cHotel
+
 
 @enduml

api-reference/direct-connects/hotel-service-4/images/diagrams/hotel_modify.png

@@ -2794,7 +2794,7 @@ <h3 id="response-6">Response</h3>
 
 <h2 id="modify-">Modify <a id="opIdmodify"></a></h2>
 
-<p>Modify a specific reservation.</p>
+<p>Modify a specific reservation. For more details about the modification process, please read <a href="./v4.hotel-modify-booking.html">Hotel modify support for CHS</a></p>
 
 <h3 id="uri-7">URI</h3>
 

api-reference/direct-connects/hotel-service-4/images/diagrams/hotel_modify_recover.png

@@ -1310,14 +1310,28 @@ <h2 id="workflow">Workflow</h2>
 
 <p>Below is the sequence diagram for the flow:</p>
 
-<p><img src="images/diagrams/hotel_modify.png" alt="" /></p>
+<p><img src="images/diagrams/hotel_modify.png" alt="Modify process" /></p>
+
+<h2 id="modify-recovery-process">Modify Recovery Process</h2>
+
+<p>In the case of a request timed out, SAP Concur will start a recovery process, in wich SAP Concur will try to confirm the status of the booking.
+Also if the supplier identifies that the modification cannot be confirmed in a timely manner, it can return a <code class="language-plaintext highlighter-rouge">PENDING_CONFIRMATION</code> status in the response to the <a href="./v4.endpoints.html#modify-">modify</a> request. In this case SAP Concur will also start a recovery process to confirm the status of the booking.</p>
+
+<p>In the process of recovery, SAP Concur will invoke the <a href="./v4.endpoints.html#read-">read</a> endpoint to get the state of the modified booking. If the returned booking have a <code class="language-plaintext highlighter-rouge">RESERVED</code> status and have the new dates requested by the user, then the booking is marked as confirmed. If the returned booking have a <code class="language-plaintext highlighter-rouge">PENDING_CONFIRMATION</code> status, SAP Concur will continue to invoke the <a href="./v4.endpoints.html#read-">read</a> endpoint until the endpoint return a booking with status <code class="language-plaintext highlighter-rouge">RESERVED</code> for a maximum of 1 day.
+If after 1 day the booking is still in <code class="language-plaintext highlighter-rouge">PENDING_CONFIRMATION</code> status, then SAP Concur will keep the booking status as Pending. When the user tries to view the booking, SAP Concur will call again the <a href="./v4.endpoints.html#read-">read</a> endpoint to sink the status of the booking with the supplier.
+If the returned booking have status of <code class="language-plaintext highlighter-rouge">RESERVED</code> but the dates of check-in and check-out are not the same as the dates requested by the user, then SAP Concur will consider the modification as failed and will notify the user about it.</p>
+
+<p>Below is the sequence diagram for the recovery flow:</p>
+
+<p><img src="images/diagrams/hotel_modify_recover.png" alt="Modify Recovery Process" /></p>
 
 <h2 id="requirements-for-chs-supplier">Requirements for CHS Supplier</h2>
 
 <ul>
   <li>Supplier is expected to set <a href="./v4.schemas.html#-hotelbooking"><code class="language-plaintext highlighter-rouge">isModifiable</code></a> flag to <code class="language-plaintext highlighter-rouge">true</code> in the booking response if they support <code class="language-plaintext highlighter-rouge">modify</code> feature for a given booking.</li>
   <li>Supplier will need to support <code class="language-plaintext highlighter-rouge">reshop</code> request via <a href="./v4.endpoints.html#rate-details-"><code class="language-plaintext highlighter-rouge">rate-details</code></a> providing detailed pricing for new dates on already booked hotel and rate-plan.</li>
   <li>Supplier will need to support <code class="language-plaintext highlighter-rouge">modify</code> request via <a href="./v4.endpoints.html#modify-"><code class="language-plaintext highlighter-rouge">modify</code></a> endpoint to update the booking with new dates.</li>
+  <li>Supplier is expected to set <code class="language-plaintext highlighter-rouge">status</code> to <code class="language-plaintext highlighter-rouge">PENDING_CONFIRMATION</code> in the response of <a href="./v4.endpoints.html#read-">read</a> endpoint if the modification is not confirmed.</li>
 </ul>
 
 

api-reference/direct-connects/hotel-service-4/v4.endpoints.html

@@ -5,8 +5,8 @@
     <description>Concur docs provides comprehensive information on working with the Concur platform</description>
     <link>https://preview.developer.concur.com/</link>
     <atom:link href="https://preview.developer.concur.com/feed.xml" rel="self" type="application/rss+xml" />
-    <pubDate>Fri, 22 Aug 2025 18:11:00 +0000</pubDate>
-    <lastBuildDate>Fri, 22 Aug 2025 18:11:00 +0000</lastBuildDate>
+    <pubDate>Tue, 26 Aug 2025 12:27:06 +0000</pubDate>
+    <lastBuildDate>Tue, 26 Aug 2025 12:27:06 +0000</lastBuildDate>
     <generator>Jekyll v4.1.1</generator>
 
   </channel>