This repo contains everything you need to get started with Localization in ServiceNow with resources and code samples for beginners.
Where should I even start?
The Phases of Localization in ServiceNow:
- Before you Start - Plan the Localization Strategy
- When you Start - Find Missing Translations
- Somewhere in the Middle - Establish Design and Development Standards
- After Go-Live - Test the Localization Implementation
- In the Future - Maintain the Localization Implementation
Here's the link to our Knowledge CreatorCon 2022 Session: Five things I wish I knew before attempting to localize my scoped application so you can learn more about these different phases! [LINK] (You can also check out the slides here. [LINK])
While the slides presented a high level overview of these different localization phases, the following contents are intended to go more in depth with additional explanations and examples.
Our tool: Clear Skye I18N Scanner Utility - We are using this to help us dig up all those pesky strings in our scripts, but we made it after we recorded our session so we didn't get to talk about it. Oh well - now we have a topic for next year!
- Debug Translations - learn how to find missing translations.
- FetchCode - learn how to use the FetchCode tool to search for hard-coded strings.
- Locate translatable strings - learn how to create stub translation records needed for custom translations.
- Design and Development Standards - follow these best practices to make it easier to localize custom strings.
- Custom Translations - learn how to translate custom strings.
To learn more, check out:
- Custom translations
- Employee Center Academy: Localization and Multi-language Support
- Hard-coded strings are bad, mmmkay
- How do you choose what languages to offer?
- In-Platform Language Support Guide
- Return a message in a specific language, gs.getMessageLang()
- Solution design is just as important as translations
- Support your globalization with well-planned localization
Have something you think should be included here? Let us know!