# Task Automations

Streamline and optimize the management of activities and template assignments by configuring an automation schedule.

<figure><img src="https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FH5sUVpD98XTzlRDLG8Y0%2Fsrtjsrtj.png?alt=media&#x26;token=c1c108d6-71c0-4842-b6fb-17ba40505aed" alt="" width="563"><figcaption></figcaption></figure>

### New Automation Rule

To create a new automation rule for a template, start by clicking the **New Automation Rule** button.

<figure><img src="https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2Fxo95SEVjHoTf5W9uW5QT%2F28-12-2023-01-17-23%20(1).png?alt=media&#x26;token=cbfd7b89-2a0b-40a3-b311-fbdd4ea85260" alt="" width="563"><figcaption></figcaption></figure>

Within the Create a Rule pop-up menu, you can set the trigger date for your rule, the condition which will execute the rule action, and the task template which will be assigned if the condition for the rule is met.

![](https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2Fp81ED28SB1fIxcWnl3aT%2Fimage.png?alt=media\&token=03496dd3-f226-401a-86f0-cf51ebeac0d3)<mark style="color:yellow;">**Trigger**</mark> - At the set date and time, the trigger will execute the action that’s configured for the user group selected in the condition field.

This section also allows for a **Recurrence** schedule to be created. By toggling Recurrence **ON**, you will be able to set the repetition cadence for the rule as well as choose an end condition for the recurrence schedule.&#x20;

![](https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FOZGSaT29uh41OglCWerG%2Fimage.png?alt=media\&token=7dc38228-4987-4dce-a9f2-b547a783475e)<mark style="color:orange;">**Condition**</mark> - This section controls which users or user segments/criteria will be affected by the set Action.&#x20;

* **All Network Users**: This option will include all network users (excluding guest users) in the action when the trigger conditions are met.&#x20;
* **Specific Users**: Select individual users for the rule. Multiple users can be chosen at once.
* **Specific User Criteria**: Choose users based on a selected criterion. Multiple criteria can be selected. The function operator **AND** will be assigned between the criteria.

{% hint style="info" %}
If **no** users meet the condition set at the time the rule triggers, the action **will** still complete, but with 0 users affected. The rule will then re-evaluate at its next scheduled execution.
{% endhint %}

![](https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FFfbXXgIiPtFyT3PcbcQ7%2Fimage.png?alt=media\&token=54e6bdd4-a66a-480e-b703-02993baf9e2b) <mark style="color:green;">**Action**</mark> - This field designates the task template that will be assigned to the selected condition group when the trigger executes. Only **one** task template can be assigned per rule. For additional templates, separate rules must be created.

When completed, your rule may look something like this:

<figure><img src="https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FCXygYO5iVcUfamvb74bl%2F28-12-2023-01-38-24%20(1).png?alt=media&#x26;token=1eef7663-41f7-4902-928d-e122dedf66f2" alt="" width="563"><figcaption></figcaption></figure>

**Breaking down the example**:

This recurring rule will execute for the first time on 2/1/2024 at 4am EST, then trigger again every subsequent 3rd month on the first Monday of the month. Since no end has been set for the recurrence schedule, this rule will follow its trigger schedule indefinitely. This means that, every 3 months, users who've joined the domain within the past 90 days will be assigned the New Hire Onboarding Task List - General.

{% hint style="info" %}
Unlike tracker workflow automations, all rules within task automations will execute, regardless of whether they have similar conditions and triggers.
{% endhint %}

***

### Action Menu

Once a rule has been created, additional menu options will become available from the **3-dot** menu.

<figure><img src="https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FsRRADyAExW7DC7lkHnrm%2Frethsrth.png?alt=media&#x26;token=dddb9d42-0b98-4a73-a541-79c34810e8c7" alt="" width="563"><figcaption></figcaption></figure>

**Edit Rule** - Click this option to bring up the **Edit a Rule** menu. From this menu, you are able to edit an existing rule.

**Disable Rule** - Disabling a rule will prevent the automation from triggering until it is re-enabled. A disabled rule will have it's **Status** changed from <mark style="color:green;">Active</mark> to <mark style="color:orange;">Inactive</mark>, and vice versa when it is re-enabled.

**Run Rule Now** - This option allows you to trigger the automation rule to run immediately. This action will **not** affect the set schedule cadence for the rule.

**Delete Rule** - This option will delete the selected automation rule permanently. <mark style="color:red;">Please consider disabling the rule rather than deleting it as this will cause</mark> <mark style="color:red;"></mark><mark style="color:red;">**permanent**</mark> <mark style="color:red;"></mark><mark style="color:red;">data loss.</mark>

***

### Automation Log

The automation log provides a comprehensive record of rule executions and changes. To access the automation log, select it from the New Automation Rule drop down menu.

<figure><img src="https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FwttzQEZXzHLk7bitXb3e%2Ftdyjdtyjdy.png?alt=media&#x26;token=f008423a-9a2a-4189-8ca4-0edf486b0fc8" alt="" width="563"><figcaption></figcaption></figure>

Within this automation log, admin users will be able to review when a rule executed and the resulting action that took place. Admins can also search for the execution log of specific rules by typing it's name into the search bar towards the top of the item table.

This log also tracks activity changes made to individual rules. Click the **Change Log** tab to view when a rule was changed (enabled, disabled, created, deleted, edited), which rule was changed, and which user made the change. This view also includes a search bar for quick rule lookup.

<figure><img src="https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FiqeukGofxKNMXc4VoWsF%2F28-12-2023-03-39-23%20(1).png?alt=media&#x26;token=ec470cb7-861c-4edf-b8bf-b73c013bb238" alt="" width="563"><figcaption></figcaption></figure>
