# Configure Salesforce Integration

{% hint style="info" %}
Please make sure you are connected to Salesforce. Otherwise, head to [Getting Started](/atlassian-cloud/scrybe-external-data-objects-and-query-for-jira/administrator-guide/getting-started.md)
{% endhint %}

### Object Views Configuration

This section lists the details for configuring object views.

Step by step guide:

1. Click on add object view<br>

   <figure><img src="/files/cn0flKULGZF80T6eL1HN" alt=""><figcaption></figcaption></figure>

2. In the dialog, the **Title of view** will be used as the tab name in the Jira issue panel. You can configure multiple tabs, allowing you to display different objects within the same Jira issue.\
   \
   \- Select the Salesforce object you want to use as the main object. \
   \- You can configure which fields will appear in the table view. \
   \- You can also specify which user groups are allowed to access the tab.<br>

   <figure><img src="/files/PFYLkCMAAkCtIf7OQkpQ" alt=""><figcaption><p>Salesforce object view in JIRA issue</p></figcaption></figure>

   <div align="left"><figure><img src="/files/smfXJXa2kLSRLOFnOgnu" alt="" width="375"><figcaption><p>Edit dialog for Salesforce object view</p></figcaption></figure></div>

3. Click **Save** once you are done.

### Query Views Configuration

This section lists the details for configuring query views.

Step by step guide:

1. Click on add query view.<br>

   <figure><img src="/files/kvGOJLAk46XmaOGcxhvR" alt=""><figcaption></figcaption></figure>

2. In the dialog, the **Title of view** will be used as the tab name in the Jira issue panel. You can configure multiple tabs, allowing you to display different queries within the same Jira issue.<br>

   <div align="left"><figure><img src="/files/QuSRQAdcMn2IRU4Myjr6" alt="" width="375"><figcaption><p>Edit dialog for Salesforce query view</p></figcaption></figure></div>

3. In the SOQL query section, you can enter the SOQL query you want to run. There are three types of queries:

   1. **Query with no variables**\
      A standard SOQL query with fixed values.\
      Exampl&#x65;*:* `SELECT Name FROM Account`
   2. **Query with issue variables**\
      You can reference values from the Jira issue (e.g., reporter email) to make the query dynamic.\
      Example:

      ```
      SELECT Id, Name, Account.Name, Owner.Name 
      FROM Contact 
      WHERE Email = '{{issue.reporter.emailAddress}}'
      ```

      With this, the query will automatically run using the issue reporter’s email.
   3. **Query with query variables**\
      These queries require the user to input values directly in the Jira issue. Once entered, the values are saved and will be used automatically the next time the tab is loaded.\
      Example:

      ```
      SELECT Id, Name, Owner.Name 
      FROM Account 
      WHERE Name LIKE '{{AccountName}}%'
      ```

      You can then provide the variable value within the Jira issue.<br>

      <figure><img src="/files/KOmYe3JfdNUodJMTt9wc" alt=""><figcaption><p>Salesforce query view in JIRA issue</p></figcaption></figure>

   \
   You can also specify which user groups are allowed to access the tab.<br>

4. Click **Preview** to verify that the query runs successfully. Once everything looks correct, click **Save**.

\
**Additional Resources**

If you need further assistance, don’t hesitate to contact our support team at **<support@upsmith.app>**. We’re always happy to help!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.upsmith.app/atlassian-cloud/scrybe-external-data-objects-and-query-for-jira/administrator-guide/configure-salesforce-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.