Busca respuestas existentes a tus preguntas de productos y soporte.
Familiarízate con nuestro sitio de soporte y aprende las mejores prácticas sobre trabajar con nuestro equipo.
Manejar Peticiones de Servicio. Ve y actualiza peticiones de servicio tuyas o de otros miembros de tu organización.
Reporta un nuevo problema a nuestro equipo de soporte técnico.
Explora recursos que serán útiles para poner en marcha tu implementación y asegurar un lanzamiento exitoso.
Accede a tu cuenta OCI.
Encuentra documentación del producto para versiones vigentes de B2C y bibliotecas de documentación para soluciones de servicio relacionadas.
Tendrás las herramientas para mejorar la experiencia de los clientes al aprender todo lo que nuestro producto es capaz de hacer.
Encuentra enlaces para la documentación de APIs, Procesos Personalizados, Portal de Clientes, y la Estructura Extensible de la Interfaz de Usuario del Navegador para Agentes (BUI).
Explora cómo los aceleradores son diseñados para demostrar cómo un escenario de integración podría ser construido usando integraciones públicas y las capacidades de extensión del servicio de Oracle B2C.
Prepárate para una transición exitosa al revisar cambios y mejoras próximas a ser lanzados.
Explora webinarios, eventos, y kits de características para aprender sobre las características, funcionalidades, y mejores prácticas para el Servicio B2C brindado por técnicos expertos en el área.
Oracle MyLearn ofrece un portafolio de recursos de aprendizaje basados en un modelo de suscripción gratuito y de paga para adquirir habilidades valiosas, acelerar la inclusión de la nube, incrementar la productividad, y transformar tu negocio.
Empodera a tu equipo con las habilidades para implementar, configurar, manejar, y usar tus aplicaciones con el Entrenamiento de la Nube para la Experiencia del Cliente.
Nuestro objetivo es facilitar un entorno amigable y solidario, donde los miembros pueden colaborar fácilmente entre ellos sobre soluciones y mejores prácticas.
Realiza y responde preguntas específicas a B2C.
Este es un recurso fascinante con el propósito de ayudar con el Análisis de la Nube del Servicio de Oracle.
Comparte ideas de cómo mejorar el producto y solicitudes de mejoras con el equipo de desarrollo de Oracle, mientras colaboras con otros clientes y socios de Oracle.
Actualiza tu número telefónico, preferencias de notificaciones por correo electrónico, y preferencias de contacto para incidentes de severidad 1 y 2.
Consulta los gestores de contactos dentro de tu organización.
Encuentra información de contacto del Gerente Técnico de Cuentas (TAM), y el Gerente de Éxito de Clientes (CSM) para tu organización.
Oracle B2C Service, Administration Console, Error Log
Resolution:
If a report fails when it is being executed, or after being queued, an error message will be displayed. You can see additional details about the error by going to the Configuration menu > System Configuration > Error Log. The log's record will contain the exact date and time when the error occurred.
You can use the Analyzer button to help determine if a report will be problematic.
The following principles can be applied to improve the performance of reports:
Additional Information: The items below also apply to improving report performance:
Editing Reports: When editing a report, review the configuration to remove unnecessary tables, filters, or output columns. If you have edited a report to remove filters or output columns, verify that all of the tables are still needed to define the remaining filters or output columns.
Accounts Table: Special consideration should be given to the Accounts table. If the only information you need from the Accounts table is the name of the Assigned To staff member, you do not actually need to include a join to the Accounts table.
For example, if your report is based on incidents, use the incidents.assign_acct_id field from the Incidents table to list the staff member's name as it is configured in their staff account. You do not need to use the accounts.full_name field from the accounts table.
Evaluating Types of Joins Used: When possible, use inner joins to join tables within the report. By default, tables are joined with an inner join. While it may be necessary to use an outer join in your report, when possible use the inner join to better restrict which records can be included in the report.
For example, when joining the contacts table to the incidents table, since a contact record is required for each incident, you can use an inner join to relate the two tables. That is, for each incident there is a corresponding contact record which allows you to use the inner join.
For more information on inner and outer joins, refer to Answer ID 1839: Types of table joins used with reports.
Open Report Without Prompting for Search Parameters: When an initial search is performed for a report, the query is run when the report is first selected. Depending on the default settings for the fixed and run-time filters, the initial search may result in querying an entire database table such as all of your incidents or contact records which may be a significantly large number.
Therefore, only enable the initial search if you know that the number of records to be returned based on the filters is fairly low, such as fewer than 100 records or so.
To do so, edit the report, navigate to the Options in the top ribbon and enable or disable the Open Report Without Prompting for Search Parameters.
Auto Refresh Option: Reports should only use the auto-refresh feature if there are adequate fixed or run-time filters in place so that a limited number of records are returned each time the query is run.
The auto-refresh feature is enabled or disabled from Options button on the report's ribbon, while the report is opened in edit mode, i.e. Automatically refresh report at a regular interval.
Using Fixed Filters: Where possible, use fixed filters to restrict records to a specific value or range. For example, reports that list all of today's solved or updated incidents could use a fixed filter for the status and last updated fields. For sites with multiple interfaces, consider adding fixed filters for the interface or language so that records from only that interface are accessible.
Set Specific Defaults for Run-Time Filters: In cases where a fixed filter is not desirable, you can still set a preferred default value or range for the run-time filters. For example if your report uses the date created for an incident as a filter, set the default range to be within the last week or the last month so that the default search will return the most recent incidents that are typically of greatest interest.
Including specific default values for your run-time filters reduces the number of rows that the query needs to evaluate. You can also include default search values with text run-time filters such as "enter search text here". This forces staff members to type in what they are actually looking for before doing a search.
Train Staff to Use Filters Effectively: A report can be as streamlined as possible, but still have problems if a user performs a search with all the run-time filter values selected and no specific search text entered. That is, if the staff member sets the run-time filters to search all available options and does not search by specific search text, the query will still be evaluating potentially thousands of rows that are not necessarily of interest.
Thus, part of improving report performance is to train staff members to use search filters responsibly, and to limit the reports which staff members can access. Some staff members tend to use reports in an attempt to get a general overview of records in the database rather than returning a small number of records in order to manage them.