Skip to end of banner
Go to start of banner

Associating a Salesforce Object with a Confluence page

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Introduction

The Connector for Salesforce & Confluence Cloud can associate the following Salesforce Objects with a Confluence page:

  • Account

  • Case

  • Contact

  • Opportunity

This page will show you how to associate a Salesforce Account with a Confluence Page. If you want to associate other Salesforce Objects such as Case, Contact, or Opportunity with a Confluence Page, the steps are very similar.

Before proceeding, ensure that the following has already been completed:

  1. Installed the Salesforce Package

  2. Set up a connection

  3. Configured Salesforce with the installed Salesforce Package.

Step-By-Step Guide

  1. Open the Salesforce Account you want to associate with a Confluence page.

  2. In the Visualforce page section that you created, there should be an Associate Confluence Page button. Click the button.

    (warning) Your company may have configured Salesforce pages differently. For example, the page layout and button position may be different. If you cannot find the "associate" button, contact your IT support department or Salesforce administrator.

  3. When the Associate Confluence Page pops up, type in the Confluence page you want to associate the Account with, and a menu with all available choices will appear.

     

  4. Choose your desired Confluence page and then click Create.

  5. Once the association is successful, a confirmation message appears, and the page is updated with the association.

  6. If you want to associate a Case, Contact, and Opportunity with a Confluence Page, just load the respective pages and click on the Associate Confluence Page button. The examples below show the button location for a Case, Contact, and Opportunity page. As noted earlier, your company may have configured Salesforce pages differently.



     

  • No labels