Skip to content

Commit f668f09

Browse files
[skip ci] Updates
1 parent 531d605 commit f668f09

2 files changed

Lines changed: 28 additions & 30 deletions

File tree

feed.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@
55
<description>Concur docs provides comprehensive information on working with the Concur platform</description>
66
<link>https://preview.developer.concur.com/</link>
77
<atom:link href="https://preview.developer.concur.com/feed.xml" rel="self" type="application/rss+xml" />
8-
<pubDate>Thu, 05 Mar 2026 20:18:43 +0000</pubDate>
9-
<lastBuildDate>Thu, 05 Mar 2026 20:18:43 +0000</lastBuildDate>
8+
<pubDate>Thu, 05 Mar 2026 21:11:06 +0000</pubDate>
9+
<lastBuildDate>Thu, 05 Mar 2026 21:11:06 +0000</lastBuildDate>
1010
<generator>Jekyll v4.1.1</generator>
1111

1212
</channel>

tools-support/release-notes/api/2026-03-03.html

Lines changed: 26 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -444,54 +444,52 @@ <h3 id="now-available-api-deprecation-headers">Now Available: API Deprecation He
444444

445445
<h3 id="preview-get-participant-of-an-existing-request-in-request-v4">Preview: GET Participant of an Existing Request in Request v4</h3>
446446

447-
<p>The Request v4 API will enable customers and partners manage the budget request experience more completely through Concur Request web services. Enhancements will include capabilities to view and manage <em>Participants</em> on a <em>Parent Request</em>, as well as related improvements to existing endpoints.</p>
447+
<p>The Request v4 API will enable customers and partners to better manage their Budget request experience through Concur Request web services. Enhancements will include capabilities to view and manage <em>Participants</em> on a <em>Parent Request</em>, as well as related improvements to existing endpoints.</p>
448448

449449
<p><strong>Overview</strong></p>
450450

451-
<p>The new <em>Participants</em> area will be added to the Request v4 API, including two new endpoints:</p>
451+
<p>A <em>Participants</em> area will be added to the Request v4 API, including two new endpoints:</p>
452452

453453
<ul>
454-
<li>
455-
<p><strong>View participants and related child requests</strong></p>
454+
<li>View Participants and Related Child Requests</li>
455+
</ul>
456456

457-
<p>Customers and partners will be able to retrieve the list of participants associated with a <em>Parent Request</em>, along with the child requests linked to it.</p>
458-
</li>
459-
<li>
460-
<p><strong>Manage participants</strong></p>
457+
<p>Customers and partners will be able to retrieve the list of participants associated with a <em>Parent</em> request, along with the child requests linked to it.</p>
461458

462-
<p>Customers and partners will be able to add and remove participants on a parent request.</p>
463-
</li>
459+
<ul>
460+
<li>Manage Participants</li>
464461
</ul>
465462

463+
<p>Customers and partners will be able to add and remove participants on a <em>Parent</em> request.</p>
464+
466465
<p><strong>Updates to Existing Request v4 API Behavior</strong></p>
467466

468467
<ul>
469-
<li>
470-
<p><strong>Request policies for a user</strong></p>
468+
<li>Request Policies for a User</li>
469+
</ul>
471470

472-
<p>Policy responses will indicate whether a given policy supports creating <em>Parent Requests</em> (<em>Budget Requests</em>).</p>
473-
</li>
474-
<li>
475-
<p><strong>Create a request</strong></p>
471+
<p>Policy responses will indicate whether a given policy supports creating <em>Parent</em> requests (Budget requests).</p>
476472

477-
<p>The create request process will support both <em>Budget Request</em> scenarios:</p>
478-
<ul>
479-
<li>Creating a <em>Parent Request</em> using an eligible policy</li>
480-
<li>Creating a <em>Child Request</em> and linking it to an existing <em>Parent Request</em></li>
481-
</ul>
482-
</li>
483-
<li>
484-
<p><strong>Get request details</strong></p>
473+
<ul>
474+
<li>Create a Request</li>
475+
</ul>
485476

486-
<p>Request details will now indicate whether the request is a <em>Parent</em> or a <em>Child request</em>. For <em>Child Requests</em>, the response will also include a reference to the related <em>Parent Request</em>.</p>
487-
</li>
477+
<p>The request creation process will support the following Budget request scenarios:</p>
478+
479+
<p>– Creating a <em>Parent Request</em> using an eligible policy
480+
– Creating a <em>Child Request</em> and linking it to an existing <em>parent</em> request</p>
481+
482+
<ul>
483+
<li>Get Request Details</li>
488484
</ul>
489485

486+
<p>Request details will indicate whether it is a <em>Parent</em> or <em>Child</em> request. For <em>Child</em> requests, the response will also include a reference to the related <em>Parent</em> request.</p>
487+
490488
<p><strong>Configuration / Feature Activation</strong></p>
491489

492-
<p>The Request v4 APIs are available for users of both Professional and Standard versions of SAP Concur Request.</p>
490+
<p>The Request v4 APIs will be available for users of both Professional and Standard versions of Concur Request.</p>
493491

494-
<p>For additional information, please view the <a href="/api-reference/request/v4.get-started.html">Request v4</a> API documentation.</p>
492+
<p>For additional information, refer to the Request v4 API documentation.</p>
495493

496494
<h3 id="decommissioning-of-launch-external-url-v1">Decommissioning of Launch External URL V1</h3>
497495

0 commit comments

Comments
 (0)