| This post will provide updates on the latest features available in Localization Workspace as well as tips and tricks to help you get the most out of the Workspace. Make sure to keep coming back to read more. |
ServiceNow's December 2025 release
The December 2025 release has just gone live and with it, Localization Workspace has been enhanced with new exciting features to help customers automate and accelerate both their implementation and translation management processes. Check out this video for a summary of what has been released.
The features listed below are now available as part of the latest release:
1. Guided Setup
2. Configuration Hub
3. Language Groups
4. Bulk deselect and Enhanced search
5. Due dates
Before we look at each feature, we’ve made it even easier to access Localization Workspace from your instance; all you need to do is go to the Workspaces tab at the top of your instance and select Localization Workspace from the list of workspaces available.
1. Guided Setup
The Guided Setups have been designed to walk admins through the configuration tasks that are necessary to correctly setup Localization Framework, including Dynamic Translation, as well as Localization Workspace, in a clear, easy-to-follow structure.
To access the Guided Setups, navigate to All; in the search bar enter Guided Setup and scroll to Localization Framework or Localization Workspace Guided Setup.
Opening the Localization Workspace Guided Setup displays the different steps required to best configure Localization Workspace so that you can take full advantage of what it has to offer.
Each step is divided into different tasks, which also helps with progress tracking. You can also leave the guided setup process at any time and come back to where you left off.
When opening an individual task, for example “Configure Translation Providers”...
...clicking on “Set up translation providers” will take you to the exact area of Localization Workspace where the configuration can be completed.
2. Configuration Hub
When configuring Localization Workspace, there is a dependency on correctly configuring other applications across the ServiceNow platform, including Localization Framework, and Dynamic Translation should you want to use machine translation.
The introduction of the new Configuration Hub centralizes all these configurations into one interface, meaning that admins and Localization Managers no longer have to switch between different apps.
To access the new Configuration Hub, open the workspace from the Workspaces tab and select the hub icon on the left panel.
More information about the Configuration Hub is available in the product documentation.
3. Language Groups
With Language Groups, requesting the same multiple languages for content on a regular basis has just become easier.
It is now possible to create groups of languages, which removes the manual task of having to add individual languages each time you want to submit a translation request.
To set up language groups, open the workspace from the Workspaces tab, select the Language setup icon on the left panel, select the Language Groups tab then select New.
More information about Language Groups and how to create them is available in the product documentation.
💡 TIP: you first need to set up Language Providers before creating Language Groups.
4. Bulk deselect and Enhanced search
In the scope phase of the translation process, Localization Workspace displays and selects all untranslated and partially translated content by default. Prior to this release if a requestor wanted to deselect content items so that they are not sent for translation, the items had to be removed one by one. It’s now possible to deselect all content items and select only those that need to be translated, cutting down the time needed to finalize what goes into a translation job.
We’ve also made it easier to search for specific content items that appear on the scope screen.
💡TIP: to deselect content items in bulk and to search for specific content items, select the filter icon on the scope screen to enable the different filters.
To deselect all content items from a request, select the check box which is displayed beside the word Filter.
💡TIP: To search for a specific content item, in the “Translation Item” column, set the operator to “Operator contains.” This will allow you to search for a word that is in the title of the content item(s) and select them for translation.
More information about using the bulk deselect feature and enhanced search when requesting translations is available in the product documentation.
5. Due dates
Our final new addition allows requestors to set due dates from the estimate screen to stay on top of all requests.
A default due date will appear on the screen. If you choose to send your translations to a regular language service provider, the due date will be set to two weeks, if you select machine translation as the language provider the due date will be set to end of day.
Opening the calendar allows you to change the due date to a later date. In this version it’s not possible to change the due date to an earlier date but stay tuned for more on that.
More information about due dates is available in the product documentation.
🤔 Did you know?
You can set email notifications to be notified when a translation job is late so that you are always on top of requests, can identify potential bottlenecks in your processes and drive any follow-ups where needed.
‼️Tell us what you think‼️
We’d love to hear your feedback on how these capabilities will help you. Share your experience and insights in the comments.
A look at our Q3 launch
Back in May, ServiceNow launched Localization Workspace; a translation command center designed to simplify the management of multilingual content and translation tasks within the ServiceNow platform.
Localization Workspace was released to help customers efficiently manage multilingual content, as well as alleviate operational pain points by removing:
- bottlenecks that require expertise from developers or localization subject matter experts
- manual processes that add repetitive, time-consuming tasks which increases time-to-market
- limited visibility into translation job progress
- inconsistent user experiences across different languages and channels and
- barriers to scalability
Since the initial launch, two new features were added as part of the July release:
1. Real-time job status: to monitor the status of translation requests in real-time from the Localization Workspace home screen
2. Dynamic artifact detection: to submit your own custom artifacts for translation through Localization Workspace
This first post will focus on "Real-time job status" and will provide a tip on how to set alerts to be notified of completed jobs.
Real-time job status
When Localization Workspace first launched, translation jobs only had two states: Draft and Submitted. Now you can see the real-time status of translation requests directly from the Localization Workspace home page. In addition, the status of translation requests in Localization Workspace matches the status in Localization Framework allowing for consistency across both platforms.
For example, the addition of the “Complete” status shows you that your translation request is ready.
There are 5 different translation request states available in Localization Workspace:
|
Translation state in Localization Workspace |
Description |
Corresponding state in Localization Framework |
|
Draft |
The translation request has been saved but not submitted. |
Draft |
|
Submitted |
The translation request has been moved to Localization Framework, where the project and its tasks are being created. |
N/A |
|
In progress |
The translation project and its tasks have been created in Localization Framework. |
In progress |
|
Complete |
The translation project is complete and all the tasks within the project are completed and closed. |
Closed Complete |
|
Closed: Project Incomplete |
The translation project is incomplete when at least one of the tasks within the project has been marked as closed but isn’t complete. |
Closed Incomplete |
Seeing that a translation job is complete on the home page lets you know that the job is ready, but it means that you still need to monitor the translation queue to find out when your translations are available.
However, what if it was also possible for requestors to be alerted when a translation job is completed?
Now, it is!
With the addition of the new translation status, admins can set up email notifications so that content owners or translation requestors can receive an alert that will let them know when a translation job has been marked as complete.
Watch this video to learn more on how to set up email notifications to be alerted when a translation job has been completed.
Take it further
Create notifications for different steps of the translation process to increase productivity and remove manual checks.
Useful links
- Download Localization Workspace directly from the app store
- Product documentation: Localization Workspace
- Product documentation: How to create general email notifications