The Client Note Section has been removed from the Check In/Out (and Quick Complete) flows due to issues determining assignment of the Client Note record when completing Appointments with multiple Participants.
Client Notes can still be created at any point in the Appointment life-cycle using the Note quick action (where they can be assigned to a specific Participant) from Manage Appointment or from anywhere in the application using the Client Note action from the Maica Global Actions menu.
This has been replaced by the Manage Participant Notes feature that can be accessed anytime in the Manage Appointment modal and in the Planner on a single click of an Appointment (when the feature is enabled).
Additionally, the Manage Participant Notes feature was extended to provide the ability to insert a Note Template (see below).
A bug was identified in the creation of Billable Notes where funding was incorrectly drawn from an inactive Agreement Item instead of the current active Agreement Item (and Service Agreement).
This issue occurred when an Agreement Expiry Tolerance (days) setting was both configured and disabled (set to 0), causing an expired Service Agreement within the tolerance period to be selected over the active one.
The logic has been updated to always prioritise the active Service Agreement and its associated Agreement Item, regardless of any Agreement Expiry Tolerance (days) settings.
When no active Service Agreement and Agreement Item exist, the system will then check the Tolerance Setting and attempt to retrieve an Agreement Item within the defined tolerance period.
This fix ensures that Billable Notes are now correctly linked to the active funding source, aligning with the expected business rules and preventing unintended funding from inactive agreements.
A bug was identified in the handling of Appointment scheduling for Resources with approved Unavailability records. When a Resource has an approved Unavailability record, Maica unschedules that Resource from an Appointment if the Unavailability record overlaps with the Appointment. However, the scheduled batch processes that create Appointment records did not adhere to this logic.
Unavailability records through recurring Unavailability schedules or manual user entries.Appointment records are created via a recurring Appointment schedule.Appointment schedule creates an Appointment after an Unavailability record has been approved, the Resource is still scheduled for that Appointment (if they are the designated Appointment Resource on the Master Appointment).
No Resource with an approved Unavailability record should be scheduled for an Appointment when the relevant setting is enabled, ensuring consistent and predictable system behaviour.
A change has been implemented in the scheduled job that creates Appointment records. When an Appointment is created via the batch job, the system will now:
Appointment Resource records – Examine each assigned Resource.Unavailability – Check if any Appointment Resource has an overlapping approved Unavailability record.Appointment Resource – If an overlapping Unavailability record is found, remove that Resource from the Appointment.
This fix ensures that Appointment scheduling aligns with user expectations by preventing Resources with approved Unavailability records from being scheduled, regardless of the timing of Appointment creation.
An issue was identified where the Resource Availability Score in the Find Resources feature of the Appointment modal was not updating to reflect cancelled Appointment records.
Previously, if a Resource was part of a cancelled Appointment, their Availability Score remained at 0%, even when they were actually available following the cancellation. This caused confusion when scheduling new Appointments, as the Resource would incorrectly appear as unavailable.
With this fix, the Resource Availability Score now accurately reflects real-time availability, ensuring that cancelled Appointment records no longer impact scheduling decisions.
Appointments were still being generated on cancelled schedules due to a validation gap in the batch process.
The batch process now respects the cancelled status of Appointments and Schedules, preventing unintended duplicate Appointments from being created.
An issue was identified where the Manage Travel component was defaulting the Travel Time to 60 minutes. If a user clicked Submit without adjusting this value, Maica would populate 60 minutes of travel time into the Appointment Travel Time field. This posed a risk of incorrectly charging or paying for travel that didn’t occur.
60-minute value has been removed from the Travel Time field.Manage Travel feature to ensure that users manually enter a Travel Time before saving the record.
This update ensures that only actual travel time is recorded, preventing unintentional travel-related charges.
The value Fortnightly has been removed from the Schedule Frequency Global Value Set due to issues being caused in the Recurring Appointment Schedule.
To create an Appointment Schedule on a fortnightly basis, the following configuration can now be used:
Frequency = Weekly.
Interval = 2
Please contact Maica Support if you have existing Appointment Schedule records with a Fortnightly Frequency, as we can rectify the data via a bulk operation.
This script retrieves 5000 Appointments max in one run where Schedule → Master → Original Start is not blank. It then analyses and removes Original values from all Masters and then from all other appointments where Original = Master Original, regardless of the status.
