Is it possible to update the date parameter for a scheduled job?

Our AP team would like to automate the AP Payment Process. We can setup the jobs/job stream and schedule to run daily but we would need the Payment Date and Effective Date field parameters from the Electronic Payment File Creation job form to default to the current date.

For Example: using the saved job (screen print below) to create our PCC payment file, the Payment Date in the file would be 8/14/24 which is the day the job was created/saved and not the day the job was executed. When the Create AP Payment Files process is generated to create the payment file, it executes our ExportPaymentOutputFiles_COA IPA. Is there a way to default to the current date each time the job executes (customization or programmatically) so that the payment date in the file = current date?

Find more posts tagged with

General Discussions

Accepted answers

All comments

cleverly

You can use Configuration Console to customize the form and specify an initial value of the current [corporate] date. This is how we have our's configured for the "Select Options" section:

andy

If you are setting parameters on a batch task (scheduled job), the initial value may be derived on the action form when you view the parameters, but when you save it will probably populate the parameters XML with the explicit value from the form at the time you save the job, so it will likely still use the same value each time it runs. Correct me if I'm wrong though Michael

I think I've run into this before and accomplished dynamic parameters for batch tasks by using "default" values in the parameter rules, and leaving the parameter blank on the batch task so the derived value defaults in, but that's probably not possible in this case since you can't modify the parameter rules of the action.

You might look at using an IPA flow instead where you have more flexibility, and having a scheduled job trigger the IPA flow.

cleverly

Andy, you are of course right. How embarrassing, I didn't read Ginger's message closely enough to see that they wanted to schedule it via async.

Here is an idea I think would work:

The idea being:

Create a User Business Class in Config Console
Store all the values that are fixed as persistent fields
Have an instance action that invokes the actual business task and passes those values along with the dynamically calculated dates
Then create a record in the UBC with the proper settings (VendorGroup = COA, PayGroup = HOSP, etc.)
Then schedule the Run instance action to run daily or on whatever frequency the Accounts Payable folks desire
When the scheduled action on the UBC runs it will in turn trigger the business task with all of the appropriate variables

I don't see any reason why this shouldn't work, but it'd definitely be worth testing in a non-Prod environment first.

cleverly

This was my mocked up key field definition:

Being in the Context of a FinanceEnterpriseGroup will be important.

Welcome To Solutions Development.docx

Copyright © 2025 Infor. All rights reserved.