You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, there is no integration between the Provider Schedule and Frappe HR. If a provider is also an employee and is scheduled for work, the system does not check whether they are on leave. This can lead to bookings being made for providers who are unavailable.
Describe the solution you'd like
The Provider Schedule should be integrated with Frappe HR to account for employee leave. If a provider is on any type of leave (sick leave, vacation, etc.), the system should prevent bookings for them during that period.
This could be implemented by:
Automatically blocking scheduling if the provider has approved leave.
Displaying leave status within the scheduling interface.
Sending notifications when a booking attempt conflicts with an employee’s leave.
Describe the alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, there is no integration between the Provider Schedule and Frappe HR. If a provider is also an employee and is scheduled for work, the system does not check whether they are on leave. This can lead to bookings being made for providers who are unavailable.
Describe the solution you'd like
The Provider Schedule should be integrated with Frappe HR to account for employee leave. If a provider is on any type of leave (sick leave, vacation, etc.), the system should prevent bookings for them during that period.
This could be implemented by:
Automatically blocking scheduling if the provider has approved leave.
Displaying leave status within the scheduling interface.
Sending notifications when a booking attempt conflicts with an employee’s leave.
Describe the alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: