Skip to main content
Hello Everyone,

I have an issue with the service cloud console.

Normally when adding an attachment or adding a new comment, the Case tab will refresh, showing the modification as shown in the attachment named 'Standard and Expected behavior (no override).png'.

Service Cloud Console does not automatically refresh the View page on the Case object when overridden

Later we have overridden the standard View page of the Case object with a new custom visualforce page called 'TicketPageWrapper.page' as shown in the attachment 'Case View Overriden.png'.

User-added image

In order for the debugging process to be easier and to eliminate other possible causes from our side, I have eliminated all our custom scripts and left the page as simple as possible.

The code for the 'TicketPageWrapper.page' visualforce page is the following:

<apex:page standardController="Case" extensions="TicketPageWrapper">

<apex:detail id="detailBlock" inlineEdit="true" relatedListHover="true" subject="{!Case.Id}" relatedList="true"/>

</apex:page>

After repeating the process the result looks as shown in the attachment named 'Faulted behavior (after override) - no refresh.png'. The automatic refresh does not occur.

User-added image

I am not sure if this can help but I have also attached the firebug console after the comment has been added in the overridden page ('Firebug output in overriden page.png').

User-added image

When refreshing the houl page, the comment appears and this is actually the problem. I would like to know why this happens and have the page refresh just like it used to before.

Other similar issues include the 'hideListButton' arrows not memorising the state after closing the ticket as shown in attachment 'hideListButton issue.png'

User-added image

as well as not being able to change the icon of this 'external page' which in fact is not external, using sforce.console.setTabIcon('/img/sprites/master.png');.

I was able to change the title however using: 'sforce.console.setTabTitle('Ticket ⌗{!Case.CaseNumber}');' however.

The most important issue of all is the first one of course. The problem with the refresh.

I would like to know what can be done to bring back that functionality.

Any suggestion and information is welcome.

Thank you!

Best regards,

Alexandru.
4 risposte
  1. 12 gen 2015, 13:41

    I have looked through these links and while I understand that having only custom visualforce pages and playing with the service console API would work just fine, in this case I am talking about the standard Case object page wrapped in a visualforce page. By doing so my original page becomes an external page and the ticket adding page as well as the new comment page appear in a subtab.

    First of all I do not see how I cann add code in that subtab... It is a standard page I have no access through through code. I cannot set the focus to the parent Tab, I cannot identify the parent Tab, I cannot get the Id of the tab (where do I write that and how do I call it), I cannot write code inside the Case tab to refresh the page on focus because the tab remains in focus and most functions don't even work anyway in this case.

    These commands are simply being ignored. If I hav code access in these standard pages I believe I would see something happen, but as it stands it does not work. The only thing I was able to do was change the onClick function in 'add attachment' to not use 'navigateToUrl' and instead open in a new primary tab. Not only does that tab not automatically get focus, but it is opened as an 'External page' as the title.

    In short, the link provided is very general in it's explanation and only works for custom visualforce page <-> custom visualforce page relations. I would like to know if anyone has managed to make this possible and I would prefer a full visualforce page A code in the answer and full visualforce page B code if necessary.

    Also I would like to know how to call a 'sforce.console....' type function from a standard subtab such as 'Ticket Comment Edit' (where I cannot write code). Perhaps that would help with the issue.