Currently, some Customer Service Calendars contain only one calendar_calendar_rules, while others have multiple rules. When all working hours are the same during the creation of a Customer Service Calendar, only one calendar_calendar_rules is generated. However, if working hours are modified and saved, the system splits them into two or more rules.

Actually, we just open and save the working hours without even modifying, it will be considered as new value and next split occurs.

Developers sometimes rely on the Calendar entity to determine working days and hours. Due to the inconsistent response format across different calendars, this has led to issues in any existing logic. The Same logic that works in one environment will throw error in another environment since the response is different unfortunately. Additionally, the "Calendar Rule" entity is totally backend we cannot use any other ways to query it.

We propose unifying the JSON response format of the Calendar entity to ensure consistency. This change is crucial as the current variation in response structure significantly impacts business processes and automation dependent on these values.