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/Visit Task Template Entry — entity reference
REFERENCE · Last reviewed

Visit Task Template Entry — entity reference

One task inside a visit task template: a named group of activities that shows as one task card on every visit carrying the template. Visits do not get copies of their tasks when a plan or visit is created. The web and mobile visit screens read the template's entries live, in Sequence Number order, and create the visit's own task record only when the representative first starts or completes an activity under the entry. Adding, renaming, hiding or re-ordering an entry therefore reaches every visit on which nobody has touched that task yet, including visits already planned. An entry with no visible activities is not shown. The work itself (the capture forms, mandatory flags and checklists) is defined on the entry's activities, not on the entry.

Fields

FieldLabelTypeRequiredWhat it does
CanExecuteOutOfSequenceExecute Out Of SequenceBooleanStored but not used: no visit screen reads it, and tasks are never held to their sequence. Within a task, the order the representative must follow comes from the activities' Mandatory flags.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTime
DescriptionDescriptionTextFree-text notes for administrators. It is not shown to the representative on the visit.
EntryNameEntryNameLongMultiLineTextA long-text alternative name. It is only used as the task card title when Name is empty. It is on no delivered form.
IdIdGuidYes
IsHiddenHiddenBooleanHides the task and all of its activities on visits where nobody has started the task yet, without deleting it. On a visit where the task was already started, it stays visible. Hidden entries are also left out of the day-end must-do and planned-minutes scores.
IsMandatoryMandatoryBooleanStored but not used: no visit screen reads it. To make work compulsory, set Mandatory on the entry's activities instead; those are what lock other activities and, on mobile, block a Productive visit close.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextThe task card title the representative sees on the visit. It is copied onto the visit's task record when the task is first started. If Name is empty, the entry's EntryName is used, then Task followed by its position.
OwnerIdOwnerLookup → UserAccountYes
RecordIdRecordTextNot used by the visit flow. It is on no delivered form.
RecordTypeIdRecord TypeGuid, hidden
SequenceNumberSequence NumberNumberThe order of the task cards on the visit, lowest first. Defaults to 0. Give every entry a distinct number starting at 1: entries left at 0 fall back to their list position, which can interleave with numbered entries. The number is copied onto the visit's task record when the task is first started, so re-numbering entries later does not move tasks already started on a visit.
TaskDurationTask Duration (Mins)NumberThe planned minutes for the task. The visit's task card shows it as N mins until the task is started, after which the card shows the elapsed time. It is not used by route or territory optimisation, and the day-end planned-minutes score adds up the activities' durations, not this value.
TaskTypeTask TypePickListA classification of the task. The only delivered value is Perform Visit Activities. It is copied onto the visit's task record, but neither the web nor the mobile visit screen behaves differently by task type. Values: Perform Visit Activities.
TotalActivitiesTotal ActivitiesCalculated (calculated)The number of activities defined under the entry, hidden ones included. Calculated, read-only.
UIPropsUI PropsText
UniqueIdentifierUnique entifierText, uniqueAn optional external key, for example for an integration. It must be unique across the tenant. It is on no delivered form and nothing in the visit flow reads it.
UpdatedDateTimeModified DateDateAndTime
VisitTaskTemplateIdVisit Task TemplateLookup → VisitTaskTemplateThe visit task template this entry belongs to. Filled automatically when the entry is added from the template's Visit Task Template Entry tab.

Actions

ActionLabelTypeWhat it does
BulkDeleteDeleteDeleteDelete
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete
EditEditEditEdit
EditInLineEditEditInlineEdit
EditInListEditEditEdit
NewNewNewNew
NewInLineNewNewInlineNewInLine