Concur Invoice Standard Edition Administration Help

February 2022 Request Standard Edition Admin Summary

Initial Post

Release Note Summaries

These release note summaries are specific to this product. For information about site-wide or shared changes that might impact your SAP Concur solutions, refer to the Shared Changes Admin Summaries.

The Standard Edition release notes are accessible from What's New - Standard Edition.

NextGen UI for Concur Request

**Ongoing** Updated User Interface (UI) for Concur Request End Users

The continued evolution of the Concur Request solution user interface experience is the result of thoughtful design and research that provides a modern, intuitive and streamlined experience for the request process.

Concur Request customers are now strongly encouraged to preview and then move to the NextGen UI well before the automatic transition date of 1 October, 2022.

Business Purpose/Client Benefit: The result is the next generation of the Concur Request user interface designed to provide a modern, consistent and streamlined user experience. This technology not only provides an enhanced user interface, but also allows us to react more quickly to customer requests to meet changing needs as they happen.

SAP Concur Platform

**Ongoing** Retirement and Decommission of Existing Concur Request APIs (v1.0, v3.0, v3.1) (30 November, 2021)

As of 31 May 2021, the existing Concur Request APIs (v1.0, v3.0 and v3.1) are deprecated. On 1 June 2021, SAP began retiring these APIs in accordance with the SAP Concur API Lifecycle & Deprecation Policy. These APIs are replaced by the Concur Request v4 APIs. SAP will no longer support these APIs after retirement.

As of 30 November 2021, the retirement phase for the existing Concur Request APIs (v1.0, v3.0 and v3.1) is completed.

Decommissioning of the v1.0, v3.0 and v3.1 APIs will start three months after retiring the APIs. The specific dates for decommissioning are dependent on the individual client's API migration.

API Timeline for v1.0, v3.0, v3.1:

  • Deprecation – 1 March, 2020 – 31 May, 2021

  • Retirement – 1 June, 2021 – 30 November, 2021

  • Decommission – starts after 3 months of inactivity at the retired state

Business Purpose / Client Benefit: The Concur Request APIs v1.0, v3.0 and v3.1 only support the previous authentication method, which is not best security practice and does not meet the Oauth2 standards. In addition, the previous versions of the Concur Request APIs provided limited possibilities for moving a Request through the approval workflow, as well as managing custom simple & connected list fields. These issues are resolved with the new Concur Request v4 APIs.

In addition, SAP has run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 APIs (not ISO-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 APIs.

Planned Change Summaries

The items in this section are targeted for future releases. SAP Concur reserves the right to postpone implementation of – or completely remove – any enhancement/change mentioned here.

There are no planned changes this month.

Client Notifications

The items in this section provide reference material for all clients.

Accessibility Updates

SAP implements changes to better meet current Web Content Accessibility Guidelines (WCAG). Information about accessibility-related changes made to SAP Concur solutions is published on a quarterly basis. You can review the quarterly updates on the Accessibility Updates (English only) page.

SAP Concur Non-Affiliated Subprocessors

The list of non-affiliated subprocessors is available here: SAP Concur list of Subprocessors (English Only)

Supported Browsers and Changes to Support

For information about supported browsers and planned changes to supported browsers, refer to the Concur Travel & Expense Supported Configurations (English Only) guide. When changes to browser support are planned, information about those changes will also appear in the Shared Changes Release Notes.