Scheduling wizard

New schedule builds one event: what is being done, to what, with whom, when — and then sends. Sending is a single action that opens a service ticket and issues the calendar invitations; there is no draft stage and no partial save.

Creating an event requires a permission. Anyone without it does not see the row in the sidebar, and reaching the URL directly produces a screen that points back to the calendar.

The steps

Up to six steps, two of which appear only when the update type asks for them. The step indicator at the top collapses the gaps, so the numbering always runs consecutively.

#	Step	What blocks Next
1	Update type	No type selected
2	Select servers · Select equipment · Databases	Nothing selected — unless the type marks the step optional
3	Manager & contacts	The system manager name is empty, or no performer was chosen
4	Date & time	Start and end not set
5	Tasks	A task exists with no title or no assigned user
6	Summary & send	—

You can go back to any completed step by clicking its circle in the indicator. You cannot jump forward.

Reset form, in the corner, clears everything and starts over. The wizard also resets itself on every entry, so an abandoned schedule does not live on into the next visit.

1 · Update type

The type comes first because it decides the rest of the wizard: whether there is a selection step at all, what is picked in it, whether there is a tasks step, and which message template goes out at the end. Full detail in Update types and templates.

2 · Select targets

The step's name changes with the type — Select servers, Select equipment or Databases — and with it the source of the list. Selection is made from a table with a search box, and beside it a paste box: paste a list of names (one per line) and press Find and add.

3 · Manager & contacts

Three parts, only two of them required.

• System manager — fetched automatically from the first selected server, and the screen says which server it came from. It can also be searched by hand in the directory by name, id, email address or user name. Required.
• Performed by — chosen from a list the system keeps, and a new name can be added from the same panel. Required.
• Additional contacts — optional. Searched in the same directory, and a contact who is not registered there can be entered by hand.

Above the contacts a System memory card may appear: people who were added to past events on the same systems beyond the type's default list, and notes an administrator recorded on those systems. Every suggestion states the date it came from and is added with one click. The card can be dismissed.

4 · Date & time

A month grid for the day, and beside it the shortcuts Today · Tomorrow · In a week.

Setting the start time drags the end to one hour later; changing the end on its own moves only the end. A Quick duration row offers one, two, three or four hours, and the duration in hours is shown large beside the times themselves.

One file up to 15MB can be attached. The file travels with the invitation only and is not stored in the system — the screen states this under the upload area.

Two warnings can appear at this step, and neither of them blocks:

Warning	When
Overlap with a planned event	The window overlaps an event on a linked system, on a shared compute cluster, on the hypervisor host of the selected servers, or on the storage underneath them
Overlap with a configuration freeze	The window falls inside a defined freeze period

Both are re-checked on every change to the window, and both stay completely silent when there is no finding or when the check itself is unavailable. Both messages end with the same sentence — "You can continue — this is a warning only" — because the coordination call belongs to the person scheduling, not to the system. On the freeze periods themselves see Configuration freeze.

5 · Tasks

Shown only for update types configured for it. Each task gets a title, details, a phase (Before the event · During the event · After the event · Rollback), a due date, assigned users and reminders. Zero tasks is a valid state — the step is an offer, not a gate. Detail in Tasks and templates.

6 · Summary & send

The screen collects everything that was chosen and adds a free-text Operational notes field. Create schedule and send does three things: it saves the event, opens a request in the ticketing system, and issues the calendar invitations.

The request is opened only when the update type has a request template. Without one the screen says "No template configured for opening a request" — a missing setting, not a connection error.

After sending, two status rows appear — Request and Calendar invite — each with its own result.

Entering the wizard with data already filled in

Several screens open the wizard with some fields prepopulated:

From	What arrives
Calendar — Schedule on this day	The date and a default window
Server list	The selected servers
Equipment list	The selected equipment
Databases	The selected databases
Vulnerability register	The affected servers, and the vulnerability id in the notes field
Suggestions	The recommended update type

The number of items carried this way is capped, and when the list is truncated the screen says so.

A database selection is the one case applied late, rather than as the wizard opens: which source is correct depends on the update type, and at the moment of entry no type has been chosen yet. Until one is, the selection waits in a message at the top of the screen. If the chosen type does not work against databases, the message says the selection will not be attached — it is never silently converted.