[skip ci] Updates

feed.xml

@@ -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>Wed, 06 Nov 2024 20:50:44 +0000</pubDate>
-    <lastBuildDate>Wed, 06 Nov 2024 20:50:44 +0000</lastBuildDate>
+    <pubDate>Wed, 06 Nov 2024 21:41:02 +0000</pubDate>
+    <lastBuildDate>Wed, 06 Nov 2024 21:41:02 +0000</lastBuildDate>
     <generator>Jekyll v4.1.1</generator>
 
   </channel>

tools-support/release-notes/api/2024-11-07.html

@@ -260,6 +260,31 @@ <h1 id="api-release-notes-november-2024">API Release Notes, November 2024</h1>
 
 <h2 id="new-this-month">New This Month</h2>
 
+<h3 id="now-available-verified-email-flag-management-in-sap-concur-profile-via-identity-41-and-ups-40-apis">Now Available: Verified Email Flag Management in SAP Concur Profile via Identity 4.1 and UPS 4.0 APIs</h3>
+
+<p>We have released a new feature that allows clients to manage the verified email flag within the SAP Concur user profile via the Identity 4.1 or UPS 4.0 APIs. This enhancement provides more flexibility and control over user profile management, improving user verification processes. Users will continue to have the option to verify their email addresses.</p>
+
+<p><strong>Key Features</strong></p>
+
+<ul>
+  <li><strong>Verified Email Flag Management:</strong> Clients can now set or update the verified email flag for user profiles, ensuring that email addresses are correctly marked as verified within the SAP Concur system.</li>
+  <li><strong>API Support:</strong> The feature is available through both Identity 4.1 and UPS 4.0 APIs, allowing for seamless integration with your existing systems. Flat file support will follow next year.</li>
+</ul>
+
+<p><strong>How to Use</strong></p>
+
+<ul>
+  <li>During user creation or updating, set the emails.verified parameter within the Identity 4.1 or UPS 4.0 API to update the status.</li>
+  <li>Refer to the Identity API <a href="/api-reference/profile/v4.identity.html">documentation</a> for details on implementation and parameters.</li>
+</ul>
+
+<p><strong>Benefits</strong></p>
+
+<ul>
+  <li>Simplifies email management workflows.</li>
+  <li>Reduces the need of manual intervention to set the value.</li>
+</ul>
+
 <h3 id="preview-deeplink-integration-for-travel-updates">Preview: Deeplink Integration for Travel Updates</h3>
 
 <p>In November, hotel deep link capabilities will be expanded to allow users to add a hotel to an existing trip. When the <code class="language-plaintext highlighter-rouge">tripID</code> is included in the hotel deep link, users will proceed directly to the hotel shop results page using the hotel parameters specified in the deep link. If hotel parameters are not included in the deep link (<code class="language-plaintext highlighter-rouge">tripID</code> only), then the user will proceed directly to the hotel shop results page based on the trip booking details. The check-in dates will be based on the departure date of the first flight and the checkout date will be based on the last flight in the itinerary. If a one way flight is booked, the check-out date is take from the trip end date. If no air is booked, then the trip start and end dates are used.</p>