Automations with Vertec scheduled tasks
Operating mode
Cloud Suite
|ON-PREMISES
Modules
Services & CRM
Budget & Phases
Purchases
Resource Planning
Business Intelligence
In order to automate processes in Vertec that are performed regularly, e.g. overnight, the planned tasks are available.
New scheduled tasks can be created in the folder Settings > Customize > Schedule Tasks.
A scheduled task has the following properties:
Type |
There are different types of tasks:
|
designation |
Designation of the planned task. For example, shown in the list. |
Active |
Only active scheduled tasks are performed. |
Repeat mode |
Here you can select between Daily and Weekly. The time is given in Coordinated Universal Time (UTC). Alternatively, a CRON expression can be specified. Information about the structure of CRON expressions can be found on the Internet, such as Wikipedia: https://de.wikipedia.org/wiki/Cron. In the background, each of these data leads to a CRON expression, with which the time of the next execution is determined. You can check your entries in the Next Execution field below, which shows the time of the next execution in both UTC and local time. Note for the Cloud Suite: We recommend setting the execution to a time from Monday to Friday between 02:00 and 19:00. Outside these times, for example due to maintenance windows, it may be that a running task is forced to complete or not execute on that day. |
Users |
The scheduled task will be performed under this user, so a user with sufficient privileges to execute this script must be defined here, usually the administrator. |
Functional reference |
Only available if as type The function reference is the name of the script entry, followed by the feature to be executed within this script, separated by a period. It must be a feature with no arguments.
Once entered, the code can be shown in a popup using the button with the three dots. The button Open in Script Editor in the popup opens the Script entry directly in the Script Editor and can be edited there. |
Status |
Specifies whether the execution was successful or failed. If the execution failed, the error message shows in the Last Output box at the bottom. |
Next version |
Here, the time of the next execution is shown in both UTC and local time. The next run is determined based on the CRON expression (see Repeat Mode field above) and the current time. However, if the Cloud Server is not running at this point, the execution cannot be performed. As soon as the Cloud Server is running again, it detects the next execution. Past “missed” executions are not made up at the start of the Cloud Server to prevent a sudden large number of tasks from running at the same time. |
Last Start |
Start time of the last execution. |
Last Completion |
End date of the last execution. |
Last edition |
Output of the last execution. If this failed, the error message is shown here. |
In the context menu of the scheduled task, there is an Execute Now menu item. It is important to note that this operation does not set the scheduled task to the current point in time, but only executes the script – just as if the script or the called method were executed in the Script Editor, under the logged-in user and not under the user defined in the scheduled task.
If the Restricted Filesystem Access or Restricted Session Process parameters are enabled, activated reports to be stored on the file system are sent to the client for storage.
In Scheduled Tasks, this does not work and throws the following errors:
Der Bericht kann nicht gespeichert werden. Bitte verwenden Sie eine DMS Schnittstelle oder geben Sie einen leeren Speicherpfad an.
As a remedy, there are the following options:
Intern
)resultat = vtcapp.executereport2(projekt, None, vorlage, '')
. The report can instead be sent e.g. by e-mail.In the Vertec.ini file in the [cloudserver] section, there are the following parameters that affect the scheduled tasks:
Task Scheduler |
Controls whether the Scheduling task is active or not. If not, no scheduled tasks are executed. If the parameter is not specified, the default is Task Scheduler = False If you are running multiple Cloud Server, only one of them is applied to run tasks. For all others, this parameter must be set to |
Task Scheduler Polling Minutes |
Controls how many minutes are checked for outstanding scheduled tasks. Natural number, default is 1. |
Task Scheduler Concurrent Tasks |
Controls the maximum number of scheduled tasks that can be executed in parallel. Natural number, default is 1. |
Special Task Scheduler Range Start
|
This allows you to define the time window in which the planned tasks for the BI calculations, the full-text indexing and the recalculation of the index statistics may be carried out. Within this time window, the Vertec Cloud Server rolls a time in which the processes are started. The start time is set by a new session at the start of the Cloud Server. Special Task Scheduler Range Start=23:00 Special Task Scheduler Range End=05:00 How to roll: Start from the start time, the quantity of minutes until the end time is determined. Then, a random number from 0 to the quantity of minutes is rolled and this value is added to the start time. This yields the CRON expression for determining the next run. |