adTempus 5.1.1 Release Notes

When hidden Job Variables are used as part of the command line for a Program Execution Task, the variable values are logged to the Job Detail Log and in adTempus server diagnostic logs. The software was changed to conceal the values in these places.

If the connection type for a Database Operation Task is set to "Other" (using a custom OLEDB connection string), the connection test fails with error ADT005320E: Unrecognized database type "unspecified", and the task will fail if the job is executed.

When upgrading to adTempus 5 from adTempus 4, the database upgrade script may fail when trying to drop a database constraint that is not present in the database. This can happen if the adTempus database has previously been through upgrades from version 3, or if the constraints have been removed for some reason. The database upgrade scripts were modified to ignore missing constraints.

When upgrading an agent-only instance of adTempus, setup does not recognize the agent-only license that is present on the computer and reports that no license was found. This problem was corrected so the license is detected.

PowerShell scripts may fail because some external modules cannot be loaded.

When an email trigger is configured to save the body and attachment separately and the message does not contain an HTML or plain-text body part, adTempus properly saves the attachments but fails to set the EmailProcessing.MessageLocation Job Variable with the location of the saved attachments.