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.
Why am I being prompted to Save when closing a record I have not made any changes to?
Environment:
Workspaces
Issue:
Our agents sometimes open a record and then close it without making any changes. However, they still receive a prompt to save their changes:
Resolution:
The cause for this behavior is due to a change being made to the record. If you have opened a record such as an incident, contact or answer then immediately close the record and are prompted to save, this can be due to one of the following reasons.
1. Workspace Rules
The workspace being used by your staff account to load the record may contain a rule to change the value of a field on the workspace under certain conditions such as when the record is loaded.
2. HTML Tidy - within answer workspace
If you experience this behavior with answers and have ruled out workspace rules, it is possible that the Tidy utility may be repairing the source code of the answer content. For more information regarding Tidy, please see Modifications to the HTML source of documents.
3. Account Signatures with Default Response Thread - within incident workspace
Another option is that the agent has an Email Signature associated with their account. In the standard incident workspace, the Response thread opens by default when editing an incident. Where the staff account has a signature, that value is automatically added within that Response thread. This is seen as making a change. As a result, if the agent then tries to close the incident, they will be prompted to save that change.
4. Incident has an uncommitted response.
If an incident response thread is saved without being committed/sent then later, if the incident is opened and closed without any changes it will prompt asking to save changes.
5. Agent assigned to solved incident is transferred to a different group.
Incidents are assigned the group id the agent is assigned to, but if the agent is transferred to a different group all solved incidents remain in the old group the agent was assigned to. When the incident is later opened and closed without changes it will ask to save due to the new group the agent is now part of.