> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/salesforce/applications/apex-classes-and-triggers.md).

# Apex Classes and Triggers

## Apex Applications

{% hint style="warning" %}

* Create Organization and Environment with appropriate external client app credentials - [Configure External Client App](/product-guides/integral-zone/iz-suite/iz-eye/salesforce/external-client-application-configuration.md)
* To start scanning the applications, a schedule has to be created to scan the Classes and Triggers deployed in Salesforce Instance - [Configure Code Scan Schedule](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/code-scan-schedule-configuration.md)
  {% endhint %}

### To view all the applications

1. Navigate to **`IZ Eye`** -> **`Salesforce`**-> **`Apex`**. Overview includes -

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fd0Uir3jqT1Z6vn5MyEPV%2Fsf_applications.png?alt=media&amp;token=b08ef5dd-9f25-440c-9df8-5bf144c0d499" alt=""><figcaption></figcaption></figure>

a. **`Name`** - Name of the Apex Class or Trigger

b. **`Organization`** - Organization to which the app belongs to

c. **`Environment`** - Environment to which the app belongs to

2. Click on the **`Plus`** icon to view the details

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FPlaf0ttmHcdhgjvmAFqj%2Fsf_applications_details.png?alt=media&amp;token=6bab5007-008a-428f-91e9-9b80cd1376f1" alt=""><figcaption></figcaption></figure>

3. Summary details include -

&#x20;    a. **`Total Issues`** - Indicates total number of issues once the application is scanned

&#x20;    b. **`Status`** - Indicated the status of class / trigger in Salesforce

&#x20;    c. **`Last Scan`** - Time since the last scan was performed

4. Actions include -

&#x20;     a.**`View Dashboard`** - Summary report of all the issues.

&#x20;     b.**`View Issues`** - Detailed report of the issues with file names and line numbers.

### To view only Apex Classes or Triggers

1. To filter either Classes or Triggers locate the **`Source`** filter from the filtering options and choose the appropriate value -

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FqGy7NMyMheGsBQtKnXzV%2Fsf_application_filters.png?alt=media&amp;token=174eeec1-fff1-4052-9ea0-1e19a45de53b" alt=""><figcaption></figcaption></figure>

1. **`Apex Class`** - To filter only Apex Classes
2. **`Apex Trigger`** - To filter only Apex Triggers

Use these filters to narrow the list quickly, then open the application details to review scan status, issue count, and the available reporting actions for the selected Apex Class or Trigger.

### See Also

* [Configure External Client App](/product-guides/integral-zone/iz-suite/iz-eye/salesforce/external-client-application-configuration.md)
* [Configure Code Scan Schedule](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/code-scan-schedule-configuration.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/salesforce/applications/apex-classes-and-triggers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.