> ## Documentation Index
> Fetch the complete documentation index at: https://target-calculator-docs.ha-consultancy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scheduling & Approvals

> Automate Target Calculator with Business Central Job Queue Entries and require approval before completed results post their action plans.

# Scheduling & Approvals

## Automate with the Job Queue

After you run **Setup Job Queue** once (see [Getting Started](./01-getting-started.mdx)),
four Business Central **Job Queue Entries** drive the extension automatically:

1. **Result Creation** - creates the result record for each new period.
2. **Calculation Engine** - recalculates achievement for active configurations.
3. **Status Update** - advances result status as periods start and end.
4. **Action Execution** - posts action plans for completed results.

To activate automation:

1. Open **Job Queue Entries**.
2. For each Target Calculator entry, review the recurrence (and adjust the schedule if
   needed), then set the status to **Ready**.
3. Make sure the configurations you want processed have **Active** turned on.

> Only configurations marked **Active** (and not **Archived**) are processed by the
> Job Queue. The on-demand **Run Calculation Now** button always works regardless.

## Govern posting with approvals

If you want a person to sign off before action plans run, turn on
**Posting Requires Approval** on the configuration card.

* When enabled, a completed result must be **approved** before its action plans post.
* The approver is determined by the standard Business Central **Approval User Setup**.
* Similarly, **Allow Goal % Override** + **Override Requires Approval** route any manual
  goal-percentage change through approval before it takes effect.

This keeps automated calculation fast while keeping a human in control of the actions that
follow.

***

## Tips & housekeeping

* **Clone** a configuration (from the list or card) to start a new one from an existing
  setup - the copy is created inactive so you can adjust it safely.
* **Archive** instead of delete to keep historical configurations out of the active list.
* Use **Export / Import to Excel** on the Targets page to manage large target sets.