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.
Environment
Incoming Emails, Mailbox Configuration / Filtering options
Resolution
When configuring a mailbox in Oracle B2C Service, you can list specific types of file attachments that will not be allowed with incoming email.
Each mailbox has two distinct fields, Discard MIME Types and Discard File Types. These fields allow you to specify types of files that will not be attached to an incident created from mail sent to the mailbox. Multiple entries must be in a comma-separated list or with a single value per line. To prevent incidents from being created for emails that have a *.exe or *.vbs extension, edit each mailbox and include *.exe, *.vbs in the Discard File Types field.
Preventing Incident Creation
Editing the Discard MIME Types and Discard File Types fields in the mailbox prevents the files from being attached to the incoming incident, but the incident is still created from the email -- minus the attachment. If you want to prevent the incident from being created as well, you can configure a rule to not create the incident based on contents of the subject or body of the email:
IF: Incident Source: Email If Incident.Customer thread matches regular expression bytes If Incident.Customer thread matches regular expression discarded If Incident.Customer thread matches regular expression application If Incident.Customer thread matches regular expression Attachment Then: Do not create incident.**
All of the IF statements should be joined by the AND connector. These words will all be present together in incidents generated with deleted attachments.
This rule should be placed first in your list of rules.
Note: Consider starting off with a rule that allows the incident to be created (minus the attachment) and assigns the incident to a specific group or sets it to the Solved status instead of not creating the incident. This allows you to review which incidents are coming in and are being affected by the rule to ensure that you are not preventing valid incidents from being created.