Skip to content

Update UPS API timeouts and strengthen PATCH vs PUT guidance#1786

Open
smrithijayarajan wants to merge 1 commit intoSAP-docs:mainfrom
smrithijayarajan:update-ups-docs-for-sap
Open

Update UPS API timeouts and strengthen PATCH vs PUT guidance#1786
smrithijayarajan wants to merge 1 commit intoSAP-docs:mainfrom
smrithijayarajan:update-ups-docs-for-sap

Conversation

@smrithijayarajan
Copy link
Copy Markdown
Contributor

Follow-up to PR #1775 based on team feedback from Ravi and Matt.

Changes Made

Timeout Updates:

  • Changed from 240 minutes to 120 minutes (60 minutes in CCPS environments)
  • Removed outdated future plans note

Language Cleanup:

  • Removed 'please reach out to us with provisionId' text per team feedback

PATCH vs PUT Guidance Strengthened:

  • Changed 'minimize error rates' to 'minimize data loss risk' (more accurate)
  • Rewrote Operations Best Practices section with explicit guidance:
    • PUT only for initial user creation (or intentional full replacement)
    • PATCH for ALL incremental user updates
    • Warning that PUT overwrites user and removes all previous edits
    • Emphasis on data loss risk for enterprise customers

Context

These updates address feedback from internal team discussions:

  • Ravi: Correct timeout values (120 min standard, 60 min CCPS)
  • Matt: Strengthen PATCH guidance with data loss warnings

Files Changed

  • (-8 lines, +3 lines)

cc: @sap-alex-oliveira (reviewer of original PR #1775)

- Update timeout from 240 minutes to 120 minutes (60 in CCPS)
- Remove 'please reach out to us' language and future plans note
- Change 'minimize error rates' to 'minimize data loss risk'
- Strengthen PATCH operations guidance per feedback:
  * PUT only for creation, PATCH for all updates
  * Warns that PUT overwrites and removes previous edits
  * Emphasizes data loss risk for enterprise customers

Follow-up to PR SAP-docs#1775 based on team feedback from Ravi and Matt.
@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented Apr 30, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Smrithi Jayarajan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@smrithijayarajan
Copy link
Copy Markdown
Contributor Author

Please don't merge until Ravi Laudya approves. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants