Select the TimeEvent (executed at the specified time) you have added. On the right you will see a list of options to configure this event:

In the process of configuration, depending on your earlier choices, the options will change slightly.

For example, you can configure PolyAnalyst to perform a scheduled task every N day(s) (see the screenshot above), i.e.

You can specify the start time and the end time of scheduled task execution, as well as its interval in hours and minutes.

In the lower-right area you can specify the start and end dates of task execution.

If you want to configure PolyAnalyst to perform certain tasks on server start, select a SrvStartEvent you have created.

Contrary to time events, server events do not require any configuration.

All the events and tasks you add are saved automatically. After you have added the required events, you may start scheduling tasks.

To create a new task, right-click the selected event and open the Add task menu. A list of tasks will be displayed:

Alternatively, you can select an event, then click the menu button and select Add task.

All these tasks are enabled in the list only after you select an event in the tree. The following commands are available:

You can assign multiple tasks to the same event. The order of tasks in the tree determines the order of execution. The tasks of one level of the hierarchy are executed simultaneously.

Note that if you create subtasks, they inherit the following properties from their parents:

Sometimes it is helpful after creating a task to verify that the task will execute as expected at a later point in time. To do it, right-click the task and select Test (immediate execution) in the context menu.

PolyAnalyst begins executing the task immediately. The progress of task execution is not displayed. You can monitor the progress of the task by viewing the task list.

Note that testing a task that involves executing a project will still permanently alter the project in the same way that having the task execute at a scheduled point in time will permanently alter the associated project. There is no difference between testing a task and a normal execution of the task except the activation way.

To delete an event or a task, right-click on its name in the Scheduler window and select Delete. Alternatively, left-click on the event’s or task’s name in the hierarchy to select it and then click the Delete button on your keyboard.

If an event was deleted, any tasks configured for this event are also deleted. Similarly, if a task was deleted, any consecutive tasks (located under the task within the hierarchy of items) are also deleted.

To copy one or more events or tasks:

PolyAnalyst cuts or copies and pastes the selected events and tasks. Pasting an item does not clear the copy-and-paste clipboard. You can paste the same copied item repeatedly into the hierarchy of items.

When you create an event or a task, it is initially enabled. It means that the event/task can be executed. Disabling an event/task means that it remains as a configured event/task in the hierarchy in the Scheduler window, but PolyAnalyst prevents the event/task from executing at its scheduled time.

Rather than deleting an event/task that you do not wish to be executed on a schedule, and losing the time spent configuring the event/task, you can instead disable it. The event/task will remain scheduled, but will not be executed. You can still edit the properties of a disabled event/task.

To disable an event/task:

Disabled events/tasks remain in the hierarchy of items in a gray font.

To re-enable one or more events/tasks, repeat the previous steps and check the Enable option.

Toggling an event/task will automatically toggle all dependent subtasks. In other words, if you have task A and B, and task B is configured to run when task A completes, when you disable task A, the task B is also disabled.

The user can make PolyAnalyst send a particular kind of alerts in case of successful completion of a scheduled task, or failure, or both.

To do it, proceed as follows:

Click OK to save the settings and close the window.

Before executing a scheduled task, PolyAnalyst checks the permissions of a specific user profile.

There are two authentication systems, i.e. that of PolyAnalyst and that of Windows. In PolyAnalyst it always works in the same way. In Windows we can work under the credentials of other users.

A scheduled task is always carried out under PolyAnalyst credentials of its owner, while the Use stored credentials option, when checked, changes the Windows user.

As a task owner, you can configure it to run under the credentials of yourself or under a different Windows user who may have different permissions. This is helpful when, for example, the task requires access to resources that a user would otherwise not be permitted to access or use (such as trying to open a CSV file located in a protected folder on an organization’s network).

If a task is run without using the stored credentials, it is run under the credentials of the server service account. However, if the server is configured to require impersonation (see the section on Impersonation policy in Administrative Tool security settings), when the server attempts to carry out the task that requires access to a protected resource (e.g. a folder of files shared with only certain Windows users), the task may fail to execute due to insufficient permissions. In this case, PolyAnalyst will record that as an error occurred.

To avoid it, you can attach a custom Windows user profile to your PolyAnalyst profile by editing your PolyAnalyst profile (via the Settings → My profile menu in the Analytical client). It virtually means storing credentials. Then, you can switch on this option for a task by right-clicking on the task in the Scheduler and selecting Use stored credentials. When it is time to carry out the task, PolyAnalyst will look up the associated credentials, authenticate itself in Windows as that user, and then carry out the task using the permissions of that user profile.

It is this process which is referred to as impersonation or delegation in Windows.

To stop a running task, right-click on the event or task and select the Stop tasks option.

Note that task execution locks the database and switches the server to the exclusive mode. No project can be opened, no client can be connected, many other tasks can also freeze or return the "PolyAnalyst is busy" error. On particular databases, it can take several minutes or dozens of minutes to complete a task.

If you are an administrator, you can select another PolyAnalyst user to perform the task you scheduled. To do so, right-click on the event or task, and then select the option Change task user. Select the required user from the list. Check the option All subtasks, if you want the user to execute the subtasks of the current task.

Click OK to save the changes and close the window.

If you are an administrator, you can give another PolyAnalyst user the opportunity to edit (and own) the task you scheduled. To do so, right-click on the event or task, and then select the option Change task owner. Select the required user from the list. Check the option All subtasks, if you want the user to execute the subtasks of the current task. Click OK to save the changes and close the window.

The permission to edit (and own) a task can be granted to a group of users.