Here user can perform transaction-related settings. There are two sub-sections under this:

## Page as Transaction

This option is used to enable or disable the transaction. It contains the following options:

- Do not consider page as transaction : No transactions are created automatically for any page. However, users can create custom transactions within the scripts.
- Consider each page as a transaction : The transactions are automatically created for each page. For example: For the Home page, a transaction named "tx_Home" will be created.
- Consider each page's success or failure as distinct transactions : Each page's success or failure is considered as a transaction.
- Consider each page status as different transaction : In this status of each page is considered as a distinct transaction for that page.
  For example: For page status Home_Success, HomeConFail, and findflight_PartialHdr, transaction names will be "tx_success" and "tx_failuretype" where the failure type is ConFail and PartialHeader.
- Do not add the 'tx_' prefix in the transaction name : 'tx_' is not prefixed with the transaction names. This option is available in all cases except do not consider the page as a transaction test.

## Advance Transaction

### Enable Transaction Grouping in Transaction Details

To enable transaction grouping in transaction details, follow these steps:

- Select the transaction group file from the drop-down list or upload a file with a .tgp extension.
- Ensure the file contains data in the following format: GroupName|Page1,page2,page3...pageN
  For example, to combine login pages, use the following format: login_group|login,login_1,login2

  Note: You can add more groups in the subsequent rows.