adTempus 4.6.0 Release Notes

When a step is configured to capture console output from the program being run, you can now view the partial capture results while the step is still running. Each time you open the file from the job history, it will display the current contents of the console output. The view of the file will not refresh automatically. If the job is running on an Agent, you still will not be able to view the file until the step completes, as the file is not sent to the Master until then.

Further enhancements will be made in adTempus 5.

 

In a job instance listing (Job Monitor, History Query, history tab of job list), the Comments for the instance can now be displayed as a column. To choose the columns to display, right-click a column heading to show the list of available columns.

If a Response that uses event "Restart limit exceeded" has an action to restart the job, the response evaluator goes into an infinite loop, causing the adTempus service to crash with a stack overflow exception.

This was corrected so that Restart actions are ignored when triggered by Restart Limit Exceeded events, as this configuration doesn't make sense anyway.

The Job Monitor may continue to show jobs as active even though they have completed. This happens if the option to show past jobs is not selected. The problem was corrected to remove inactive instances.

In some cases evaluation of inline scripts fails. This does not cause the job to fail, but an error message is reported in the Job Log ("Inline script evaluation failed") with no error reason.

For more information see Knowledge Base article K00000564.

For more information see Knowledge Base article K00000573.

A job exists on server A and server B. On server A, you delete a step from the job, then export the job and import it on server B. After import, the deleted step is still present on server B; it should have been removed by the import. The same problem may occur with other parts of the job (triggers, conditions, responses, etc.). This problem was resolved.

For more information see Knowledge Base article K00000562.

If two jobs run at the same time that use the same Script or Script Library, and that script or library has been modified since it was last used, one of the jobs may fail with error "Script compilation error: Unable to write output file..." If the job is rerun it works correctly.