- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 02-03-2021 10:28 AM
At the Community sometimes the question arises how to translate the Workspace Homepage especially the labels of the CSM Home Page:
The good news is that all labels on that page are just labels which can be configured easily if you know how and where and this article demonstrates how to this.
At Workspaces single pages such as the Homepage are called Landing Pages. And for creating and layouting a Landing Page ServiceNow offers the so-called UI Builder. Unfortunately, the UI Builder is quite hidden and not accessible via the Application Explorer.
So therefore navigate to Workspace Experience > Landing Pages and open the record "CSM Landing Page (enabled for UI Builder)":
In case your current Application Scope is not "CSM Workspace" the existing Landing Page was built in, you have to click on "To edit this record click here":
Now the button "Open in UI Builder" becomes visible and you can click on it:
At UI Builder you will be informed that the current page cannot be modified and thus a copy has to be created. So click on "Copy"
In the following dialog modal it is essential to choose the correct Application Scope (for example "Global" or the scope from a custom application) and "None (default)" at choice field "Protection":
After clicking on "Create Copy" the UI Builder loads:
To have more space on the canvas you can collapse the left panel. To change one of the labels (except the page label "My Workspace") click on of the nested page component and rewrite the label in the configuration panel on the right hand.
After translating all labels don't forget to save and activate the page and then reload the complete Workspace (STRG+F5). You should see now your modifications:
You may wonder how the workspace knows to load your new page and not the existing one. For a better understanding go back to the list of all Landing Pages and have a look on the values at the "Order" column:
Both CSM Landing Pages are active but the recently created Landing Page has a "Order" value of "0" and therefore takes precedence over the existing Landing Page.
Last step is to adjust the page header "My Workspace". To do this open the Landing Page in edit mode and select the "Default view":
Another field becomes visible where you can customize the label for the page header:
Save and reload the Workspace.
- 5,186 Views

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Maik,
the article is pretty descriptive and understandable! Thanks a lot!
I managed to translate the widgets' names, but have overwritten the English version.
I believe I need to change the type of the string into "translated text" for the Label field in the table, where these values are being stored.
The problem it that, I can't find this table.
Thanks in advance,
Kind Regards,
Anna Maksymova
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi
when you say, you "have overwritten the English" version, does this mean you did not create a page copy as described?
If so, you can change back the label texts without problems.
And to answer your questions: The label text values are not stored in any table but in payload fields deep, deep in the platform.
Kind regards
Maik

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi,
no, I do have created the copy of the landing page:)
What has been overwritten (or hard-coded) is the label name of the widgets.
I need the English version stay for the English version of the instance, and the German text be shown, when the language is changed to German in the settings.
But now for both languages only German is being shown.
So, do I understand correctly, that the translation can be only hard coded in this case?
Or is there another possibility?
Maybe one can set different Landing pages be shown for various Languages?
I have tried to translate one of the widgets in the System UI -> Messages, but it didn't work.
BR,
Anna
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi
for the hard coded UI Components the translation works as usual. But for the manual entered text values on a landing page there is no localisation possible as the values are stored completely different (in payload fields)
Kind regards
Maik

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi,
that's a pity.
Thank you for the clarification & help!
BR,
Anna