Skip to main content
replaced http://salesforce.stackexchange.com/ with https://salesforce.stackexchange.com/
Source Link

I managed to launch a Primary Tab from a Custom Console Component, using this openPrimaryTab sample page as the Custom Console Component.

I had to whitelist the domain that I wanted to launch, so in this case www.salesforce.com in the Service Console App Settings (Whitelist domains)

The Primary Tab does launch alright, although the cross domain error message that you mentioned comes up in the javascript console, I would guess because Visualforce is served up from a different domain.Visualforce is served up from a different domain.

I managed to launch a Primary Tab from a Custom Console Component, using this openPrimaryTab sample page as the Custom Console Component.

I had to whitelist the domain that I wanted to launch, so in this case www.salesforce.com in the Service Console App Settings (Whitelist domains)

The Primary Tab does launch alright, although the cross domain error message that you mentioned comes up in the javascript console, I would guess because Visualforce is served up from a different domain.

I managed to launch a Primary Tab from a Custom Console Component, using this openPrimaryTab sample page as the Custom Console Component.

I had to whitelist the domain that I wanted to launch, so in this case www.salesforce.com in the Service Console App Settings (Whitelist domains)

The Primary Tab does launch alright, although the cross domain error message that you mentioned comes up in the javascript console, I would guess because Visualforce is served up from a different domain.

Source Link
techtrekker
  • 18.4k
  • 1
  • 45
  • 50

I managed to launch a Primary Tab from a Custom Console Component, using this openPrimaryTab sample page as the Custom Console Component.

I had to whitelist the domain that I wanted to launch, so in this case www.salesforce.com in the Service Console App Settings (Whitelist domains)

The Primary Tab does launch alright, although the cross domain error message that you mentioned comes up in the javascript console, I would guess because Visualforce is served up from a different domain.