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 Activity — entity reference
REFERENCE · Last reviewed

Visit Task Activity — entity reference

The record of one activity actually worked on a visit, such as a taken order, a filled checklist or a captured signature. It sits under the visit's task record and points back to the template activity it came from. Visits are not given activity records in advance: the web and mobile visit screens show the template's activities live and create this record the first time the representative works an activity, or when the representative adds an extra activity to a task during the visit. A visit nobody worked therefore has no activity records. The record holds a short summary of what was captured, the full capture as structured text, an amount where one applies, and a link to any document the activity created (order, invoice, payment, delivery order, service order or product demo). Photos and signatures are attached to it as files, and checklist answers are stored as checklist lines that point to it. Saving any change to an activity that is not yet Completed marks it Completed and stamps its End Time. Only the resource the visit plan is assigned to can start or complete it.

Fields

FieldLabelTypeRequiredWhat it does
ActivityNameActivity NameTextThe name shown on the activity row of the visit's task card. Copied from the template activity when the record is created, or typed by the representative when they add an extra activity during the visit.
ActivityTypeActivity TypePickListDecides which capture form opens, for example Take Order, Checklist, Digital Signature or General Task. Copied from the template activity, or chosen by the representative for an extra activity. A type the visit screens do not recognise opens a simple start-and-complete form. Values: Take Order, Checklist, Digital Signature, Photo Capture, General Task, Stock Check, Payment Collection, Returns Pickup, Merchandising Audit, Asset Verification, Competitor Capture, New Outlet Registration, Parts Consumption, Meter Reading, Proof of Delivery, Time & Expense, Barcode Scan, Safety Compliance, Schedule Follow-up, Lead Capture, Log Case, Custom Form, Product Demo, Generate Invoice, Delivery Fulfillment, Service Order Execution.
BooleanValueBoolean ValueBooleanYesNot written by the visit screens.
ChecklistTemplateIdChecklist TemplateLookup → ChecklistTemplateThe checklist a checklist-type activity runs, copied from the template activity. Its answers are stored as checklist lines that point to this activity, or to the service order when the template activity routes them there.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
CurrencyValueCurrency ValueCurrencyThe amount captured, where the activity type records one. Take Order on the web stores the order's net total here.
DateDateTimeOnly
DateTimeValueDate Time ValueDateAndTime
DateValueDate ValueDateAndTime
DecimalValueDecimal ValueNumber
DeliveryOrderIdDelivery OrderLookup → DeliveryOrderThe delivery order worked by a Delivery Fulfillment activity.
DurationDurationCalculated (calculated)Minutes between Start Time and End Time, calculated on save. It is 0 when Start Time is empty, which is common.
EmailEmailText
EndTimeEnd TimeTimeOnlyStamped by the server, in UTC, when the activity changes to Completed.
FieldNameField NameTextFor activity types that bind to a field of a record, the field to use. Copied from the template activity; the template is the fallback.
FieldValueField ValueTextFor activity types that bind to a field of a record, the value to use. Copied from the template activity; the template is the fallback.
FormLayoutIdForm LayoutExternalIdFor entity-form activity types, the create form to open instead of the record type's default one. Copied from the template activity; the template is the fallback.
GeolocationValueGeo Location ValueTextNot written by the visit screens. Captures that record a location keep it in the full capture text.
IdIdGuidYes
InvoiceIdInvoiceLookup → InvoiceThe invoice linked by a Payment Collection activity.
IsActivityCompletedIs Activity CompletedBooleanNot stored. The visit screens send it when an activity is completed, but the value is dropped, so Status is the only completion signal on a saved record.
IsDisabledIs DisabledBooleanYesNot set by the visit screens and not read by them.
IsHiddenIs HdenBooleanYesCopied from the template activity when the record is created. A hidden activity is not shown on the visit.
LongTextValueLong Text ValueMultiLineTextThe full capture as structured text, written when the activity is completed: entered values, product lines, readings or the linked record, depending on the activity type. Reopening a completed activity during the visit edits this capture.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameText
NumericValueNumeric ValueNumberNot written by the visit screens. Numeric checklist answers are stored on the checklist lines instead.
ObjectNameObject NamePickListFor entity-form activity types, the kind of record the activity creates. Copied from the template activity; if it is missing on the record, the visit screens read it from the template. Values: Sale Order, Sale Invoice, Repair Order.
OrderIdOrderLookup → OrderThe order the activity created or linked, for Take Order and Generate Invoice activities.
OwnerIdOwnerLookup → UserAccountYes
PaymentIdPaymentLookup → PaymentThe payment recorded by a Payment Collection activity.
PerformAutomaticallyPerform AutomaticallyBooleanYesNot read by the visit screens.
PhonePhoneText
PlannedDurationPlanned DurationCalculated (calculated)Minutes between Planned Start Time and Planned End Time, calculated. Usually 0 because the planned times are not filled in.
PlannedEndTimePlanned End TimeDateNot filled in by the visit screens.
PlannedStartTimePlanned Start TimeTimeOnlyNot filled in by the visit screens. Planned times for the visit are kept on the visit itself.
ProductDemoIdProduct DemoLookup → ProductDemoThe product demo recorded by a Product Demo activity.
RecordTypeIdRecord TypeGuid, hidden
RNAExternalIdRNA ExternalText
SequenceNumberSequence NumberNumberThe activity's position inside its task, copied from the template activity. An extra activity added during the visit is placed after the task's existing activities.
ServiceOrderIdService OrderLookup → ServiceOrderThe service order an activity worked on, for service-order activity types and for checklists whose answers are stored against the service order.
StartTimeStart TimeTimeOnlyStamped by the server only when an existing activity record changes to Started. Activities the visit screens create already started, which is the usual case, keep Start Time empty. The task record carries the task's own start time.
StatusStatusPickListStarted when the record is created by the web visit screen and when a General Task is started; Completed when the activity is finished. Any saved change to an activity that is not yet Completed sets it to Completed, so editing the record by hand also completes it. A completed activity cannot be set back by the visit screens. The visit screens treat Started and Ongoing as in progress. Completed is written by the system even though it is not one of the listed values, and Draft is never set by the system. Values: Started, Draft.
TextValueText ValueTextA one-line summary of what was captured, for example the order number and amount, Signature captured, or the name of the record an entity form created.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes
URLURLText
VisitIdVisitLookup → VisitThe visit the activity was worked on. Filled in by the visit screens.
VisitTaskIdVisit TaskLookup → VisitTaskThe visit's task record that the activity belongs to. The task record is created first, from the template entry, and the activity is created under it.
VisitTaskTemplateActivityIdVisit Task Template ActivityLookup → VisitTaskTemplateActivityThe template activity this record was created from. Empty for an extra activity the representative added during the visit. The visit screens use it to match the record to its place in the template, and read the Mandatory flag from the template activity, so extra activities are never mandatory.

Actions

ActionLabelTypeWhat it does
BulkDeleteDeleteDeleteDelete
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete
EditEditEditEdit
EditEntityEditEditEditEntity
EditInLineEditEditInlineEdit
EditInListEditEditInlineEdit In List Header
NewNewNewNew