Introduction / FirstSpirit ServerManager / Schedule entry planning

Schedule entry planning

FirstSpirit schedule entry planning can be used to group associated actions together into a schedule entry and to start them at defined, scheduled times.

The FirstSpirit ServerManager offers the ability to display existing schedule entries and the associated information. The Schedule overview table can be opened within the server or project properties.

The Schedule management menu item is used to add new schedule entries and manage existing ones. Creating new schedule entries is divided between configuring the schedule properties, such as entering a start time, and adding the desired actions that are to be carried out as part of the schedule entry.

The actions must first be created using ServerManager. Server-based actions are defined within the server properties; project-based actions are defined within the project properties of the individual projects.

The following server-based actions can be selected in the server properties:

The following project-based actions can be selected in the project properties:

The two action types

can be used both in server-based and project-based schedule entries.

Project-specific schedules and actions can also be installed on the FirstSpirit server with a module and executed via schedule entry planning (for more information about implementation, see Schedule Tasks (→FirstSpirit Online Documentation) and for information about integrating these project-specific schedules).

Actions already created once can easily be copied from the existing schedule entries. If the same actions are to be reused in multiple schedule entries, an action template can be created similarly to using the FirstSpirit template concept. The action template is used to add an action to any number of schedule entries. Changes to an action in this case are entered centrally through the template.

In addition to execution through ServerManager, schedule entries can also be executed interactively through the FirstSpirit SiteArchitect. To do this, the user needs to have the required permissions for interactive execution, which means the user must be in the list of authorized users or a member of a user group that is in the list of authorized groups.

© 2005 - 2024 Crownpeak Technology GmbH | All rights reserved. | FirstSpirit 2024.4 | Data privacy