Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It is possible to embed visualforce pages onto page layouts. So I would recommend creating a visualforce page like the example below. Use the apex code you already have that is performing the webservice callout as the controller extension for this page and you'll be able to show the fields.</p> <p>The only thing I'm unclear about is what specific parameter do you want to pass to your webservice? and how is it being passed to the contact page currently? If it's just a url parameter, your controller extension will have access to it using the ApexPages class. If it's the Id of the contact the constructor of the controller extension will be able to get it from the StandardController parameter.</p> <p>Some important things to note:</p> <ul> <li>the visualforce page must use the Contact standardController for it to be available as an embeddable visualforce page.</li> <li><p>If the contact view action is already overridden the embedded visualforce page will not render. However if the page is already overridden you wouldn't have this problem because you could add the required code straight to the override page.</p> <p></p> <pre><code>&lt;apex:pageBlock id="block"&gt; &lt;apex:pageBlockSection id="section"&gt; &lt;apex:pageBlockSectionItem id="item"&gt; &lt;apex:outputLabel value="External Value:" for="externalValue" /&gt; &lt;apex:outputText id="externalValue" value="{!externalField}" /&gt; &lt;/apex:pageBlockSectionItem&gt; &lt;/apex:pageBlockSection&gt; &lt;/apex:pageBlock&gt; </code></pre> <p></p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload