7.3.6.3 Edit Dynamic Parameters

Modify the dynamic parameters set for a batch/batch group.

You can modify the batch parameters, batch header parameters, task parameters, and the task header parameters associated with a batch/batch group.

You can save your custom settings for future use by checking the "Remember my saved preference" option. When you execute a batch, your saved preferences will be used for that batch and its tasks. When you migrate a batch, your preferences will also be migrated. When you save your preferences:

• Copying a batch or task will also copy the preferences.
• Deleting a batch or task will also delete the preferences.

To edit the dynamic parameters from the Schedule Batch page:

1. Select Batch/Batch group and then select the specific batch/batch group.
2. Click Edit Parameters to access the Edit Dynamic Params page.
   You can also edit the dynamic parameters while configuring the scheduling options.
3. Click the batch/batch group name to access all the parameters.
4. Set the $BatchDate$ to set the batch execution date: :
   • Set the batch date to SYSDATE (system date). The batch execution date is set to SYSDATE by default.
   • Toggle and select MISDATE to select a particular batch execution date.

   Note:

   All dates used in scheduling logic, including the MISDATE field, are consistently stored and processed in UTC (Coordinated Universal Time). This design ensures that scheduled batch executions and system date calculations remain standardized across all regions, eliminating discrepancies caused by local time zones. The MISDATE represents the scheduled date of a batch as stored in UTC. It does not adjust based on the user’s local time zone. The SYSDATE function always reflects the current date and time in UTC when used for scheduling logic.

   Example: If a customer in Singapore (UTC+8) schedules a batch for March 16th at 02:00 AM local time, the system automatically converts and stores it as March 15th, 18:00 UTC. When any user views the MISDATE field for this batch, it will display 2024-03-15 (the UTC date stored).

   Similarly, the SYSDATE value is based on the current UTC date and time, ensuring all scheduling logic is aligned with the UTC standard. As a result, while the user schedules the batch for March 16th in their local time zone, the system consistently operates on the equivalent UTC date, maintaining uniformity across all locations.
5. Enter $BATCHRUNID$ to set the batch run ID in the format: <BATCH_CODE>_<MIS_DATE>_<ITERATION-COUNT>.
6. Edit the batch header parameters and the task parameters.
7. Click Save to update the batch/batch group parameter values.
8. After updating the changes, execute the batch/batch group or configure the scheduling settings.