Connect an AI assistant
Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.
The catalog did not load. Refresh the page to try again.
Loading…
{{server.name}}
{{server.summary}}
{{server.documentCount.toLocaleString()}} pages Not published to this site
- Name
-
{{server.name}} - URL
-
{{mcpServerUrl(server.path)}}
| Tool | What it does |
|---|---|
{{tool.name}} |
{{part.text}}{{part.text}} |
How can we help?
Searching in {{docApp.searchFilterBySpecificBookTitle}}
Searching for:
{{docApp.searchResultFilteredItems.length}} results for:
{{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown.
Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
The utility provides a simple, safe and secure way to bulk-translate your Services, and associated Catalog Items, FAQs, Bulletins, Customer Feedback Questions and Sub Statuses. Translation of Sub Statuses requires Service Manager build of 2144 or above.
The tool is designed to run behind your corporate firewall and connects to your Hornbill instance in the cloud over HTTPS/SSL. So as long as you have standard internet access then you should be able to use the tool without the need to make any firewall configuration changes.
Installation Overview
- Download the architecture-specific ZIP archive
- Extract zip into a folder you would like the application to run from e.g. C:\Users\yourserviceaccount\servicetranslate\
- Open a Command Line Prompt as Administrator
- Change Directory to the folder containing the utility C:\Users\yourserviceaccount\servicetranslate\
- Run the command:
services_translation.exe -src="en-GB" -dst="it"
Configuration
Command Line Parameters
debug: true/false, defaults to false - Log extended debug information;src: The source language code to translate the records from;dst: The destination language code to translate the records to;getlangs: Return a list of supported languages and their codes into a file in the tool folder called languages.txt, then exits;version: Output the tools version number, and exit;creds: Defaults to false. Set to true to be prompted to input your instance ID, and you will be presented with the stored API key.
First Run
From version 2.0.0 of the Service Translation tool, when you first run the utility it will prompt you for the ID of your Hornbill instance (case-sensitive), and the API key (also case-sensitive) that will be used to authenticate the API calls back into Hornbill. This information will be encrypted, and stored locally on the client PC that will be running the tool. For each subsequent import run, the utility will decrypt your instance ID and API key, and will use those to make the API calls back into Hornbill.
NOTE - the encrypted instance ID and API key can only be decrypted on the computer, and by the user, that performed the encryption, so please keep this in mind when scheduling your imports.
Should you wish to use a different API key to what has been previously encrypted, just delete the import.cfg file from the folder where the import binary resides, and re-run your import from the command line inputting the Instance ID and new API Key as you would have on its first run.
API Key Rules
This utility uses (API keys):
- data:entityBrowseRecords2
- system:getLanguageList
- session:getApplicationList
- apps/com.hornbill.servicemanager/Services:smGetServiceDetails
- apps/com.hornbill.servicemanager:translateData
- apps/com.hornbill.servicemanager:translateAddLanguage
HTTP Proxies
If you use a proxy for all of your internet traffic, the HTTP_PROXY Environment variable needs to be set. The https_proxy environment variable holds the hostname or IP address of your proxy server. It is a standard environment variable and like any such variable, the specific steps you use to set it depends on your operating system.
For windows machines, it can be set from the command line using the following:
set HTTP_PROXY=HOST:PORT set HTTPS_PROXY=HOST:PORT
Where “HOST” is the IP address or host name of your Proxy Server and “PORT” is the specific port number.
Troubleshooting
Logging Overview
All logging output is saved in the log directory, in the same directory as the executable. The file name contains the date and time the import was run Service_Translation_20210202142114.log
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}