Job Scheduling and System Automation
adTempus 5.0.3.0 Release Notes
5.0.3.0
Released September 19, 2023
Enhancements
Console
Change to allow a Save operation to be canceled from the Comments window
When auditing or snapshots are enabled, the user may be prompted to enter comments when saving an object (Job, Queue, etc.). The comments window does not have a cancel button, and closing the window without clicking OK does not cause the Save operation to abort. This behavior was changed so the window now includes a Cancel button that can be used to cancel the Save operation.
User Scripts
New limit on number of messages user scripts can write to the Job Log
A user script can use the adTempus.LogMessage method to log
messages to the Job Log for the executing job instance. Because each
message is stored as a separate database record, logging a large number
of messages can have an adverse effect on adTempus database space
requirements and on Console performance. A new limit of 100 script
messages per job instance has been added, to protect against excessive
logging from scripts. Once this limit is exceeded, all subsequent
messages are sent only to the Script Debug Log, which appears as a
Captured File in the job history.
This limit can be configured through the "JobExecutor:ScriptMessageLogLimit" Advanced Server Option.
If
your script needs to log a large number of messages for debugging or
diagnostic purposes, use adTempus.LogMessage with MessageTypeEnum.Debug,
which sends the message to the Script Debug log instead of the main Job
Log.
Fixed Issues
Console
In some windows, clicking a button causes the window to unexpectedly close
This issue was resolved.
For more information see article K00000624.
Server connection broken when saving duplicated items
Attempting to duplicate some items (such as steps within a job) causes the connection between the Console and server to be dropped when using an adTempus 5.x Console with a 4.x server.
For more information see article K00000626.
Console may prompt for comments when saving objects even when configured not to
When a user saves an object (Job, Queue, etc.) the user may be prompted to enter optional comments for the change, even when auditing is not enabled for the object (in which case the comments are not saved anywhere) or when the audit setting is "Automatic" (in which case the user should not be prompted for comments).
Server connection broken when setting Advanced Server Options
Attempting to set an Advanced Server Option causes the connection between the Console and server to be dropped when
using an adTempus 5.x Console with a 4.x server.
Distributed Scheduling
Connection fails if large amount of data is waiting to be sent from Agent to Controller
If a large amount of data (status updates, log messages, etc.) is waiting to be sent from an Agent to its Controller, the connection between them may fail when the Agent tries to send the data. This failure prevents any updates from being sent, and also may block the Controller from sending commands to the Agent. This problem can occur if the Controller is unreachable for an extended period and/or jobs on the Agent are producing large numbers of log messages, and happens because the Agent tries to send more data at one time than the Controller can accept.
This problem was resolved so the Agent sends data in smaller batches in this scenario.
General
adTempus reports database error alert with error "Object reference not set to an instance of an object"
For more information see article K00000628.
Installation
Database upgrade fails if user running installation does not have default schema of dbo
If the user running the database upgrade process does not have their default schema set to dbo in SQL Server, the database upgrade process may fail because the upgrade scripts do not include the dbo table prefix in all cases,
Job Execution
Job Control Action fails after upgrade from 4.x
After importing or upgrading data from adTempus 4.x, some Job Control Actions may fail to execute.
For more information see article K00000627.
