Create Bot Use Case

To create a Bot Use Case:

Go to Configuration > Use Cases > Bot tab.
Click the Create Use Case button.
Enter the Use Case Details:
1. Select the Use Case Type:
- BASIC: the default type
- SCRAPER: this Use Case automatically creates a Bot Task intended for scraping web pages.
- ETL: using this type, you can add Answers to the Bot Task. These answers can define variables, parameters, or column names used in the config code.
By using ETL configs, you improve the config re-using and flexibility. Business users (non-programmers) do not need to edit the config code directly – they only need to specify parameters in Answers while adding Bot Task to a BP.
Switch to Advanced Mode and paste your valid XML code from Web-Harvest IDE.
If you create an ETL config, select Add Answer. These Answers are completed when using the Bot Step in a BP. You can set some parameters or variables, for example, map input and output columns.
Save the Use Case.

Use variables and Answer values

The variables are as follows:

<var-def name="var_name">: Defines a new variable in your config.
<var name="var_name">: Returns a value of the defined variable inside the tag.
${var_name}: Returns a value of the defined variable in tag attributes.

Example:
```
<single-column name="http" value="${var_name}"/>
```

To return a value of a variable from step input data inside another tag, for example, ocr_link, use the template processor:

<mail smtp-host="smtp.example.com" 
      smtp-port="587" 
      type="text"
      to="venkata@example2.com"
      security="ssl">
      
      <template>${ocr_link}</template>
</mail>

The Answers are as follows:

{{answer_code}}: Returns the ETL answer value.

Example:

<var-def name="input_column"> 
    {{column_with_url}}
</var-def>

The ETL config code is processed by the FreeMarker engine. To return a value from the input file column name defined in Answer, wrap it with the <#noparse>...</#noparse> tag. FreeMarker does not search FTL tags and interpolations and other special character sequences in the body of this directive, except the noparse end-tag.

Example:

<export include-original-data="true">
    <#noparse>
        <single-column name="http" value="${output_column}"/>
    </#noparse>
</export>