adTempus 4.10 Release Notes

Jobs can be configured to run if their scheduled execution is missed because the system's clock is set forward and/or to repeat if the clock is set back. This feature was intended to address small time changes such as clock synchronizations and Daylight Saving Time changes. It can cause problems in scenarios with larger time changes, such as on a computer where the system clock is incorrect by months or years at startup and is subsequently synchronized with a time source after adTempus has scheduled jobs for execution. To address these issues adTempus was modified to recalculate execution schedules (ignoring the settings for individual jobs) for forward clock changes of more than 4 hours or backward changes of more than 12 hours. That is, if the clock is set forward by more than 4 hours, no missed jobs will be executed; if the clock is set backward by more than 12 hours, any jobs that would normally execute in the "repeated" timeframe will be executed.

This problem was fixed.

When a Notification Action or Notification Task includes attachments that are not configured to be saved in the job history, these attachments are not included if an email notification fails and is later successfully retried.

In some cases where the adTempus server is under high load (server CPU at 100%) adTempus may incorrectly detect that the system clock has been set forward by a second or two. If this happens at the exact second that a job is scheduled to run, the execution may be missed if the job does not have the option set to "Run once if clock set forward."

Input fields in the Console accept some non-printing Unicode characters that are not valid in the XML format. adTempus accepts these characters and saves the data, but when it tries to write this data to XML in some contexts (for example, when creating export files or object snapshots), this produces an error such as the following:

"Export failed: ", hexadecimal value 0x1F , is an invalid character."

This can prevent you from saving or deleting objects in the Console, because the server writes copies of them to XML as part of the snapshot process.

This problem was corrected to filter out the invalid characters.

If a File Transfer Task is configured with a source folder that has a trailing slash (e.g., "c:\myfolder\"), the task may behave incorrectly, including:

• Failing to properly apply exclusions
• Failing to copy/move files from the source folder
  

If a File Trigger is configured to monitor a folder that does not exist when the trigger starts monitoring, the File Trigger may fail to trigger if the folder is created and files are immediately created in it.

If a job is executing and other instances of the job are pending execution (waiting for the active instance to complete) and you terminate all instances of the job, in rare cases this can result in a database error that causes adTempus to think there are still active instances of the job even though there are not; this can prevent additional instances from running if they are configured to wait for previous instances. This problem was corrected.

When a file transfer operation is given a source file name or pattern that contains certain punctuation characters, those files are ignored by the file operation because of a problem with the way adTempus filters file names for selection. Names containing these characters are affected: "+{[()^$#". This problem was corrected.

When a script runs, the adTempus object is not returning values for these properties:

• JobOID
• JobInstanceID
• StepOID
• StepInstanceID;
• InstanceID
• StepNumber
  

When you try to add a security login that uses adTempus (user ID/password) security, you may get an error that a login already exists for that user even though there is no existing login.