# Create a Job

> Create an AutoSteps job, either from the Jobs view or from an existing script.

Source: https://docs.capaone.com/performanceguard/administration/about-autosteps/autosteps-user-interface/create-a-job/  
Product: PerformanceGuard — a separate CapaSystems product; do not apply this page to any other.

AutoSteps allows user to create jobs in two different ways:

- **From Jobs:** To create a new job click ![](/attachments/performanceguard/c1b57e08-1f76-4bbb-9199-55a3c019ddda.png) .
- **From Scripts:** From a script ![](/attachments/performanceguard/85573bb2-b8d8-46d3-9451-bc1ff4a748d6.png) create a job.

## Scripts

AutoSteps uses AutoHotkey allowing users to automate repetitive tasks in any windows application. Scripts run in an environment where many pieces of information are made available.

:::tip
You can create a job with multiple scripts - but it will create separate jobs for each script i.e. "one specific Script per Job".
:::

## Executor Group

The grouping of executors allow users to submit jobs to specific executors depending on the group name. Users can specify different groups for all executors. Based on the group name executors will be selected and job will be submitted by performing load balancing among these executors.

## Schedule

**Schedule:**You can add a schedule to a job. The user can add schedule to run these scripts to avoid having to configure every time via daily, weekly, monthly or custom intervals.

:::caution
As a default it is set as **Enabled**. There will not be

![](/attachments/performanceguard/56128f21-793c-41c5-9e8e-2917ff6ea398.png)

next to a job if it isn't enabled.
:::

:::caution
You can also set jobs to **Debug** as well if you wish to determine whether a program is working correctly.
:::

:::note[Important]
<details>
<summary>Where can I find the file with Debug log?</summary>

You will find the logs in the \AppData\Local\Scout\ExecutionDir. The file will be named same as the Script name with the date and time the script was executed.

</details>
:::

:::caution
You can not save a job until **Script**, **Executor Group** and **Schedule** have been selected.
:::

:::note[Important]
**Example:**Click thumbnail to view image in full size.

![](/attachments/performanceguard/b4eb29d7-be46-4c6b-8b55-2887a9868bcf.png)
:::

:::caution
After creating Jobs you can select multiple jobs SHIFT+Click to edit (change them to enable or disable) or delete the jobs. You can deselect a job by clicking again on it.
:::

# Default Scripts

You can select from some default scripts that AutoSteps already contain:

**BTMutil** **Demo:** This script demonstrates how to use the BTMutil supplied with the PerformanceGuard Agent. BTMUtil.exe is a small tool that is useful when you want to test your installation and when you want to time events in local scripts. See more about [Monitor Complex Activity with AutoSteps](/performanceguard/administration/more-setup/monitor-complex-activity-with-autosteps/)

**Notepad Demo:** AutoSteps uses BTM with AutoHotKey to run this script, execute it and then save the file in the default location specified in the Script. This also uses [AutoSteps Source Code](/performanceguard/technical-reference/concepts/autosteps-source-code/) for COM start-stop interface as BTM.

**Outlook Mail Roundtrip:** AutoSteps uses BTM with AutoHotKey to run and execute the script. The script will create an e-mail and send the mail to the recipient specified in the Script. This also uses [AutoSteps Source Code](/performanceguard/technical-reference/concepts/autosteps-source-code/) for the COM start-stop interface.

# Overriding Job Parameters

AutoSteps allows you to override the executable parameters when creating/editing a job.

:::caution
If you will not check Override - the job will use the Default Parameters values that were set when created that particular script.
:::

:::note[Important]
**Example:** Click thumbnail to view image in full size.

![](/attachments/performanceguard/df39e548-46de-4662-8ac7-24fd5ec4c067.png)
:::