
The code for the 'TicketPageWrapper.page' visualforce page is the following:
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.<apex:page standardController="Case" extensions="TicketPageWrapper">
<apex:detail id="detailBlock" inlineEdit="true" relatedListHover="true" subject="{!Case.Id}" relatedList="true"/>
</apex:page>
4 respostas

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.