Download Release Notes

Automation Engine
120
Forecast calculation incorrect for a periodic turnaround later than 00:00
The Forecast assumed a wrong starting date for the calendar check of schedules when the
periodic turnaround was later than 00:00. The same held for JobPlans with starting point on the
next day. If an object of the JobPlan had a condition specified in the Earliest tab, it was not
considered.
S# 28571
Version 3.02B
Object name could contain invalid characters (CREATE_OBJECT).
The script element CREATE_OBJECT creates Calendars and Variables. Invalid characters
were accepted up to now, for object names. This has been changed and now a warning message
with a list of all allowed characters is displayed when invalid characters are used.
S# 31965
Script element PREP_PROCESS_FILENAME could not be fully used in the Event object
The script element PREP_PROCESS_FILENAME can also be used in the script of an Event
object. If, however, the optional parameter was used for the Login object, an error message was
displayed.
S# 31687
Incorrect calculation of maximum runtime for tasks in Schedules
It is possible to make settings for monitoring the runtime of tasks in Schedules. With the
corresponding maximum runtime (MRT), AE can monitor a task and react when the limit is
exceeded. This value was not correctly calculated.
S# 32621
Job report was not deleted although the corresponding option was selected
When executing Jobs, you can specify if the job report is to be stored or deleted (host-specific
tab). It happened from time to time that these reports could not be deleted although the
corresponding option had been activated. Mostly this occurred when a file name was generated
incompletely.
S# 31887
UTC was used instead of the specified time zone
When processing the script element :SET_CONDITION, which defines starting conditions for
JobPlans, UTC (Coordinated Universal Time) was used, thereby setting the wrong starting time.
Now the time zone of the task (if available) or of the user or client is used.
S# 32728, S# 30305
With the script function GET_WIN_EVENT, the date and time of an Event can be determined
with the keyword TIMESTAMP. UTC used to be returned by mistake instead of the client's time
zone.
S# 36286
The version management can now also be activated in the client settings. So far, the objects that
were duplicated in this process did not show the time stamp of the client's time zone as
intended.
S# 32093
Local time was used instead of UTC when objects were imported with the loading program. As a
result, the displayed time differed from the actual creation time.
S# 37014