> For the complete documentation index, see [llms.txt](https://200ok.gitbook.io/200ok-documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://200ok.gitbook.io/200ok-documents/user-manual/etl/create-your-etl/additional-features-of-etl.md).

# Additional Features of ETL

The inherent flexibilities within ETL functionalities not only contribute to heightened adaptability but also serve as a key catalyst in capturing comprehensive insights into the usage dynamics of each execution, amplifying its utility and effectiveness.

The additional functionalities includes.

**Run With Data**

<figure><img src="https://lh7-us.googleusercontent.com/z-ojmrsuRhkR3txAecRC_CzHPg2I2ZzVQGERg58AkeC8DPz7KjddMXj_XJQgi81FO6f9pvSYBvoVqjK97vG8G1DRKQJsTKYy3Sh0FZf_2xL13500jhre4Wi_RZShJzQzvHiQoSu7nvWzk2AAzTKxR0I" alt=""><figcaption></figcaption></figure>

The Run With Data helps to pass additional data to the ETL before the execution starts. It consists of different parts which includes.

**SObject**

This helps to send a Record Id for a particular SObject.<br>

<figure><img src="https://lh7-us.googleusercontent.com/IK4_GYRPeiFvuibfkB3bNilFqS6Uif6S9K-N5TfL6xDDNV-Mfi1aD2cpMObfvdITOgLX-fSZMoBxxRvEL9Wrx4KsnfkW2n1O_HSEnY7q2G7IXolf3A0qNDLSqlKZhQwd38iGltpB_ysuPnJndYUmEL0" alt=""><figcaption></figcaption></figure>

**Type**

<figure><img src="https://lh7-us.googleusercontent.com/TLN5ksRmVUyxaFee3KCXVRH06Qmm3MSX2cskWYzljHPGmJ2uhl-3gGAN7bG2ebrn4niIDPpzsS_mL02U2jhyPF6W2tCj0czonJkIudQt_AhhqeD0z5bage_OAUw3bB_ApZ8ty7CQZj4fYGyMg1LBxy8" alt=""><figcaption></figcaption></figure>

There are various types based on which the execution can happen. The types are

**ETL**

This is where the execution takes place starting from the Extract, Transform and Load. This is set as the default one.

**Extract**

The execution takes place only on the Extract Part.

**Transform**

The execution takes place only on the Transform. The data which needs to be transformed can be sent from the Custom JSON part of the Run with Data.

**Load**

The Load can take place independently by taking the data from custom json.

**Extract and Transform**

The user can extract the data from the selected data sources and transform the data based on the requirement. This excludes the Load part for ETL.

**Transform and Load**

Transform the Custom JSON data from run with data and use the same transformed data on the Load excluding extracting data from the ETL.

**Custom JSON**

This section holds on the add-on JSON for the ETL execution which can be used on ETL’s various types.

**Advanced Setting**

<figure><img src="https://lh7-us.googleusercontent.com/1UFKBX1MuI1HN1th9l1o1aqlaTPasBWfMGpx5LkBydPNbc2XB17IvvNmI6J4RgcC_FoVKEpBjc6n2NEkk0vKKa1hR439o7a0lQKGAq7_7BfQuPpiF2XQ9tWGSaad7pkD-fvtwHW4mDhXSu8KtNyBGOg" alt=""><figcaption></figcaption></figure>

The advanced setting for ETL provides two functionalities which includes.

**Logging Level**

The logging level provides the functionality to get the execution log for the ETL and it also helps to get the stack trace of the transaction.

**Email**

Here the user needs to enter the email where they will get the notifications from the ETL execution.

With these final insights, we gracefully conclude the ETL process, having navigated through its intricacies and harnessed its transformative capabilities to empower informed decision-making and unlock the full potential of our data ecosystem.