Skip Navigation
Expand
Inlay getConfigs error
Answer ID 10567   |   Last Review Date 07/24/2019

Why am I getting a getConfigs error for my inlay?

Environment:

B2C Service Chat, Customer Portal (CP)
Oracle B2C Service

Issue:

Error received:

> getConfigs: request failed > {readyState: 4, getResponseHeader: f, getAllResponseHeaders: f, setRequestHeader: f, overrideMimeType: f, ...}

Request failed error image

Resolution:

If you are getting the getConfigs error in the DevTools (To view DevTools in your browser you have to hit F12 then go to the Console tab) for a site that has inlays implemented this could be due to one of the following.

  1. The Customer Portal (CP) version
    If the CP version is CPv2 then you will get this error. The CP version needs to be 3.x in order for the inlays to be used on the site. If this is the case you will need to migrate CP to a supported version.

    See Customer Portal versions associated with Oracle B2C Service for steps on how to check your CP version.
     
  2. The CX version
    The OIT_CORS_ALLOWLIST*
    If this configuration value is set to "*.", blank or if you have for example <*.your_domain.com> then you will get this error. For the <*.your_domain.com> the getConfigs will fail due to there already being an implicit "*" so it would be seen as "<**.your_domain.com>". It should be like the following .*, or "<your_domain.com>". Examples of this are (.*, .rightnowdemo.com, .*demo.com, .open-fusion5.rightnowdemo.com, rightnowdemo.com). The configuration setting is under Configuration Settings > Common > General > Cached Content.
*In versions 18C to 20C, this configuration is OIT_CORS_WHITELIST.

For additional information, refer to the section in the Online Help User Guide documentation. To access Oracle B2C Service manuals and documentation online, refer to the Documentation for Oracle B2C Service Products.