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.
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 can Thread Translation be configured to include the required OCI compartment ID when the External Object and integration connection tests are successful, but language detection and translation fail when used within an actual thread?
Environment:
Oracle B2C Service External Objects and Integrations
Thread Translation
Issue:
External Objects and integration connections have been configured for Thread Translation, and the Thread Translation feature has been enabled and configured in AI Studio.
Testing the External Objects and integration connections using the Test Connection option returns the expected responses. Language detection and translation also work correctly when tested through the External Object test page because the required OCI compartment ID can be included in the test payload.
However, language detection or translation does not work as expected when invoked from an actual thread.
The request payload generated by the delivered Thread Translation functionality does not include the required OCI compartment ID.
Resolution:
Use a console extension to intercept the Thread Translation request and add the required OCI compartment ID to the request payload.
In the Customizations tab, configure the action name for the ConvertRequest Extensibility Action. The same action name must then be registered by the console extension.
For example, if the action name is ociRequest, the extension can transform both translation and language-detection requests as follows:
ociRequest
ORACLE_SERVICE_CLOUD.extension_loader .load("Global Extension", "1") .then(function(extensionProvider) { extensionProvider.getGlobalContext().then(function(globalContext) { globalContext.registerAction("ociRequest", function(param) { var transformedRequest; if (param.translationType === "TRANSLATION") { transformedRequest = { payload: { documents: [ { key: "1", text: param.text, languageCode: "auto" } ], targetLanguageCode: param.targetLanguageCode, compartmentId: "<compartment id>" } }; } else if (param.translationType === "DETECT_LANGUAGE") { transformedRequest = { payload: { documents: [ { key: "1", text: param.text } ], compartmentId: "<compartment id>" } }; } return transformedRequest; }); }); });
Replace <compartment id> with the OCI compartment ID required by the language service configuration.
<compartment id>
The extension adds the compartment ID to the generated payload for both:
TRANSLATION
DETECT_LANGUAGE
Also ensure that the appropriate profile has access to the console extension. Without profile access, the extension will not be executed for the affected users.