@W-20874526 - Integrate Order History with OMS

[sf-deepali-bharmal]

Summary

This PR updates the Order History page to support displaying order data from Salesforce Order Management (SOM). When orders are ingested into SOM, the page now correctly displays OMS-specific data including order status and shipping address information.

Changes

order-history.jsx

• Added expand: 'oms' parameter to useCustomerOrders hook to fetch OMS data
• Updated order status display to fallback to omsData.status when ECOM status is not present
• Updated shipping address name to use firstName + lastName with fallback to fullName (OMS uses fullName instead of separate name fields)

orders.test.js

• Added createMockOrder and createMockOmsOrder test factory functions for consistent mock data
• Added OMS/SOM Integration test suite for Order History with tests for:
  • ECOM order status display (order.status)
  • OMS order status display (omsData.status)
  • ECOM shipping address (firstName + lastName)
  • OMS shipping address (fullName)

Testing

• All 32 tests passing

Related

• Companion changes for Order Details page in PR @W-20874529 - Integrate PWA Order Details with SOM/OMS #3573

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• This PR updates the Order History page to support displaying order data from Salesforce Order Management (SOM)

How to Test-Drive This PR

• Integrate your ECOM site with SOM Org and place and order. Once your order is successfully ingested to SOM, load Order History page from PWA.

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[cc-prodsec]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sf-madhuri-uppu]

Can there be a case where fullname might not be populated?
If it always exists, it'd be cleaner to directly use it instead of a combination of firstName, lastName and further checks.

[sf-deepali-bharmal]

From what I am seeing FullName is always there. But I would like to not change the default behaviour late in the release.