Do you need to translate your portal or other UI elements into multiple languages? Go beyond manual translation processes and into scalable and maintainable localization with NewRocket Translation Assistant. Don't settle for a single language UI or time-consuming localization efforts, deliver a better user experience with less time and effort.Get In Touch
NewRocket Translation Assistant supports the entire localization process in ServiceNow. It starts with setting up a translation scope, a declarative way of specifying what portals, catalog items, knowledge bases, and other records that you want to localize. Using this information, Translation Assistant will retrieve the localizable strings related to these areas and consolidate that information into a staging table. This makes it easy to see what is already translated and what remains to be done.
As your portal, catalog, and knowledge base change, you'll need a way to maintain your translations as well. Translation Assistant helps with this too, but giving you a convenient one-line business rule that you can add to any table to update your translation scopes as your system changes. Both new records and changed records are flagged for processing.
A translation scope is a declarative way to pinpoint exactly what you want to localize and what languages you want to target. This fine-grained control allows you to adapt the process to your needs while supporting a repeatable process. Specifying catalogs, knowledge bases, portals and their related records for localization is easy. Target any record in ServiceNow using custom scopes.
One of the challenges with localization in ServiceNow is that localized strings are stored in several different tables depending on what you are translating. Translation Assistant understands this and uses what is specified in the translation scope to scan the base record as well as the relevant system translation table to determine what translations already exist. It then consolidates this information into a staging table that provides context about the translatable string and the relevant translation if it exists. This consolidation accelerates the overall process.
Translating the static text in widgets and in other contexts can be challenging. If a developer doesn't have the discipline to add the UI message to the sys_ui_message table during development, the string could be missed during a traditional translation cycle. Translation Assistant overcomes this change by automatically extracting UI messages directly from widget templates and server scripts so developers don't need to take the extra step to add the strings to UI message table manually.
Change happens. Translation Assistant allows you to monitor for new and changed records that impact your translation efforts. These changes can be automatically captured and reflected in the staging records associated with one or more translation scopes. From there, the strings can be translated and synced back into the appropriate location to ensure that you are delivering the best experience for your users.