Fix: Add missing schemas field to SCIM2 Bulk PATCH operations for all affected versions (Product IS issue #24647)

[wso2-engineering-bot]

This PR was automatically generated by Claude AI.

• Issue: Wrong sample payload metioned in Bulk User Update API product-is#24647
• Type: Documentation / Bug
• Summary: Added the missing schemas field with value "urn:ietf:params:scim:api:messages:2.0:PatchOp" to the SCIM2 Bulk User Update and Bulk Group Update API request payloads. This field is required according to RFC 7644 for PATCH operations within bulk requests.
• Affected Versions: All versions (5.11.0, 6.0.0, 6.1.0, 7.0.0, 7.1.0, 7.2.0, next) - The fix was applied to the shared include file (en/includes/apis/scim2/scim2-batch-operations.md) which is used by all versions.
• Changes Made:
  1. Added "schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"] to the data object in both User Update PATCH examples
  2. Added "schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"] to the data object in both Group Update PATCH examples
  3. Added documentation for the schemas parameter in the Data parameters section for both Update users and Update groups operations
• Verification: mkdocs build passed successfully for version 7.2.0

Summary by CodeRabbit

• Documentation
  • Improved SCIM2 batch operations documentation with clarified requirements for PATCH requests
  • Enhanced consistency and readability across bulk operations examples
  • Minor text refinements for better clarity

[CLAassistant]

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.

---

wso2-engineering-bot 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.}

[coderabbitai]

Walkthrough

Adds the "schemas" field with PatchOp schema to SCIM2 bulk operation PATCH request examples and documents this required parameter in data tables. Includes minor text corrections and ensures consistency across user and group operation demonstrations.

Changes

Cohort / File(s)	Summary
SCIM2 Bulk Operations Documentation en/includes/apis/scim2/scim2-batch-operations.md	Adds "schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"] to PATCH request examples for both users and groups bulk operations; documents the schemas field requirement in data-parameters table; applies minor text fixes for grammar and formatting consistency.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Multiple homogeneous updates (schema field additions) across related sections suggest consistent pattern
• Documentation changes are straightforward and low-risk
• Minor text corrections are trivial to verify
• Primary focus: confirming schema URIs are correct and documentation accurately reflects API requirements

Poem

🐰 With whiskers twitched and paws in air,
I hopped through schemas everywhere,
PatchOp fields now crystal clear,
Bulk operations bright and dear,
Documentation hops with care! 🎉

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is mostly complete with issue link, type, summary, affected versions, and changes made. However, it lacks required sections: Test environment, and Security checks with checkboxes.	Add the missing template sections: specify test environment (JDK, OS, browsers) and complete the Security checks checklist items.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding missing schemas field to SCIM2 Bulk PATCH operations, with issue reference for context.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fixing-product-is-issue-24647-1762949557

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bb37e6d and 2637a83.

📒 Files selected for processing (1)

• en/includes/apis/scim2/scim2-batch-operations.md (7 hunks)

🔇 Additional comments (4)

en/includes/apis/scim2/scim2-batch-operations.md (4)

290-290: RFC 7644 compliance: schemas field correctly added to all PATCH operations.

The addition of "schemas":["urn:ietf:params:scim:api:messages:2.0:PatchOp"] to both user and group PATCH operation data blocks addresses the documented RFC 7644 requirement. The changes are consistently applied across both the user update (lines 290, 312) and group update (lines 879, 898) examples.

Also applies to: 312-312, 879-879, 898-898

---

402-416: Documentation accurately reflects the required schemas parameter for PATCH operations.

The new Data parameters table rows (user: lines 409–416; groups: lines 1003–1010) properly document the schemas field as Required and correctly specify the PatchOp schema URI. Descriptions align well with the examples provided above them.

Also applies to: 996-1010

---

421-421: Minor text improvements enhance clarity.

Changes from "data" to "data's" (user: line 421) and "user group" (group: line 1015) improve grammatical correctness and specificity. The phrasing now more accurately describes what the operation modifies.

Also applies to: 1015-1015

---

428-428: Link text consistency normalized across user and group operations.

Both sections now reference "SCIM2 Patch Operations" consistently (user: line 428; groups: line 1022), improving readability and reducing minor text inconsistencies.

Also applies to: 1022-1022

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}