xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
Auto DMSConsumer Goods DMSSales Force Automation (SFA) FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Business Hour — entity reference
REFERENCE · Last reviewed

Business Hour — entity reference

A working calendar: a time zone, the working weekdays and one daily working window. It takes effect only where another record links to it. An SLA policy's calendar sets case due dates, and a case's calendar shifts deadlines after a paused clock resumes. A resource's calendar, or else its default branch's, drives mobile attendance gates, the attendance day and time zone, auto check-out and time-off day counting. A branch's calendar sets which weekdays open appointment slots. For the SLA clock and attendance the calendar counts as 24x7 unless the working days are non-zero and both day start and day end are set with end later than start. Holidays are separate records, and only the SLA clock reads their Business Hours link. New records are named from the BH numbering series, which replaces the typed name.

Fields

FieldLabelTypeRequiredWhat it does
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DayEndMinutesDay End (min)NumberEnd of the daily working window in minutes after local midnight, for example 1080 for 18:00. It must be later than the day start, so a window across midnight is not supported; otherwise the SLA clock and mobile attendance treat the calendar as 24x7.
DayStartMinutesDay Start (min)NumberStart of the daily working window in minutes after local midnight, for example 540 for 09:00. If empty, the SLA clock and mobile attendance treat the calendar as 24x7. Territory route planning uses the Sales default shift start instead. Slot release does not use it; slot times come from the slot template.
IdIdGuidYes
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYesThe record name. Required on the form, but on save it is replaced by the next number from the BH series while the Business Hours numbering setting is active, and that number is what Business Hours pickers show.
OwnerIdOwnerLookup → UserAccountYes
RecordTypeIdRecord TypeGuid, hidden
TimeZoneIdTime ZoneTextThe time zone the working days and window are read in, entered as a Region/City name such as Asia/Kolkata. Empty or unrecognised values are treated as UTC without any message. It decides local dates for attendance, time off, slot release and SLA due dates.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes
WorkingDaysMaskWorking Days (mask)NumberThe working weekdays as a sum of day values: Sunday 1, Monday 2, Tuesday 4, Wednesday 8, Thursday 16, Friday 32, Saturday 64, so Monday to Friday is 62 and Monday to Saturday is 126. 0 or empty means not configured, and the SLA clock, mobile attendance, appointment slot release and fiscal days then count every weekday as working.

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record
DeleteEntityDeleteDeleteDelete Entity
DeleteHeaderDeleteDeleteDeleteHeader
DeleteRowDeleteDeleteDeleteRow
EditEntityEditEditEditEntity
EditInLineListEditEditInlineEditInLineList
EditRowEditEditEditRow
NewNewNewNew
  • UserAccount — looks up via OwnerId
  • IncentivePlan — looks up via BusinessHoursId
  • UserAccount — looks up via ModifiedById
  • UserAccount — looks up via CreatedById
  • Case — referenced by via BusinessHoursId
  • Scheme — referenced by via BusinessHoursId
  • Branch — referenced by via BusinessHoursId
  • Resource — referenced by via BusinessHoursId
  • Branch — referenced by via PayrollBusinessHoursId