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/Availability Request — entity reference
REFERENCE · Last reviewed

Availability Request — entity reference

A request a field user raises on the mobile app for someone else to approve or decline. Three mobile screens create it: Regularize on the attendance calendar (correct a day's check-in and check-out), Outlet Transfer (move outlets between beats) and Visit Route Regularization (change a beat's schedule). The delivered record carries only Request Name, Request Type and Status; the day, punch times, reason, requester, beats and outlets are custom fields an administrator adds, and each screen is told their names. Raising a request changes nothing. Outlet transfer and beat requests are decided by the requester's manager on the same screen, which then makes the change. Attendance requests go through the entity's approval process, and approving one does not rewrite the attendance day. The entity is in no delivered app and has no delivered approval process, number series or picklist values.

Fields

FieldLabelTypeRequiredWhat it does
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
IdIdGuidYes
ModifiedByIdModified ByLookup → UserAccountYes
NameRequest NameTextYesThe request's name. Required. The mobile screens fill it in from the request type and date, for example Attendance 2026-10-05. No number series is delivered; an active document numbering setting added by an administrator replaces the typed name.
OwnerIdOwnerLookup → UserAccountYes
RecordTypeIdRecord TypeGuid, hidden
RequestTypeRequest TypePickListWhich kind of request this is. Delivered with no picklist values. The mobile screens write Attendance, Outlet Transfer or Visit Regularization by default (configurable per screen) and list only requests of their own type.
StatusStatusPickListWhere the request has got to. Delivered with no picklist values. The mobile screens start requests at Draft and read Approved and Rejected; a blank status reads as Draft. Outlet transfer and beat screens write Approved or Rejected when the manager decides. For attendance requests, Status changes only if the approval process has field updates that set it, and a rejected status reopens the date for a new request.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
BulkDeleteDeleteDeleteDelete the selected records.
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete in a list page
EditEditEditEdit
EditInListEditEditEdit in page.
NewNewNewNew