AWA, in it's infinite wisdom, does NOT populate the start time field on the Process Monitoring tab, until execution truly begins. So a user that uses "Execute Once" to start a job at a later time, cannot easily go back and see WHEN it will start.
I would like to implement a workaround.
At OSU, we set our outer workflows to generate at activation. This means their Process tab executes when the user submits the JOBP, even when they use the "Execute Once" feature to have the the actual execution start at a later time.
With this in mind, I would like for our outer workflows to read their own "intended start time", and set ARCHIVE_KEY2 to that value, so it can be viewed in the Process Monitor.
However, I cannot find documentation on an attribute that would give me this information.
Does anyone know of an AWA attribute to provide the future time that a job is scheduled to run for?
Thanks!
------------------------------
Reed Byers
Programmer/Analyst
Oregon State University
------------------------------