Search for existing answers to your product and support questions.
Familiarize yourself with our support site and learn best practices in working with our team.
Manage Service Requests, View and update service requests submitted by you and others in your organization.
Submit a new issue to our technical support team.
Oracle B2C Service insights from our Technical Support team subject matter experts
Browse resources to assist you in launching your implementation and ensure a successful go-live.
Access your OCI account.
Find product documentation for supported versions of B2C and documentation libraries for related service solutions.
You will have the tools to improve your customers' experience when you learn about all the things our products can do.
Find links for API documentation, Custom Processes, Customer Portal, and Agent Browser UI Extensibility Framework.
Explore how accelerators are designed to demonstrate how an integration scenario could be built using the public integration and extension capabilities of the Oracle B2C Service.
Prepare for a successful transition by reviewing upcoming release changes and enhancements.
Explore webinars, events, and feature kits to learn about B2C Service features, functionality, and best practices from the technical experts.
Oracle MyLearn offers a portfolio of free and paid subscription-based learning resources to help you gain valuable skills, accelerate cloud adoption, increase productivity, and transform your business.
Empower your team with the skills to implement, configure, manage, and use your applications with Customer Experience Cloud Training.
Our goal is to facilitate a friendly, supportive environment where members can easily collaborate with each other on solutions and best practices.
Ask and answer questions specific to B2C.
This is an exciting resource intended to help with your Oracle Service Cloud Analytics.
Share product improvement ideas and enhancement requests with Oracle Development, while collaborating with other Oracle customers and partners.
Update your phone number, email notification preferences, and severity 1 and severity 2 contact preferences.
View the contact managers within your organization.
Find contact information of the Technical Account Manager (TAM) and Client Success Manager (CSM) for your organization.
How is the language setting determined for incidents that are created via incoming techmail?
Environment:
Foreign Language, Email
Resolution:
For an incident created by techmail:
The language ID is set by language-detection software that uses the content from the message body and/or subject line. The language ID is set only if an interface of that language pack exists within your site. If language cannot be determined from the content or subject, then the language id is set to the language of the interface for the mailbox to which it was sent. Incidents generated for techmail processing errors will have the language id set to match that of the current interface. The interface for the resulting incident is not changed to match the interface where that language exists. If desired, create business rules to set the interface for these incidents to different values. The behavior for incoming emails and languages within the application functions as follows. Process message based on encoding which defines the language family. For example, ISO-8859-1 would be European language including English. Review the decoded text to identify the specific language, for example Dutch. Assign incident to interface of mailbox. Assign incident to language of email IF an interface of that language exists. In this case, the language would be English or Dutch if the incoming message is English or Dutch and the site has an English and Dutch interface. Assign incident language to the language of the interface for the mailbox to which it was sent.
The language ID is set by language-detection software that uses the content from the message body and/or subject line. The language ID is set only if an interface of that language pack exists within your site. If language cannot be determined from the content or subject, then the language id is set to the language of the interface for the mailbox to which it was sent. Incidents generated for techmail processing errors will have the language id set to match that of the current interface. The interface for the resulting incident is not changed to match the interface where that language exists. If desired, create business rules to set the interface for these incidents to different values.
The behavior for incoming emails and languages within the application functions as follows.
For incidents created via other methods:
If other incidents are created with no language specification, you can use Workspace rules if desired. Language can't be set in Business Rules. Example workspace rules are below. Note: Set Language is not a conditional choice in Business Rules. An example of an incident work space rule, could be something like the following based on a site with English and Dutch interfaces. Apply this rule when the editor loads. But only if interface = English interface and the language is not English or No Value Then set language to English. A second work space rule could manage all the rest of the interfaces and set the value to Dutch if the language is Not Dutch or No Value. In using Work Space rules, the language is not set at incident creation but the first time the incident is edited. The behavior for End User Questions is as follows.
If other incidents are created with no language specification, you can use Workspace rules if desired. Language can't be set in Business Rules. Example workspace rules are below.
Note: Set Language is not a conditional choice in Business Rules.
An example of an incident work space rule, could be something like the following based on a site with English and Dutch interfaces.
A second work space rule could manage all the rest of the interfaces and set the value to Dutch if the language is Not Dutch or No Value. In using Work Space rules, the language is not set at incident creation but the first time the incident is edited.
The behavior for End User Questions is as follows.
Another option to manually set the language of incidents, would be to add the language field to the Incident Multi-Edit work space. Then create a report which filters your incidents similar to the rules above. Then you could multi-select and change the language.