As an Archer administrator, you need to run calculations on Exception Requests daily to see...

In the Archer platform, the Recalculation Schedule (found within the application's General Tab) is a powerful tool, but it can become a performance bottleneck if not configured efficiently. When a recalculation job is triggered, the Archer services must evaluate every record in the application to determine if calculations need to be updated. According to the Archer Administration II curriculum, the most effective way to optimize this process is by using Calculation Filters .

By selecting option A, you are instructing the system to ignore records that are irrelevant to the specific business logic (e.g., records that are already "Expired," "Rejected," or "Draft"). By filtering the schedule to run only for "Approved" requests, the job engine processes a significantly smaller subset of data, which reduces the load on the Async Service and speeds up the completion time. Option B would likely slow the system down further by adding logical complexity to the calculation itself. Option C (Data-Driven Events) is not suitable for date-based triggers because DDEs only fire upon a record "Save" event; they cannot proactively "watch" a date to trigger a change without user intervention or a scheduled recalculation.