This article is intended for Salesforce administrators responsible for installing and configuring the Language I/O Article Translation for Salesforce. Estimated time to complete: 30 minutes.
Before installing Language I/O Article Translation, the following Salesforce settings are required:
- For each profile that will have the package installed, it needs to have Manage Salesforce Knowledge enabled under Administrative Permissions.
- The following permissions are also required: Article Translation - Edit, Article Translation - Publish, Article Translation - Submit for Translation under General User Permissions.
- Each user who will use the app needs to be a Knowledge User in User Details.
- Create a queue for Knowledge Article Version object that will be used to hold translated draft articles.
- Optionally, create another queue that holds completed translations.
- Knowledge settings should be enabled with multiple languages as illustrated below.
Installation of the Language I/O Article Translation
- Contact Language I/O Support at firstname.lastname@example.org to get an account setup in our database. Once an account is created on our side, you will be sent the credentials and API Endpoint url. This will be used later in the post-installation process.
- Install the package from the latest URL below depending on whether you are using a Sandbox or Production org. Begin by logging into the instance of Salesforce you wish to use. Visit the install link in the same browser and select "Install for all users". The current release is 1.14.
- Sandbox org:
- Production org:
Setting up Named Credentials
Using Named Credentials with Salesforce ensures security and authentication are friction-free by simplifying the critical task of securely storing login details and authenticating with external APIs. Language I/O Article Management leverages Salesforce's Named Credentials extensively, which allows per org, per profile, as well as per user-level endpoints and credentials for flexible and powerful Language I/O omni-language translation integrations.
After receiving your credentials, from Setup enter Named Credentials into Quick Find box, select Named Credentials, then click New Named Credential. You can do this from either Classic or Lightning Experience.
Give it a label and name. The name will be used later in our Custom Settings, in order for our Chat app to know which credentials and endpoint to use to communicate with our backend.
This is also where you enter the credentials and endpoint you received earlier. From Authentication section, choose Named Principal as the Identity Type, Password Authentication as Authentication Protocol, and then enter the username and password. For the endpoint's URL, unless instructed otherwise, you would normally use https://golinguist.com/linguistnow/resources.
Click "Save" to save the new named credential.
Before using Language I/O Article Translation for Salesforce, you must create a org-wide default custom setting named Language I/O Articles Settings.
From Setup/Custom Settings, click on Manage to the left of Language I/O Articles Settings.
Create "New" at the root level to creat a new Default Organization Level value. If you are upgrading from a previous version, click "Edit".
The following figure shows a basic configuration. Named Credential should match the name of the Named Credential created earlier. Enter the API Name of the queues where all translation drafts and completed translations are saved.
Create a visualforce tab
From Setup, enter "Tabs" in Quick Find. Click on Tabs. Create a new Visualforce Tab.
Select HelpProjects as the Visualforce Page. Enter a Tab Label and select a Tab Style. Click Next to set the profiles where the tabs are visible. Click Next to make the tab visible to any apps. Finally click Save.
After the visualforce tab has been created, you can make it visible to the user by including the tab to your favorite app, e.g., Sample Console.
When you first run the app, an error will appear to ask for a url to be added to the Remote Site Settings. Copy the prompted domain name (e.g. https://somedomain.com). Then go to Setup/Remote Site Setting. Add the copied domain to the remote site settings. Run the app again.