Published at: 2026-09-17
Example: US sales organization rollout acceptance
This page applies the internationalization implementation and acceptance framework to one scenario. It shows how to turn the general method into test roles, data, and acceptance steps for a specific sales organization. Other organizations must adapt the test data to their countries, business objects, and processes instead of copying it unchanged.
Scenario objective
This template is for a sales organization that works primarily in the United States and collaborates with its China headquarters. The objective is to prove that language, time zone, regional format, geographic data, addresses, currencies, multilingual business data, notifications, and BI work together, not merely that the administrative switches were saved.
Test roles and data
| Item | Suggested test value |
|---|---|
| Administrator | One system administrator responsible for enterprise configuration |
| US salesperson | One employee using English, the time zone of the target US state, and the United States regional format |
| China collaborator | One employee using Simplified Chinese and China Standard Time |
| Account | A US test account with an English name, a USD opportunity, and a US Dynamic Address |
| Time | A date and time close to midnight for either China or the United States, including a daylight saving time example |
| Currency | The enterprise base currency and USD, with a test exchange rate maintained according to the enterprise’s finance policy |
Do not use a real account, phone number, or email address in test data.
Administrator configuration path
- Confirm that required capabilities, including multiple languages, multiple time zones, regional formats, and multiple currencies, are enabled. Automatic device time-zone synchronization and data-level multiple-language support are generally available and do not require a separate rollout request.
- In Country/Region Management, confirm that the United States and the target states, cities, and other administrative divisions are available. Verify that the administrative-division import and export controls appear.
- Set the enterprise default language, time zone, and regional format, and assign English to the US salesperson.
- Maintain English names for required objects and fields, such as Account, Opportunity, and Product. Enable the required business fields in Data Translation Settings.
- Set the base currency, enable USD, and maintain a test exchange rate. Add the currency and exchange-rate fields to target object layouts.
- Configure the form order, display labels, postal-code rules, and text composition of the US Dynamic Address format.
End-to-end acceptance
Language and business data
- Have the US salesperson sign in in English and create a US account, contact, and opportunity.
- Confirm that menus, objects, fields, layouts, buttons, and business-type names appear in English.
- Maintain Chinese and English business values for an account or product. View them as both the US salesperson and the China collaborator.
- Search using the current-language value and check lists and details. Confirm that a fallback display value is not treated as a current-language search value.
- Edit a record, then review both old and new change-history entries. Confirm that later language changes do not rewrite historical entries.
Time zone and regional format
- Have both users view the same date-time record. Confirm that it represents the same instant and appears in each user’s time zone.
- Use examples close to midnight and a daylight saving time transition. Check the date boundary, notification time, and formula conditions.
- Confirm that date order, 12-hour or 24-hour time, decimal points, and thousands separators follow the United States regional format.
Addresses, currencies, and exchange rates
- Create a US account address. Confirm that state, city, street, postal code, and other fields follow the configured order and validation rules.
- Save the address and check the formatted address in lists, details, exports, and downstream integrations.
- Create a USD opportunity and verify the original-currency amount, exchange rate, and base-currency amount. Then check summary fields and BI reporting rules.
- Disable a currency or address format used only for testing. Confirm that historical records remain visible while the option is unavailable for new records.
Notifications and BI
- Trigger a CRM notification and verify its standard translation. If the Automatic Translation rollout for CRM notifications is enabled, verify that switch and behavior as well.
- Republish the BI dashboard after translating names. Confirm that the new language takes effect without deleting the report.
[!NOTE] This page provides an operational baseline for rollout acceptance. Select the checks required for your business scope and maintain actual results and issue records in your enterprise’s project acceptance record.