adTempus 4.0 Release Notes

Previous behavior: when e-mail notification fails for a job, adTempus logs a warning message to the Job Log and continues to retry the notification at intervals for up to an hour. If notification is still not successful after that time, an Alert is logged.

New behavior: The initial warning message is now logged as an Alert instead of just appearing in the Job Log for the job.

Due to a problem in an earlier version of the software, the adTempus 2 or adTempus 3 database may contain records that point to data that has been deleted. This causes the database upgrade process to fail. The database conversion scripts were modified to remove the invalid data during conversion.

For more information see Knowledge Base article K00000432.

When editing a job that is linked to other jobs (on either end of a Job Condition or Job Control Action) the adTempus server erroneously sends all jobs linked to the job (and jobs linked to them, etc.), resulting in a very slow load.

adTempus Administrators added through the Database Configuration Wizard or the Administrator Provisioning tool may not be added to adTempus on service startup.

If more than on instance of adTempus is configured, the Administrator Provisioning tool may crash after you select the instance to manage.

adTempus can now automatically create logins for users based on Active Directory group membership. See Automatic Login through Group Membership in the online help for more information.

For more information see Knowledge Base article K00000428.

For more information see Knowledge Base article K00000423.

If a Program Execution Task, Script Execution Task, or Response Event has an exit code rule that tests for a value equal to 0, the "0" value is not displayed in the Console (the entry box is empty). However, the criterion is still applied correctly using a value of 0. If the criterion is set to a value other than 0, it is displayed correctly.

For more information see Knowledge Base article K00000426.

The replace references function did not replace references to Notification Recipients. The problem was corrected.

For more information see Knowledge Base article K00000427.

As a result adTempus cannot connect to the adTempus database if the LocalSystem account did not already have permissions for the database. Database wizard was fixed to ensure that LocalSystem account is granted permission for adTempus database.

If the adTempus service on an Agent is running under a user account (instead of LocalSystem), the Master fails to connect with error "The target principal name is incorrect". This problem was resolved.

 

For more information see Knowledge Base article K00000424.

In rare cases when two job steps are executed at exactly the same time, one job may fail with an internal error message.

For more information see Knowledge Base article K00000425.

For more information see Knowledge Base article K00000429.

Due to the way that adTempus executed external PowerShell scripts, the $MyInvocation.MyCommand was of type Script rather than ExternalScript and did not have the Path and other properties set. This was corrected.

If you include Job Variables in the Comand-Line Parameters for a PowerShell script run by the Script Task, the variables are not expanded before being passed to the script.

Applies to container-level security windows (Notification Recipient Security, Script Security, etc.)

The Database Configuration Wizard and Database Utility were changed to require Administrator authority for execution.

Console gives error "The Execution Target and Batch Script cannot both be specified" when step was configured to run an internal batch script and you change it to run an external program.

If a File Trigger includes Job Variables in the File Specification, adTempus may fail to trigger for the file(s).

If a File Trigger has more than one file specification and is configured to wait until all specifications have been matched, the Trigger ignores this setting and fires as soon as any of the specifications is matched. This problem was resolved.

If a Schedule has been configured to run on specific days and you change it to run every X days, you get an error when you try to save the Scheduler: "Cannot specify days when Criterion Type is Interval".

The Job Diagram does not show Job Triggers, and may fail to draw links between jobs linked by Job Control Actions.

Previous versions had the ability to schedule on "weekdays" (Monday through Friday) and "weekends" (Saturday, Sunday). Changed to eliminate these fixed definitions to support other workweeks (e.g., Sunday through Thursday).

If option checked to only capture files modified since start of job, files not captured.

 

In some scenarios it was not possible to remove a reference from one object to another. For example, if a Schedule Trigger was configured to use a Holiday Set and you changed the Schedule Trigger to no longer use holidays, after saving the Schedule Trigger the holidays were still referenced.

PowerShell scripts can now reference/include other scripts.

Changes were not saved