If you install adTempus to a location other than the default location ("Program Files\Arcana Development\adTempus\4.0"), the adTempus database and other adTempus data may still be created under that folder. The problem was resolve to place data in the correct location.

Existing installations are not affected by this change. Please contact us for assistance if you need to relocate an existing data folder.

If you have configured the adTempus server to use certificate security (to accept client connections from outside the Windows domain), the server may still not accept connections that use certificate security.

This update must be applied to both the adTempus server and the remote computer(s) where the Console is run.

The Alerts view should include job-level alerts (alerts logged for a particular job) but does not. This problem was fixed in the adTempus server and does not require an update to the Console.

Note: As a result of this fix, when you first start adTempus after applying the fix you may find a large number of old job-level alerts in the Alerts view, because these alerts were generated in the past but not visible in the view for acknowledgment

For more information see Knowledge Base article K00000442.

When you edit a Schedule within a Schedule Trigger and click the "Show Matching Dates" link, the resulting list of dates does not reflect the holiday settings configured for the Schedule Trigger. This is intentional, as the Show Matching Dates command was intended to be used to confirm that your date rule is matching the correct options.

This creates misleading results if the schedule uses a date rule with an option such as "exclude holidays" set. Therefore this command has been changed to reflect the holidays when holiday-related settings are used within the schedule.

When a Program Execution Task executes with the "Capture screen output from console-mode program" option checked, adTempus will now save a copy of the captured output in a file in the job's temporary folder, so that scripts and tasks within the job can read the file. The name of the file is stored in the "JobStep.CapturedConsoleFileName" Job Variable.

Note that the file is not available until the program being run has exited.

For more information see Knowledge Base article K00000437.

The Active Range for a Date Criterion shows date/time values for the start and end values. It should show only dates, because the time value is not used.

If a script retrieves a Job Variable value from the JobVariables collection and the value of that variable contains references to other Job Variables, the variable tokens are not expanded.

For example, Variable1 is set to "A", Variable2 is set to "B", and Variable3 is set to "%Variable1%%Variable2%". If a script retrieves the value for Variable3 using adTempus.JobVariables("Variable3"), the value is returned as "%Variable1%%Variable2%", when it should be returned as "AB".

For more information see Knowledge Base article K00000449.

When you run a Database Operation Task with the "Execute SQL" or "Select a scalar value" Action, adTempus will now log each command/query executed, along with the output from the database server, to a text file, which will be included in the Captured Files for the job as "Database Results.txt".

During job execution (after the task completes), a copy of the file will be available in the job temporary directory, so that scripts and other tasks within the job can read it. The path/name of the file will be found in Job Variable "DatabaseTask.DatabaseResultFile".

The Database Operation Task does not provide a way to set the timeout value for database operations, and uses a default timeout of 30 seconds. Operations that take longer than this will fail with a timeout error.

This was resolved by increasing the default timeout to 30 minutes and adding a global configuration setting to allow the value to be changed.

A future adTempus version will allow configuration of the timeout for each task.

For more information see Knowledge Base article K00000444.

File Operation Tasks now allow you to use a Job Variable as an include file when the Source Root is set to "Specify absolute paths."

You can include multiple files in a single Job Variable by using ";" or "," to separate them. For example, you can set "MyFileList" to "c:\test\file1.txt;c:\test\file2.txt;c:\test\file3.txt". In the File Transfer task, set the Source Root to "Specify absolute paths" and enter "%MyFileList%" in the Include Files box. The task will copy all three files.

This feature can be used to copy the files found by a File Trigger: Set the Include Files to "%FileTrigger.FileName%". The "FileTrigger.FileName" is automatically set by the File Trigger to contain the names of the files matches by the trigger.

If a network (or removable) drive is unavailable, the File Trigger may treat this as though all files on the monitored drive had been deleted, resulting in erroneous file deletion triggers followed by erroneous file creation triggers when the drive is restored. The problem was fixed to correctly handle this scenario.