Many periodic tasks require the entry of execution date or parameters. Sometimes this uses a query which means users can use the flexible date ranges (advanced filter query syntax) however in most periodic tasks users must specify a from and to date or a posting date. These fields are linked to a standard data field which don't allow for dynamic input. This means that if the batch task was set to recurrence, the operation would be complete with the same date as was specified in the initial input. This is preventing users from using recurring batch jobs when processing ledger allocation request or fixed asset depreciation proposals automatically. There are many examples of periodic tasks that cannot be run in a batch job due to this limitation.

It would be extremely useful to have dynamics date entry for recurring batch job processing. Example of dynamics coding could be:
(day(0)) = today
(day(-1)) = yesterday
(month(-1)) = this day last month

The syntax doesn't have to allow for complex scenarios, the most important requirement is a dynamic input for today.