Travel: August 2020 Release Notes · Web viewPreviously, when an API customer using Legacy OAuth...

SAP Concur Release Notes

Concur TravelConcur Professional/Premium and Concur Standard

Month AudienceRelease Date: August 15, 2020

Initial Post: Thursday, August 13, 3:00 PM PT SAP Concur Client FINAL

** FINAL **

The enhancements and changes described in this document may or may not be included in this release. SAP Concur reserves the right to postpone implementation of – or completely remove – any enhancement/change mentioned here.

The PREVIEW, DRAFT, and FINAL release notes contain information about Concur Professional/Premium and Concur Standard.

Each note contains a table that which indicates if the enhancement/change applies to Professional and/or Standard.

ContentsRelease Notes............................................................................................1

Administration...................................................................................................1Post-Approval Pre-ticket Change Queue............................................................................1

Flight................................................................................................................3**Ongoing** Southwest Ticket Credit Expiry Date Update.................................................3

Miscellaneous....................................................................................................4Legacy OAuth Refresh Access Token.................................................................................4**Ongoing** Deprecation of Director SAML Service and Migration to SAML v2..................5**Ongoing** Deprecation of HMAC Initiates Migration to SSO Self-Service........................7**Ongoing** SAP Concur Legacy File Move Migration........................................................9SSL Certificates for us.api.concursolutions.com and emea.api.concursolutions.com Expiring...........................................................................................................................11

Planned Changes......................................................................................13Profile.............................................................................................................13

**Planned Changes** Travel Profile 2.0 API, Active Arrangers Only.................................13SAP Concur Release Notes Page i Concur TravelRelease Date: August 15, 2020 SAP Concur Client FINALInitial Post: Thursday, August 13, 3:00 PM PT

Flight..............................................................................................................14**Planned Changes** Next Generation AA AirPass Program............................................14

Client Notifications...................................................................................16Browser Certifications and Supported Configurations........................................16

Monthly Browser Certifications and Supported Configurations........................................16Subprocessors.................................................................................................16

SAP Concur Non-Affiliated Subprocessors........................................................................16

Additional Release Notes and Other Technical Documentation....................17Online Help – Admins........................................................................................17SAP Concur Support Portal – Selected Users......................................................18

SAP Concur Release Notes Page ii Concur TravelRelease Date: August 15, 2020 SAP Concur Client FINALInitial Post: Thursday, August 13, 3:00 PM PT

Legal DisclaimerThe information in this presentation is confidential and proprietary to SAP SE or an SAP affiliate company and may not be disclosed without the permission of SAP SE or the respective SAP affiliate company. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP SE or its affiliated companies. SAP SE and its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation and SAP SE or an SAP affiliate company’s strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP SE and its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise or legal obligation to deliver any material, code or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP SE and its affiliated companies assume no responsibility for errors or omissions in this document, except if such damages were caused by SAP SE or an SAP affiliate company’s willful misconduct or gross negligence.

All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

SAP Concur Release Notes Page iii Concur TravelRelease Date: August 15, 2020 SAP Concur Client FINALInitial Post: Thursday, August 13, 3:00 PM PT

Release Notes: Miscellaneous

Release Notes

Administration

Post-Approval Pre-ticket Change QueueProf Stan Edition

On: Impacts end users who use this feature/vendor; no configuration/setup by agency/ admin; cannot be turned OFF (example: new icons or rate display, new Amtrak feature)

X X Available for use: No impact to end users unless/until configuration/setup by agency/admin (described below) (example: new rule, new Travelfusion airline)Other: Refer to the release note belowDoes not apply to this edition

Source / Solution SuggestionGDS All GDS

Direct Connect

Solution IDOther

X EMEA Data Center Scan impactX North America Data Center UI impact

China Data Center File finishing impactAll data centers Profile/Profile API/3rd Party XML Sync Impact

Affected DocumentationTSGs

Fact SheetsAdmin Guides Travel System Admin Guide

Other

Overview

In some limited situations, an air trip that has been approved but not yet ticketed might undergo a trip change to an earlier travel date, which in turn adjusts the trip’s ticketing deadline to an earlier date than was previously documented in the GDS reservation (PNR). Since all trip change PNRs are dropped into the In-process queue, trips in this situation are not readily identifiable by agency partners and may result in missed ticketing and auto-cancellation.

With this release, a new GDS queue is introduced for these PNRs. The new queue is called Post-approval Pre-ticket Change. PNRs will only appear on this queue if the queue has been configured and the PNR is in the described state. When the queue is configured and a post-approval pre-ticket change occurs, the system will drop the PNR into the new queue instead of the In-process queue. The TMC will then be able to take appropriate action.

In addition, a new PNR Remark will be added to PNRs that are sent to the new queue, which documents the post-approval pre-ticket change with a timestamp. The TMC can use the remark to ensure on-time ticketing. The timestamp identifies when the change was made.

SAP Concur Release Notes Page 1 Concur TravelRelease Date: August 15, 2020 SAP Concur Client FINALInitial Post: Thursday, August 13, 3:00 PM PT


NOTE:While the new queue is available to configure for all GDSs, the PNR remark is not currently supported for Amadeus PNRs.

What the User Sees

There is no change to what end users see in Concur Travel.

What the Agency Partner Sees

When a PNR is sent to the Post-approval Pre-ticket Change queue, Concur Travel will include a PNR remark for agency use. Below is an example of a PNR remark:

CB/POST-APPROVAL CHANGE/2020-07-15T21.22.00Z

Configuration for Professional and Standard Travel

To configure the queue:

1. Navigate to the Agency Configuration you want to update and locate the Defined Queues section. Specify the Queue and Category/Prefatory for the Post-approval Pre-ticket Change queue:

2. To complete the configuration, click Submit.



Flight

**Ongoing** Southwest Ticket Credit Expiry Date UpdateInformation First Published Information Last Modified Feature Target Release Date

June 2020 - September 2020Any changes since the previous monthly release are highlighted in yellow in this release note.

Prof Stan Edition

X X On: Impacts end users who use this feature/vendor; no configuration/setup by agency/ admin; cannot be turned OFF (example: new icons or rate display, new Amtrak feature)Available for use: No impact to end users unless/until configuration/setup by agency/admin (described below) (example: new rule, new Travelfusion airline)Other: Refer to the release note belowDoes not apply to this edition

Source / Solution SuggestionGDS

Direct Connect

Southwest

Solution IDOther




Fact SheetsAdmin Guides

Other

Overview

Because of the COVID-19 pandemic, Southwest Airlines has extended the validity of unused ticket credits multiple times. SAP follows these changes and ensures that travelers do not lose their ticket credits. Due to system limitations, these updates in Concur Travel will happen in multiple iterations and, in certain cases, the expiry date in Concur Travel may not reflect to what was communicated by Southwest Airlines. The effected ticket credits, however, will not expire and will be available to use until the extended expiry date.

The latest expiry date update occurred on June 5, 2020; all entries created before this date have the expiry date set to September 7, 2022. Manual unused ticket credit entries created after June 5, 2020 will not be updated before September 2020. Please make sure that the expiry date of any new entries is in accordance with the latest official communication of Southwest Airlines.

NOTE:The next unused ticket credit update is scheduled for September 2020. Airline policy updates may cause this date to change.

For more information, refer to https://www.southwest.com/Coronavirus/.


https://www.southwest.com/Coronavirus/



This feature is enabled by default. There are no configuration steps.

Miscellaneous

Legacy OAuth Refresh Access TokenProf Stan Edition

On: Impacts end users who use this feature/vendor; no configuration/setup by agency/ admin; cannot be turned OFF (example: new icons or rate display, new Amtrak feature)Available for use: No impact to end users unless/until configuration/setup by agency/admin (described below) (example: new rule, new Travelfusion airline)

X X Other: Refer to the release note belowDoes not apply to this edition


Direct Connect

Solution IDOther

EMEA Data Center Scan impactNorth America Data Center UI impactChina Data Center File finishing impact

X All data centers Profile/Profile API/3rd Party XML Sync ImpactAffected Documentation

TSGsFact Sheets

Admin GuidesOther SAP Concur Developer Center

Overview

Previously, when an API customer using Legacy OAuth refreshed an access token, the same token would be updated with a new expiry date. As of the July 2020 release, a new and fully unique access token is returned with a new expiry date.

For more information, refer to the SAP Concur Developer Center Authentication guide, https://developer.concur.com/api-reference/authentication/authorization-pre-2017.html#refreshing-access-token .

USER/CUSTOMER BENEFIT

Providing a new token allows for improved security.


https://developer.concur.com/api-reference/authentication/authorization-pre-2017.html#refreshing-access-token

https://developer.concur.com/api-reference/authentication/authorization-pre-2017.html#refreshing-access-token


**Ongoing** Deprecation of Director SAML Service and Migration to SAML v2

Information First Published Information Last Modified Feature Target Release DateJuly 10, 2020 -- July – December 2020

Any changes since the previous monthly release are highlighted in yellow in this release note.

Prof Stan EditionOn: Impacts end users who use this feature/vendor; no configuration/setup by agency/ admin; cannot be turned OFF (example: new icons or rate display, new Amtrak feature)Available for use: No impact to end users unless/until configuration/setup by agency/admin (described below) (example: new rule, new Travelfusion airline)



Direct ConnectSolution ID

OtherEMEA Data Center Scan impactNorth America Data Center UI impactChina Data Center File finishing impact


TSGsFact Sheets

Admin GuidesOther

NOTE:These changes are part of our continued commitment to maintaining secure authentication.

Overview

Support for the Director SAML service is being deprecated. Travel Management Companies (TMCs) and SAP Concur personnel will soon begin assisting customers who currently use Director SAML to migrate to SAP Concur SAML v2 SSO (SAML v2).

Clients currently using Director SAML are encouraged to migrate to SAML V2 as soon as possible.

Deprecation of support for the Director SAML service is dependent on the following requirements:

SAP Concur technicians and TMCs assist existing SAP Concur clients to migrate from the Director SAML service to SAML V2.

All clients that currently rely on the Director SAML service have migrated from Director SAML to SAML V2.

Migration from Director SAML to SAML V2 requires the following general steps: The client identifies an admin to act as the SSO admin and assigns the proper

permission/role.



The SSO admin coordinates with their SAP Concur technician to obtain the SAP Concur SP metadata.

The SSO admin configures the SSO settings at the IdP based on information from SP metadata.

The SSO admin retrieves IdP metadata from the IdP and delivers the metadata to the SAP Concur technician.

The SSO admin adds a few testing users and tests the new SSO connection. With successful testing, the company rolls out SSO to their SAP Concur users.

For more detailed information about migrating to SAML v2, refer to the SSO Service: Overview Guide and the Shared: SSO Management Setup Guide.


This change provides better security and improved support for users logging in to SAP Concur products and services.


MIGRATION FOR TMCS

TMCs will be significantly impacted by this change and should begin testing now to prepare for migration to SAML V2.

TMCs must set up SAML v2 instead of Director SAML for their new clients. Setting up SAML v2 now allows more time for TMCs to test the new configuration and train internal staff to assist clients.

To prepare for the deprecation of Director SAML: TMCs must support SAML 2.0 compliant SSO. TMCs must contract for, or

develop, their SAML 2.0-compliant solution. TMCs must have an Identity Provider (IdP).

Once support for SAML 2.0-compliant SSO is established, TMCs that need more information can open a case with SAP Concur support. TMCs do not need to use the online order form to request setup.

MIGRATION FOR LEGACY DIRECTOR SAML CLIENTS

Clients should begin testing SAML v2 immediately to prepare for migration.

To prepare for the deprecation of Director SAML: Clients must have an Identity Provider (IdP) or a custom SAML 2.0-compliant

solution. Clients must coordinate with an SAP Concur technician to complete migration

to SAML v2.

For more information, refer to the SSO Service: Overview Guide and the Shared: SSO Management Setup Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.


https://www.concurtraining.com/customers/tech_pubs/Docs/_Current/SG_Shr/Shr_SG_SSO_Mgmt.pdf


https://www.concurtraining.com/customers/tech_pubs/Docs/_Current/SG_Shr/Shr_SSO_Service_Overview.pdf





**Ongoing** Deprecation of HMAC Initiates Migration to SSO Self-Service

Information First Published Information Last Modified Feature Target Release Date

July 12, 2019 July 17, 2020 Phase I: July 2020Phase II: July 2021

Any changes since the previous monthly release are highlighted in yellow in this release note.







TSGsFact Sheets

Admin GuidesOther

NOTE:These changes are part of our continued commitment to maintaining secure authentication.

Overview

SAP Concur support for Hash-Based Message Authentication Code (HMAC) is being deprecated. Travel Management Companies (TMCs) and SAP Concur personnel are currently assisting customers who use HMAC to migrate to SAP Concur SAML v2 SSO (SAML v2).

In Q3 of 2020, SAP Concur plans to provide a self-service tool that will enable client admins to setup their SAML v2 connections without involving an SAP Concur support representative.

NOTE:SAML v2 supports the use of multiple identity providers (IdPs).

The HMAC deprecation includes two phases:

Phase I: Clients must have an identity provider (IdP) or a custom SAML 2.0-compliant

solution. Clients begin testing authentication using SAML v2.



TMCs prepare to onboard new SAP Concur clients to SAML v2. Once the SSO self-service tool is available, customers will be notified via

release notes about the official deprecation date of HMAC. As of the official deprecation date, no new clients can be onboarded using HMAC; new clients must be onboarded to SAML v2.

Existing clients using HMAC must migrate to SAML v2.

Phase II: TMCs have migrated all existing SAP Concur clients from the HMAC service to

SAML v2. The HMAC service is deprecated. Phase II is targeted to end mid-year in 2021.


This change provides better security and improved support for users logging in to SAP Concur products and services.

MIGRATION FOR TMCS

TMCs will be significantly impacted and should begin testing now to prepare for migration to SAML v2.

TMCs must set up SAML v2 instead of HMAC for their new clients. Setting up SAML v2 now allows more time for TMCs to test SAML v2 and to train internal staff to assist clients.

To prepare for Phase I of the HMAC deprecation: TMCs must support SAML 2.0 compliant SSO. TMCs must contract for or

develop their SAML 2.0 compliant solution. TMCs must have an Identity Provider (IdP).

Once support for SAML 2.0 compliant SSO is established, TMCs that need more information can open a case with SAP Concur support. TMCs do not need to use the online order form to request setup.

MIGRATION FOR LEGACY HMAC CLIENTS

Clients should begin testing SAML v2 immediately to prepare for migration.

To prepare for Phase I of the HMAC deprecation: Clients must have an Identity Provider (IdP) or a custom SAML 2.0 compliant

solution. Clients can coordinate with SAP Concur support now to complete migration to

SAML v2. When it is released, clients can configure the SSO self-service tool. The self-

service tool is targeted for release in Q3 of 2020.



For more information, refer to Authentication | **Planned Changes** Single Sign-On (SSO) Self-Service Option in the Shared Planned Changes release notes and to the SSO Service: Overview Guide and the Shared: SSO Management Setup Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

**Ongoing** SAP Concur Legacy File Move MigrationInformation First Published Information Last Modified Feature Target Release Date

March 6, 2020 -- Ongoing in 2020Any changes since the previous monthly release are highlighted in yellow in this release note.







TSGsFact Sheets

Admin GuidesOther

Overview

This release note is intended for the technical staff responsible for file migrations with SAP Concur solutions. For our customers and vendors participating in data exchange, SAP Concur solutions is maintaining our file transfer subsystem to provide greater security for those file transfers.

SAP Concur solutions will begin migrating entities that currently use a legacy process for moving files to a more efficient and secure file routing process that relies on APIs.

Clients whose entities are currently configured to use the legacy process will be migrated to the more efficient process sometime between now and the end of 2020. After they are migrated to the more efficient process, clients will see the following improvement:

With the legacy process, clients had to wait for the file move schedule to run at a specified time. With the more efficient and secure API-based process, extracts and other outbound files from SAP Concur solutions will be available within the existing overnight processing period shortly after the files are created.





https://www.concurtraining.com/customers/tech_pubs/RN_shared_planned/_client_shared_RN_all.htm


This announcement pertains to the following file transfer DNS endpoints: st.concursolutions.com


These changes provide greater security and efficiency for file transfers.


If assistance is required, please contact SAP Concur support.

For more information, refer to the Shared: File Transfer for Customers and Vendors User Guide. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

SSL Certificates for us.api.concursolutions.com and emea.api.concursolutions.com Expiring







TSGsFact Sheets

Admin GuidesOther

Overview

To ensure the ongoing security of our products and services, the current SSL certificates for us.api.concursolutions.com and emea.api.concursolutions.com are being renewed.

NOTE:The current certificates will expire on August 21, 2020.

Clients who have not pinned the SSL certificates do not need to take any action as the certificates will be renewed automatically. Most clients do not pin certificates.


https://www.concurtraining.com/customers/tech_pubs/Docs/ConcurPremier/UG_Shr/Shr_UG_FileTransfer.pdf

https://www.concurtraining.com/customers/tech_pubs/Docs/ConcurPremier/UG_Shr/Shr_UG_FileTransfer.pdf


Clients who have pinned the expiring certificates must renew the certificates before August 21, 2020. If the pinned certificates are not updated before August 21, 2020, connections to SAP Concur products through SAP integration with Concur Services (SAP ICS) and Web Services might be disrupted. Please consult with your IT department to confirm whether this applies to you.

! IMPORTANT! Because SSL certificates are renewed on a regular basis to ensure the security of our products, pinning them is not recommended.


This update provides ongoing security for our products and services.


For clients who have not pinned the certificates (most clients), there are no configuration steps. The certificates are automatically renewed.

For clients who have pinned the expiring certificate, the new SSL certificate can be accessed using this link: https://assets.concur.com/concurtraining/cte/en-us/api.concursolutions.pem.

NOTE:The landing page contains two certificates, the server certificate and an intermediate certificate.


https://assets.concur.com/concurtraining/cte/en-us/api.concursolutions.pem


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

! IMPORTANT: These Planned Changes may not be all of the upcoming enhancements and modifications that affect this SAP Concur product or service. The Planned Changes that apply to multiple SAP Concur products and/or services are in a consolidated document. Please review the additional Planned Changes available in the Shared Planned Changes Release Notes. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.

Profile

**Planned Changes** Travel Profile 2.0 API, Active Arrangers OnlyInformation First Published Information Last Modified Feature Target Release Date

July 2020 - September 2020Any changes since the previous monthly release are highlighted in yellow in this release note.




Direct Connect

Solution IDOther


China Data Center File finishing impactAll data centers X Profile/Profile API/3rd Party XML Sync Impact



Other

Overview

Currently, when using the Travel Profile 2.0 API to retrieve a user’s Travel Arranger, both active and inactive Arrangers are returned for that user. With this change, the Travel Profile 2.0 API will return only active Travel Arrangers.


https://www.concurtraining.com/customers/tech_pubs/RN_shared_planned/_client_shared_RN_all.htm


For more information, refer to the SAP Concur Developer Center, Travel Profile Resource. To locate, refer to Additional Release Notes and Other Technical Documentation in these release notes.


By returning only the minimum amount of data required to arrange travel SAP Concur solutions can reduce the amount of data exposed online.


This feature is enabled by default. There are no configuration steps.

Flight

**Planned Changes** Next Generation AA AirPass ProgramInformation First Published Information Last Modified Feature Target Release Date

August 2020 4th quarter of 2020Any changes since the previous monthly release are highlighted in yellow in this release note.

Prof Stan EditionOn: Impacts end users who use this feature/vendor; no configuration/setup by agency/ admin; cannot be turned OFF (example: new icons or rate display, new Amtrak feature)

X Available for use: No impact to end users unless/until configuration/setup by agency/admin (described below) (example: new rule, new Travelfusion airline)Other: Refer to the release note below

X Does not apply to this editionSource / Solution Suggestion

GDS Sabre onlyDirect

ConnectSolution ID

OtherX EMEA Data Center X Scan impactX North America Data Center X UI impact


Affected DocumentationTSGs American Airlines AirPass Travel Service Guide


Other

Overview

For companies that participate in the American Airlines AirPass program, Concur Travel will soon have the ability to support American Airlines’ next generation AirPass program. This program allows travelers to purchase unrestricted airfares at a pre-paid fixed rate.


https://developer.concur.com/api-reference/travel-profile/v2.profile-resource.html

https://developer.concur.com/api-reference/travel-profile/v2.profile-resource.html


AirPass utilizes full-fare inventory, offering last-seat availability and flexibility, and is tied to a traveler's AAdvantage membership number. The following options will be made available in Concur Travel:

AAnytime®: Members who make their travel arrangements at the last minute can enjoy last-seat availability by booking in unrestricted First (F), Business (J), or Coach (Y); one-way or round-trip without change fees.

Instant Upgrade Fares (UP Fare): If an UP fare is available in the market, it can be booked using AirPass. All fare rules must still be followed.

AA AirPass travel is valid on flights marketed by American Airlines. Additional details will be added to this release note as they become available.

NOTE:Concur Travel will not support PlanAAhead® fares with the new program. These fares require purchase at least 7 days in advance and reflect a 25% discount off AAnytime fares by booking in Restricted (H) inventory. A $200.00 fee is automatically deducted for changes, cancellations, or no-shows after ticketing.

For more information on the AA AirPass program, visit the American Airlines AirPass website.


http://www.airpass.aa.com/

http://www.airpass.aa.com/


Client Notifications

Browser Certifications and Supported Configurations

Monthly Browser Certifications and Supported Configurations

The SAP Concur Release Notes – Monthly Browser Certifications document lists current and planned browser certifications. The document is available with the other SAP Concur monthly release notes.

The Concur Travel & Expense Supported Configurations – Client Version guide is available with the setup guides, user guides, and other technical documentation.

For information about accessing all release notes, browser certifications, setup guides, user guides, other technical documentation, and supported configurations, refer to the Additional Release Notes and Other Technical Documentation section in this document.

Subprocessors

SAP Concur Non-Affiliated Subprocessors

The list of non-affiliated subprocessors is available here: SAP Concur list of Subprocessors

If you have questions or comments, please reach out to: [email protected]


mailto:[email protected]

mailto:[email protected]

https://support.sap.com/content/dam/support/en_us/library/ssp/my-support/trust-center/sap-tc-04-0011.pdf

https://support.sap.com/content/dam/support/en_us/library/ssp/my-support/trust-center/sap-tc-04-0011.pdf


Additional Release Notes and Other Technical Documentation

Online Help – AdminsAny user with any "admin" role can access release notes, setup guides, user guides, admin summaries, monthly browser certifications, supported configurations, and other resources via online Help.



SAP Concur Support Portal – Selected UsersAccess release notes, webinars, and other technical documentation on the SAP Concur support portal.

If you have the proper permissions, the Contact Support appears on the Help menu. Click to access the SAP Concur support portal, then click Resources.

Click Release/Tech Info for release notes, technical documents, etc. Click Webinars for recorded and live webinars.


© 2020 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.


Date post:	29-Aug-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

Travel: August 2020 Release Notes · Web viewPreviously, when an API customer using Legacy OAuth...

Documents