Learn about how Resources can manage their Unavailability within Maica
Maica supports the management of Unavailability records which essentially mark any given Resource as not available for inclusion into an Appointment or Shift.
The Manage Unavailability Tool essentially allows you to manage and create these records directly from the Planner, as demonstrated below.
Maica offers the ability to either create a single Unavailability for any given Resource or multiple at the same time by simply adding multiple Resources into the Resources(s) input.
It is important to note that if multiple Resources are selected, Maica will create an individual Unavailability record for each Resource to ensure that each Resource can manage their own Unavailability.
To create a new Unavailability record, simply click on the Unavailability icon in Maica's Planner, select the + New button and complete the fields as per the below screenshot.
Where multiple Resources are selected, any future Recurring Unavailability records will be created via Maica's batch feature so you might not see these in the Planner straight away.
Please note, when an Unavailability Record is created, Maica will automatically remove the associated Resource from any assigned Appointments or Shifts during the Unavailability period.
| Field | Description |
|---|---|
The Recurring Unavailability follows the same execution logic as Appointments and Shifts which is further described .
Start and End Date/Time
The Start and End date and time of the Unavailability.
Resource(s)
The Resource(s) for whom the Unavailability record will be created.
Type
Status
Notes
Additional notes that can be taken during the creation of the Unavailability.
Create a corresponding Timesheet
This indicates that a corresponding timesheet activity will be generated for each Unavailability.
This is a Recurring Unavailability
The type of Unavailability being created. This list is configurable via Maica .
The status of Unavailability being created. This list is configurable via Maica .
If a Recurring Unavailability is required, this enables the capturing of the required details as documented further .