> For the complete documentation index, see [llms.txt](https://docs.slapfive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slapfive.com/integrations/salesforce/slapfive-app-spring-2024-4.0-and-earlier-versions/12.-salesforce-classic.md).

# 12. Salesforce Classic

There are two SlapFive components you can add:

The Customer Case Study and References component looks like this and it's Visualforce Page names are *SlapFive\_BoardContainerVF\_Opp* and *SlapFive\_BoardContainerVF\_Account*.

![](/files/ki89G86bJMPSK1tdmVbl)

The SlapFive Reference Content & Customers component looks like this and it's Visualforce Page names are *SlapFive*\_*ReferencesVF*\_*Opp and SlapFive*\_*ReferencesVF*\_*Account*.

![](/files/PRo9fsVG0NGHr1q3SKJ1)

Here are the steps for adding the first component to the Opportunity page layout:

Go to **Setup** > **Build** > **Customize** > **Opportunities** > **Page Layouts** and select **Edit** on the page layout to which you want to add the component.

* [ ] In the palette at the top of the page, scroll to the **Visualforce Pages** section, and drag & drop the **Section** block to the position you want it placed in the page layout, then click the wrench icon for the new Section and give it a name like *Customer Case Studies & References*.
* [ ] From the same **Visualforce Pages** section, drag & drop the **SlapFive\_BoardContainerVF\_Opp** component to the **Section** block.
* [ ] Double-click the **SlapFive\_BoardContainerVF\_Account** component you just dropped, check the **Show scrollbars** field and click **OK**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.slapfive.com/integrations/salesforce/slapfive-app-spring-2024-4.0-and-earlier-versions/12.-salesforce-classic.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.