Before you begin: An overview of the Language I/O Case installation process
The purpose of the article is to give a brief overview of the different steps to install Language I/O Case for Salesforce in your Salesforce instance.
Installation overview
Each step that involves an action on your part is explained in a dedicated article, linked below. The process is as follows:
- First, make sure that your instance is ready for the install process (See the Prerequisites section below). This step is crucial to make sure that you have everything you need for the installation.
- Install the Language I/O application.
Installing the Language I/O application in the Salesforce instance. - Create (or reuse) a Named Credential.
Named Credentials are used for authentication. You can reuse existing Named Credentials for certain Language I/O applications - Configure the Language I/O application.
Configure Salesforce for the Language I/O application. Some steps are optional. - Configure your Custom Settings.
The Language I/O application is highly customizable. In this step you configure mandatory settings as well as optional settings according to your needs. - Configure your desired Public Settings.
In the same section, finish configuring your custom public settings for the Language I/O application. - Finish the configuration:
Preventing installation issues
Please read the Installation troubleshooting guide to prevent the most common issues that may happen during installation process.
If you have any question about this process or if you require assistance, contact your Customer Success Manager.
Prerequisites to the installation
Credentials
- Contact Language I/O Support at support@languageio.com to get an account set up for your company. Language I/O will send you a set of API credentials. You must have these credentials to complete the Create (or reuse) a Named Credential step.
- If you use human translation, Language I/O needs the username, password, and security token for an account that has the necessary permissions to modify cases and objects used by cases, such as case comments and email drafts. This set of credentials requires at least API access to push translations from the Language I/O server back into Salesforce. Once you complete the app installation, you can remove regular login permissions from these credentials for security purposes.
Note: To add a new user in Salesforce, see this Salesforce documentation. If you do not have permissions to add a new user to your org, ask your Salesforce administrator to create one.
Preparing Salesforce
Enabling email-to-case
- In the Quick find box, search for "email-to-case".
- Make sure that "Enable Email-to-Case", "Enable HTML Email" and "Enable On-Demand Service" are checked.
- Click Save.
- On the same page, find the box labeled "Routing Addresses" and click New.
- Fill in the required fields.
- "email address" is the address from your organization that will be receiving the emails and routing them into Salesforce. Check with your administrator if you are not sure of which address to use.
- Click Save to complete this setup.
- (Optional) Send an email to the email address to test the email case service.
Creating a Lightning Record page
See Creating a Lightning Records page in Salesforce.
Setting up the Language field
- Go to Object Manager > Case > Fields & Relationships.
- If the "Language" field does not exist, click New and set up a new field with the settings below:
(Click to enlarge)
User permissions for Human Translation
This step is optional and only required if you will use Human Translation.
Set the necessary user permissions to allow Language I/O to connect to your instance:
- All objects installed with Language I/O Account
- Case
- CaseComment
- EmailMessage
- Name
- OpenActivity
- Task
- Email to Case for some features.
Note: To add a new user in Salesforce, see this Salesforce documentation. If you do not have permissions to add a new user to your org, ask your Salesforce administrator to create one with the permissions listed above.
Comments
0 comments
Please sign in to leave a comment.