Previous Next JavaScript must be enabled to correctly display this content

## 3 Scheduling the Archival Jobs

This topic provide information about the Archival Jobs.

These jobs can be scheduled under Configure Tasks screen via CRON expressions.

Configuration Requirements

1. CRON Expression: Users need to set up the CRON expression to specify how often the job runs. For instance, the CRON expression `0 */10 * * * *` means the job will execute every 10 minutes, daily.
2. Task Trigger Name: When you choose a Task Name, the task trigger name will automatically set itself. However, it's advisable to give it a clear name, particularly when adding additional trigger parameters for certain branches.
3. Additional Trigger Parameters: To enable branch-specific account closure, extra parameters must be provided in the Additional Trigger Parameters field. The supported format is key:::value. For instance, branchCode:::000;userId:::ADMINUSER1.
4. Priority of Parameters: The branchCode and userId in the Additional Trigger Parameters take precedence over default values.
   - Default Values: If branchCode and userId are not supplied in the Additional Trigger Parameters, default values from the PROPERTIES are used. Ensure that the following entries have valid user and branch code values, along with applicable roles to run the job:
     1. APPLICATION = "plato-batch-server", KEY = "batchServer.userId", VALUE = "<user-id>"
     2. APPLICATION = "plato-batch-server", KEY = "batchServer.branchCode", VALUE = "<branch-code>"
5. Saving the Configuration: Save the configuration, and the job will be scheduled according to the provided CRON expression.

For Detailed Information, refer to Oracle Banking Microservices Platform Foundation User Guide