> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/platform-docs/zebratester-scripting/zebratester-user-guide/2.-scripting-the-load-test-session/6.-execution-control-user-defined-transactions-and-page-breaks.md).

# 6. Execution Control -User-Defined Transactions And Page Breaks

## Add Transaction <a href="#id-6.executioncontrol-user-definedtransactionsandpagebreaks-addtransaction" id="id-6.executioncontrol-user-definedtransactionsandpagebreaks-addtransaction"></a>

The Transaction tab allows defining and adding Transactions into the recorded session.

***

**Add Transaction Input Fields:**

* **Transaction Name**: Enter an arbitrary, unique transaction name.
* **End at Item:** Select the end of the transaction. A transaction can end at any URL or can end at any page.

The measured results of the transactions are shown in the Load Test Result Detail menu:

***

## Insert Page Break <a href="#id-6.executioncontrol-user-definedtransactionsandpagebreaks-insertpagebreak" id="id-6.executioncontrol-user-definedtransactionsandpagebreaks-insertpagebreak"></a>

The Page Break tab allows inserting belated Page Breaks into the recorded session.

**Insert Page Break Input Fields:**

* **Before/After Item**: Inserts the page break before or after the specific URL position.
* **Page Description**: Arbitrary description of the web page.
* **User's Think Time**: The "human" page view delay in seconds.
* **User's Think Time Randomness**: Random deviation of the page view delay in percent, recalculated every time when a simulated user calls the web page during the load test.

**Hint:** See also Insert Page Break at the left upper corner in Main Menu to insert a Page Break at the end of the currently recorded session.


---

# 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.apica.io/platform-docs/zebratester-scripting/zebratester-user-guide/2.-scripting-the-load-test-session/6.-execution-control-user-defined-transactions-and-page-breaks.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.