Which field determines the default batch job used for reporting in a template editor?

Which field determines the default batch job used for reporting in a template editor?

• A. The Report frequency field
• B. The Activation date field
• C. The User role mapping
• D. The Security level field

Answer: (A)

The field that sets how often reports should run determines which batch process the template will use. The report frequency defines the cadence (daily, weekly, monthly, etc.), and the system links that cadence to the corresponding default batch job for reporting. In other words, the default batch job is chosen based on how often you want the reports to execute. Activation date affects when the template becomes active, not which batch job runs; user role mapping controls who can access or run reports, and security level governs access permissions, not scheduling. So matching the default batch job to the chosen frequency ensures reports are generated on the intended schedule.

The field that sets how often reports should run determines which batch process the template will use. The report frequency defines the cadence (daily, weekly, monthly, etc.), and the system links that cadence to the corresponding default batch job for reporting. In other words, the default batch job is chosen based on how often you want the reports to execute. Activation date affects when the template becomes active, not which batch job runs; user role mapping controls who can access or run reports, and security level governs access permissions, not scheduling. So matching the default batch job to the chosen frequency ensures reports are generated on the intended schedule.