# Events

The *Events* are conditionally triggered *Methods* if something happens. In terms of distribution, we can split *Events* into two groups; one group is bound with *Views*, and the second one is attached with the *Components*.

![Application calling sidebar by an Event](/files/7fBjfpGEWRMcIsXs8ckx)

### 1. Components Events

Except for a few *Layout components* rest of them can edit *Events* by clicking on the flash icon, choosing the proprietary *Method*, and configuring *Event* logic with the *Flowchart* wire editor.

{% tabs %}
{% tab title="Button\[onClick] Event" %}
![](/files/8iU1grmszUWohrVnArhE)
{% endtab %}

{% tab title="Flowchart  Editor" %}

<figure><img src="/files/neD8IZ7UbAyeooaCrsjO" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

### 2. Views Events

Each of the existing application *Views* has an option to edit its *Events* on Initialize and when the input parameters are changed — even in editing *Views Events*, configuring *Event* logic with the *Flowchart* wire editor.

{% tabs %}
{% tab title="View Events Settings" %}
![](/files/P6ywRXTPw4XwjCLMnONJ)
{% endtab %}
{% endtabs %}


---

# 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.adapptio.com/getting-started/architecture-overview/events.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.
