You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Bug on Oracle Report: Co-Browse Summary Report ID 193 - Solution

Received Response
17
Views
1
Comments
edited Dec 6, 2016 11:09AM in Reporting & Analytics for B2C Service 1 comment

Content

Hi All,

We have a customer who is using the Livelook / OSvC Co-browse on their Service Cloud Implementation.

Looking at the reports we appear to have identified a bug with the OOTB "Co-Browse Summary Report" (ID 193) report.  Anyone using Co-Browse should be aware of this potential issue

This report has the following code within the definition against source:

if(cobrowse_sessions.tbl=1, msg_lookup(7475), msg_lookup(7494))

What this means is if a Co-browse is initiated on the back of a chat and then converted to an incident the Source type will be against the table type of 1 and presented as a

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!