Output Data Pipelines

💡These lists show the Data Pipelines that Output Templates can use. A Data Pipeline is a set of data, for example, a transaction's header details or its items. In the template designer, the pipelines are listed in the Data Tree.

Customers and Suppliers#

Customers#

The following Data Pipelines can be used on Customers Output Templates.

• Cus_Rec: The selected customer:
  • Name.
  • Account number.
  • Contact details.
  • Addresses.
  • Category.
  • Rep.
  • Terms.
  • Limits.
  • Currency.
  • Bank details.
  • Notes.
• Cus_All: One row per customer on the list:
  • Name.
  • Account number.
  • Contact details.
  • Addresses.
  • Category.
  • Rep.
  • Terms.
  • Limits.
  • Currency.
• Cus_Contacts: All the selected customer's contacts:
  • Name.
  • Position.
  • Phone numbers.
  • Email.
  • Groups.
  • Notes.
• Cus_Addresses: All the selected customer's addresses, with the default address marked.
• Cus_Attachments: All the selected customer's attachments: description, link and who added them.

Suppliers#

The following Data Pipelines can be used on Suppliers Output Templates.

• Sup_Rec: The selected supplier:
  • Name.
  • Account numbers.
  • Contact details.
  • Addresses.
  • Category.
  • Terms.
  • Credit limit.
  • Currency.
  • Bank details.
  • Notes.
• Sup_All: One row per supplier on the list:
  • Name.
  • Account numbers.
  • Contact details.
  • Addresses.
  • Category.
  • Terms.
  • Currency.
• Sup_Contacts: All the selected supplier's contacts.
• Sup_Attachments: All the selected supplier's attachments: description, link and who added them.

Transactions#

Transaction Header#

The following Data Pipelines can be used on transaction Output Templates.

• Trans_All: All the transaction headers on the list: number, dates, customer or supplier, totals, status, priority and the details of the transaction each was created from. Fields include PURCH_PRIORITY (checked = priority) and CREATEDFROMDATE, CREATEDFROMTOTAL and CREATEDFROMVARIANCE, which can add an invoice's details to a credit note template.
• Trans_Rec: The selected transaction's header: number, dates, customer or supplier, totals, status, priority and the details of the transaction it was created from (for example, the invoice on a credit note). Fields include PURCH_PRIORITY (checked = priority) and CREATEDFROMDATE, CREATEDFROMTOTAL and CREATEDFROMVARIANCE, which can add an invoice's details to a credit note template.
• Trans_Company: The customer or supplier on the transaction:
  • Name.
  • Account number.
  • Contact details.
  • Addresses.
  • Terms.
• Trans_Contact: The customer's or supplier's contact person on the transaction.
• Trans_AssignTo: The staff member the transaction is assigned to, with their contact details.
• Trans_Rep: The rep on the transaction, with their contact details.
• Trans_CAA: The age analysis of the transaction's customer:
  • Current.
  • 30.
  • 60.
  • 90.
  • 120 days.
  • Unallocated.
  • Work in progress.
  • Totals.
• Trans_Comp_UDF: The user-defined fields of the customer or supplier on the transaction.
• Trans_Entity_UDF: The user-defined fields of the item linked to the transaction header.
• Trans_Entity: The item linked to the transaction header:
  • Code.
  • Description.
  • Image.
  • Specification.
• Trans_BusEntity: The business entity on the transaction:
  • Name.
  • Registration.
  • VAT numbers.
  • Contact details.
  • Addresses.
  • Bank details.
  • Images.
  • Masthead.
• Trans_Timekeeping: All the completed timekeeping records on the transaction:
  • Item.
  • Service.
  • Cost Centre.
  • Operator.
  • Times.
  • Cost.
  • Customer.
  • Approval status.
• Trans_Payments: The transaction's Payment Schedule, in order.
• Trans_StockItems: All the stock batches received or issued on every transaction in the transaction's flow:
  • Item.
  • Serial or batch number.
  • Bin.
  • Quantity.
  • Transaction number.
• Trans_UDF: The transaction's user-defined fields.
• Trans_Flow_Timekeeping: All the timekeeping records on every transaction in the transaction's flow:
  • Times.
  • Cost.
  • Operator.
  • Cost Centre.
  • Customer.
  • Transaction number.
• Trans_Finance: The transaction's loan finance details.
• Trans_Checklist_All: All the checklist items on the transaction, with their values, notes and who updated them.
• Trans_Checklist_Manual: The checklist items on the transaction that users tick by hand (manual and limit items).
• Trans_User: The staff member who created the transaction, with their contact details.
• Trans_Requestor: The staff member who requested the purchase, with their contact details.
• Trans_Manager: The manager who approves the purchase, with their contact details.
• Trans_Head: The head of department who approves the purchase, with their contact details.
• Trans_Signatures: All the signatures attached to the transaction, oldest first.
• Trans_Inventory: One row per stock item on the transaction:
  • In stock.
  • Reserved.
  • On order.
  • Available.
  • The quantity on this transaction.
  • What is left after it.
• Trans_WHT: The transaction's total paid to the bank and total withholding tax.

Totals Fields#

The transaction header pipelines include these totals, which can also be used in Custom Reports:

• TOTALCURRENCY: The total in the transaction's currency.
• TOTAL: The total excluding VAT, in the home currency.
• VATAMT: The VAT amount.
• TOTALVAT: The total including VAT, in the home currency.

Deposit Fields#

• DEPOSITPERCENT: The deposit percentage.
• DEPOSIT: The deposit amount.
• DEPOSIT_TEXT: The text to show when a deposit is requested, for example "Deposit (50%) 1,000.00". Blank when there is no deposit percentage.

Transaction Items#

The following Data Pipelines can be used on transaction Output Templates.

• Items_All: All the items on the transaction, including each item's total cost and batch number.
• Items_Rec: The selected item on the transaction, including its total cost and batch number.
• Items_StockItems: The stock batches (serial or batch number, bin and quantity) of the selected transaction item; the transaction must be in an inventory status.
• Items_Costs: All the estimate costs on the transaction, ordered by transaction item, estimate component, cost type and estimate order.
• Items_SerialNo: All the serial numbers of the selected transaction item.
• Item_Flexo: The flexo engineering image of the selected transaction item.
• Item_Pump_Install: The installation details of the selected transaction item's pump and motor: application, site specification and description.
• Item_Pump: The selected transaction item's pump:
  • Name.
  • Image.
  • Model.
  • Duty point.
  • Warranty.
  • Series.
  • Product data.
• Item_Motor: The selected transaction item's motor:
  • Name.
  • Image.
  • Model.
  • Warranty.
  • Series.
  • Product data.
• Item_UDF: The user-defined fields of the item linked to the selected transaction item.

Item Totals Fields#

• TOTALUNIT: The total per unit, after the adjustment, in the transaction's currency.

Transaction Estimates#

The following Data Pipelines can be used on transaction Output Templates.

• Est_Qty_Price: All the quantity price breaks in the selected item's estimate:
  • Quantity.
  • Subtotal.
  • Adjustment.
  • VAT.
  • Totals.
  • Unit price.
• Est_Summary: The summary lines of the selected item's estimate: caption, amount and percentage.
• Est_Desc: The description lines of the selected item's estimate, in order.
• Est_Spec: The specification lines of the selected item's estimate: each caption with its worked-out value.
• Est_Qty_Price_NonActive: The quantity price breaks in the selected item's estimate other than the selected quantity.
• Est_Params: The selected item's estimate parameters, one field per parameter name (for example, INP_DEPTH).
• Est_CompSum: All the cost lines of the selected item's estimate, by component and cost type:
  • Quantities.
  • Costs.
  • Selling prices.
  • Stock levels.
  • Provider.
  • Note.
  • Specification.
• Est_CompBudget: The budget lines of the selected item's estimate, by component.
• Est_Mat_Resolve: All the material lines resolved from the estimates on the transaction.
• Est_OW_Resolve: All the outwork lines resolved from the estimates on the transaction.
• Est_Services: All the services in the estimates on the transaction, with their item, component, quantities, provider and hours; usually grouped by service code.
• Est_Service_Mat: The materials in the same component as the service, with quantity and size.
• Est_Service_Ser: All the services in the same component as the service, in order, so the matching service can be highlighted.
• Est_Components: All the components (assemblies) in the estimates on the transaction, with their parent, quantity and unit; used for Worktickets grouped by assembly.
• Est_Components_Active: The active components in the selected item's estimate, with quantity, unit and totals.
• Est_Mat_Note: The note, specification and instruction of each resolved material line.
• Item_Est_Desc: The lines in the selected item's estimate that are ticked for the description (Desc), in order.
• Item_Est_Services: The active services in the selected item's estimate:
  • Component.
  • Provider.
  • Hours.
  • Quantity.
  • Costs.
  • Specification.
• Item_Est_Mat: The active materials in the selected item's estimate:
  • Component.
  • Quantity.
  • Waste.
  • Provider.
  • Costs.
  • Specification.

Estimate Parameters on a Template#

• You can place estimate parameters as individual fields on a template with the Est_Params pipeline.
• The form designer reads the fields from the Output Template you opened, so open the template from a transaction with an estimate item that has parameters.
• If the transaction has no estimate parameters, selecting Est_Params in the Data Tree shows a 'SQL statement cannot be empty' error.
• Each parameter's field name is P followed by the parameter's ID, for example, P12.
• The values are those of the transaction item being output.

The parameter types included are:

• Numbers: Input - Est. Qty, Input - Number, Input - Select Number, Calc - Numerical and Calc - Estimate Qty.
• Text: Input - Text, Input - Number > Text, Calc - Text and Items (the material name).

Services are not estimate parameters. They are in the Est_Services, Est_Service_Mat and Est_Service_Ser pipelines.

Transaction Images#

The following Data Pipelines can be used on transaction Output Templates.

• Est_Images_Rec: The images of the materials used in the selected item's estimate.
• Est_Images_All: The images of the materials used in all the estimates on the transaction.
• Items_Images: All the images of the items on the transaction where the transaction item is set to show its image.
• Item_Blobs: The image, note and specification of the item linked to the selected transaction item.
• Trans_Images: All the images in the transaction's Images tab, with their captions.
• Images_Item: All the images attached to the item linked to the selected transaction item, or to the transaction item itself.
• Images_Items: All the images attached to the items used on the transaction.
• Images_Trans: All the images attached directly to the transaction.
• Images_Flow: All the images attached to any transaction in the transaction's flow.
• PumpMotorImages_Item: The product, diagram and dimension images of the selected transaction item's pump and motor.

Accounting#

Ledger#

The following Data Pipelines can be used on Ledger Output Templates.

• Lgr_Rec: The selected transaction on the Ledger:
  • Number.
  • Date.
  • Reference.
  • Customer or supplier.
  • Totals.
  • Allocated.
  • Unallocated amounts.
  • Status.
• Lgr_Allocation: All the transactions the selected transaction is allocated to:
  • Number.
  • Date.
  • Type.
  • Amount.
  • Unallocated balance.
• Lgr_All: All the rows in the Transaction View or the Detailed Ledger View, depending on the view selected.
• Lgr_Items: All the items on the selected transaction:
  • Description.
  • Debit.
  • Credit accounts.
  • VAT.
  • Withholding tax.
  • Totals.
• Lgr_Filters: The Data Filter selections on the Ledger.
• Lgr_Warning: The warning shown for the selected transaction, with its debit and credit totals.
• Lgr_BusEntity: The business entity on the selected transaction:
  • Name.
  • Registration.
  • VAT numbers.
  • Contact details.
  • Bank details.
  • Images.
  • Masthead.

Customer Payments#

The following Data Pipelines can be used on Customer Payments Output Templates.

• Pay_Invoices: All the customer's outstanding transactions that the payment can be allocated to:
  • Date.
  • Type.
  • Number.
  • Reference.
  • Total.
  • Unallocated amount.

Supplier Payments#

The following Data Pipelines can be used on Supplier Payments Output Templates.

• SP_Rec: The selected supplier payment:
  • Supplier.
  • Bank account.
  • Payment date.
  • Status.
  • Entity.
  • Currency.
  • Subtotal.
  • Discount.
  • Total.
  • Reference.
  • Note.
• SP_Outstanding: All the supplier's outstanding invoices:
  • Type.
  • Number.
  • Date.
  • Reference.
  • Total.
  • Allocated.
  • Outstanding.
  • Approvals.
• SP_Trans: All the supplier invoices paid by the selected payment:
  • Type.
  • Number.
  • Date.
  • Reference.
  • Invoice total.
  • Amount paid.
  • Amount due.
• SP_All: All the supplier payments on the list:
  • Supplier.
  • Bank account.
  • Payment date.
  • Status.
  • Totals.
  • Reference.

Customer Age Analysis#

The following Data Pipelines can be used on Customer Age Analysis Output Templates.

• CA_List: One row per customer on the age analysis:
  • Account details.
  • Contact.
  • Terms.
  • Category.
  • The amount in each ageing period.
• AA_Invoices: The selected customer's outstanding transactions:
  • Date.
  • Type.
  • Number.
  • Reference.
  • Order.
  • Invoice numbers.
  • Total.
  • Paid.
  • Outstanding.
  • The transaction each was created from.
• CA_Record: The selected customer's age analysis:
  • Account details.
  • Contact.
  • Terms.
  • Category.
  • The amount in each ageing period.
• AA_DetLedger: The selected customer's or supplier's detailed ledger:
  • Date.
  • Transaction.
  • Reference.
  • Accounts.
  • Debit.
  • Credit.
  • Allocated amounts.
  • Running balance.
  • The transaction each was created from.
• CA_Filters: The Data Filter selections on the Customer Age Analysis.
• CA_BusEntity: The business entity selected in the Data Filter: name, registration and VAT numbers, contact details, bank details, images and masthead; only filled when an entity is selected. If no entity is selected, a warning appears when you click Output.

Supplier Age Analysis#

The following Data Pipelines can be used on Supplier Age Analysis Output Templates.

• SA_List: One row per supplier on the age analysis:
  • Account details.
  • Contact.
  • Terms.
  • Category.
  • Currency.
  • Entities.
  • The amount in each ageing period.
• SA_Record: The selected supplier's age analysis:
  • Account details.
  • Contact.
  • Terms.
  • Category.
  • Currency.
  • Entities.
  • The amount in each ageing period.
• SA_Invoices: The selected supplier's outstanding transactions:
  • Date.
  • Type.
  • Number.
  • Reference.
  • Invoice number.
  • Total.
  • Paid.
  • Outstanding.
  • The transaction each was created from.
• SA_Filters: The Data Filter selections on the Supplier Age Analysis.
• SA_BusEntity: The business entity selected in the Data Filter:
  • Name.
  • Registration.
  • VAT numbers.
  • Contact details.
  • Bank details.
  • Images.
  • Masthead.

Financial Statements#

The following Data Pipelines can be used on Financial Statements Output Templates.

• TrialBalance: One row per account on the Trial Balance's Accounts view:
  • Report.
  • Category.
  • Parent account.
  • Account number.
  • Opening balance.
  • Movement.
  • Debit.
  • Credit.
• TrialBalance_Detail: One row per transaction item on the Trial Balance's Transaction view:
  • Account.
  • Contra account.
  • Transaction.
  • Date.
  • Customer or supplier.
  • Reference.
  • Debit.
  • Credit.
• TrialBalance_Category: The Trial Balance rows for the Category view:
  • Account.
  • Contra account.
  • Transaction.
  • Debit.
  • Credit.
• TrialBalance_Filter: The Trial Balance's Data Filter selections.
• IS_Level1: The main sections of the Income Statement, such as Revenue and Cost of Sales.
• IS_Level2: The account groups and accounts in each Income Statement section.
• IS_Level3: The accounts in each Income Statement account group.
• FS_Period: The names of the period columns on the Financial Statements.
• FS_Filter: The Financial Statements' Data Filter selections.
• BS_Level1: The main sections of the Balance Sheet, including Assets, Liabilities and Equity.
• BS_Level2: The second level of the Balance Sheet: the lines under each main section.
• BS_Level3: The third level of the Balance Sheet: the lines under each level 2 line.
• BS_Level4: The fourth level of the Balance Sheet: the lines under each level 3 line.
• IS_Level4: The fourth level of the Income Statement: the lines under each level 3 line.

VAT Reconciliation#

The following Data Pipelines can be used on VAT Reconciliation Output Templates.

• VAT_Header: The selected VAT reconciliation:
  • Entity.
  • Period.
  • Status.
  • Input.
  • Output.
  • Balance.
  • Who last updated it.
• VAT_Transactions: All the transaction items included in the VAT reconciliation:
  • Transaction.
  • Date.
  • Accounts.
  • VAT input.
  • VAT output.
  • VAT number.
  • VAT Type.
• VAT_Filter: The date, branch and status selected in the VAT Reconciliation's Data Filter.
• VAT_Sum_TransTypes: One row per Transaction Type in the VAT reconciliation, with its debit and credit totals.
• VAT_Sum_VATTypes: One row per VAT Type in the VAT reconciliation, with its input and output totals.

Cashup#

The following Data Pipelines can be used on Cashup Output Templates.

• Cashup_Rec: The selected cash-up:
  • Dates.
  • Users.
  • Status.
  • Totals.
  • Counted amount.
  • Variance.
  • The shortfall or surplus transaction.
• Cashup_All: All the cash-ups on the list:
  • Dates.
  • Users.
  • Status.
  • Totals.
  • Counted amount.
  • Variance.
• Cashup_Coins: The notes and coins counted for the cash-up.
• Cashup_Items: One row per payment type on the cash-up: system total, counted total and variance.
• Cashup_Trans: All the transactions in the cash-up period:
  • Number.
  • Date.
  • Customer.
  • Amount.
  • The user who created them.

Cost of Sales#

The following Data Pipelines can be used on Cost of Sales Output Templates.

• CoS_Items: One row per item on the Cost of Sales:
  • Transaction.
  • Item.
  • Quantity.
  • Category.
  • Customer.
  • Status.
  • The cost.
  • Profit figures.
• CoS_Ledger: The detailed inventory ledger for the selected account:
  • Transaction.
  • Date.
  • Item.
  • Accounts.
  • Quantity.
  • Unit price.
  • Stock price.
  • Variance.
  • Debit.
  • Credit.
  • Balance.
• CoS_Trans: One row per transaction on the Cost of Sales:
  • Number.
  • Date.
  • Customer.
  • Status.
  • Issued.
  • Returned.
  • Purchases.
  • Expenses.
  • Labour.
  • Total.
  • Cost.
  • Profit.
  • GP.
  • Mark-up.

Inventory#

Inventory#

The following Data Pipelines can be used on Inventory Output Templates.

• Inv_Default: One row per stock item on the Inventory list:
  • Category.
  • Description.
  • Code.
  • Location.
  • Bin.
  • Quantities.
  • Prices.
  • The start.
  • End values for the period.
• Inv_Ledger: The detailed inventory ledger for the selected account:
  • Transaction.
  • Date.
  • Item.
  • Accounts.
  • Quantity.
  • Unit price.
  • Stock price.
  • Variance.
  • Debit.
  • Credit.
  • Balance.
• Inv_Trans: One row per stock movement in the period:
  • Item.
  • Category.
  • Customer.
  • Quantity.
  • Unit price.
  • Total.
  • Location.
  • Transaction.
• Inv_BatchItems: One row per stock batch:
  • Item.
  • Location.
  • Bin.
  • Serial or batch number.
  • Quantity in.
  • Out.
  • Price.
  • Expiry date.
  • Supplier.
• Inv_BatchMovement: All the movements of the selected stock batch:
  • Transaction.
  • Date.
  • Quantity in.
  • Out.
  • Location.
  • The transaction each was created from.
• Inv_SerialNo: One row per serial number:
  • Item.
  • Location.
  • Transaction.
  • Date.
  • Customer or supplier.
  • Reference.
• Inv_Replenishment: One row per stock item to replenish:
  • Minimum.
  • Reorder levels.
  • Quantities.
  • Supplier.
  • Price.
  • Order quantity.
• Inv_Over_Under: One row per stock item with its demand compared with what is available:
  • Quantities.
  • Variance.
  • Stock price.
  • Supplier.
  • Lead days.
• Inv_Ageing: One row per stock item with the value of stock held in each age period, from 30 days to more than four years.
• Inv_Filter: The Data Filter selections on the Inventory screen.

Pricing#

The following Data Pipelines can be used on Pricing Output Templates.

• Pricing_Sup: One row per supplier price:
  • Item.
  • Supplier.
  • Supplier reference.
  • List price.
  • Quantity.
  • Adjustment.
  • Currency.
• Pricing_Inv: One row per stock item's inventory price:
  • Last purchase order.
  • Goods received prices.
  • Supplier price.
  • Stock price.
  • Variance.
• Pricing_Sell: One row per selling price:
  • Item.
  • Price List.
  • Cost price.
  • Selling price.
  • Adjustments.
  • Margin.
  • Currency.
• Pricing_Filter: The Data Filter selections on the Pricing screen.
• Pricing_Service: One row per service price:
  • Service.
  • List price.
  • Set-up.
  • Speed hours.
  • Cost Centre.
  • Rate.

Stock Check#

The following Data Pipelines can be used on Stock Check Output Templates.

• Stk_Check: One row per item counted on the stock check:
  • Item.
  • Location.
  • Bin.
  • Serial number.
  • System quantity.
  • Counted quantity.
  • Variance.
  • Price.
  • Totals.

MRP#

The following Data Pipelines can be used on MRP Output Templates.

• MRP: One row per item needed:
  • Quantity required.
  • In stock.
  • Reserved.
  • On order.
  • Available.
  • Shortfall.
  • Lead days.

Production#

Production Planning#

The following Data Pipelines can be used on Production Planning Output Templates.

• PB_Mat: One row per material line on the Materials view:
  • Transaction.
  • Item.
  • Location.
  • Dates.
  • Quantities ordered.
  • Reserved.
  • In stock.
  • Available.
  • Issued.
  • On purchase order.
• PB_Mat_Filter: The Data Filter selections on the Materials view.
• PB_Owk: One row per outwork line on the Outwork view:
  • Transaction.
  • Item.
  • Dates.
  • Quantity.
  • Purchase order quantity.
  • Due date.
  • Status.
• PB_Owk_Filter: The Data Filter selections on the Outwork view.
• PB_Tasks: One row per task on the Tasks view:
  • Transaction.
  • Dates.
  • Customer.
  • Stage.
  • Operator.
  • Status.
  • Estimated quantity.
  • Time.
  • Actual hours.
  • Notes.
• PB_Tasks_Filter: The Data Filter selections on the Tasks view.
• PB_Trans: One row per item on the Transactions view:
  • Transaction.
  • Dates.
  • Customer.
  • Entity.
  • Item.
  • Assigned user.
  • Rep.
  • Status.
  • Estimated.
  • Actual time.
  • Progress.
  • Quantities.
• PB_Trans_Filter: The Data Filter selections on the Transactions view.

Production#

The following Data Pipelines can be used on Production Output Templates.

• Production_Task: The selected production task:
  • Transaction.
  • Item.
  • Dates.
  • Quantity.
  • Customer.
  • Contact.
  • Assigned user.
  • Status.
  • Actual.
  • Variance hours.
  • Note.
  • Specification.

Tracker#

The following Data Pipelines can be used on Tracker Output Templates.

• Tracker: The fields on the open Tracker, as filled in by the current user.

Non-Conformance Reports#

The following Data Pipelines can be used on Non-Conformance Reports Output Templates.

• NCR_Rec: The selected non-conformance report:
  • Category.
  • Type.
  • Customer or supplier.
  • Status.
  • Dates.
  • Owner.
  • Assigned user.
  • Reference.
  • Problem.
  • Containment.
• NCR_All: All the non-conformance reports on the list:
  • Category.
  • Type.
  • Customer or supplier.
  • Status.
  • Dates.
  • Owner.
  • Reference.
• NCR_Staff: The staff members on the selected non-conformance report, with their roles.
• NCR_Progress: The progress notes on the selected non-conformance report, newest first.
• NCR_Cost: The costs of the selected non-conformance report:
  • Transaction.
  • Reference.
  • Date.
  • Total.

Compounds#

The following Data Pipelines can be used on Compounds Output Templates.

• Compounds: The selected compound sample:
  • Sample.
  • Test details.
  • Item.
  • Linked transaction.
  • Captions.
  • The minimum.
  • Maximum values.

Flexo Engineering#

The following Data Pipelines can be used on Flexo Engineering Output Templates.

• plFlexoTooling: The selected flexo engineering record:
  • Press.
  • Material.
  • Gear.
  • Cylinder.
  • Print repeat.
  • Plate.
  • Bearer settings.
  • The image.

Office#

Service Manager#

The following Data Pipelines can be used on Service Manager Output Templates.

• CSM_Rec: The selected ticket:
  • Customer.
  • Contact.
  • Status.
  • Category.
  • Severity.
  • Dates.
  • Rep.
  • Assigned user.
  • Reference.
  • Project details.
• CSM_All: All the tickets on the list:
  • Customer.
  • Contact.
  • Status.
  • Category.
  • Severity.
  • Dates.
  • Rep.
  • Assigned user.
• CSM_Response: The selected ticket's responses and activity, with who added them.
• CSM_Detail: The selected ticket's details as shown in its Detail panel.
• CSM_MeterData: The meter readings linked to the selected ticket or its asset:
  • Date.
  • Reading.
  • Quantity.
  • Unit.
  • Transaction.
• CSM_Costing: The parts linked to the selected ticket's asset:
  • Description.
  • Code.
  • Unit.
  • Yield quantity.
  • Quantity in stock.
• SM_Components: All the components of the selected project:
  • Description.
  • Groups.
  • Total.
  • Percentage complete.
  • Percentage invoiced.
  • The amount still to invoice.
• SM_ProjectLevel1: The top-level tasks of the selected project:
  • Dates.
  • Duration.
  • Hours.
  • Actual hours.
  • Status.
  • Notes.
• SM_ProjectLevel2: The tasks under each top-level project task:
  • Dates.
  • Duration.
  • Hours.
  • Status.
  • Groups.
• SM_ProjectLevel3: The tasks under each level 2 project task:
  • Dates.
  • Duration.
  • Hours.
  • Status.
  • Groups.
• SM_ProfitLoss: The selected ticket's profit and loss: the income and expense lines with their totals.

Workflows#

The following Data Pipelines can be used on Workflows Output Templates.

• WF_Main_Rec: The selected workflow record's header.
• WF_Items: All the items on the selected workflow record.
• WF_Remind: The reminders on the selected workflow record.
• WF_Main_All: All the workflow records on the list.
• WF_UserFields: The user-defined fields of the selected workflow item.
• WF_Item_Rec: The selected item on the workflow record.
• WF_FieldsComp: The user-defined fields of the customer linked to the workflow record.
• WF_FieldsItem: The user-defined fields of the item linked to the workflow item.
• WF_UserFields_Header: The user-defined fields of the selected workflow record's header.

Reminders (Workspace)#

The following Data Pipelines can be used on Reminders (Workspace) Output Templates.

• WS_Remind_Rec: The selected reminder:
  • Note.
  • Reminder.
  • Due times.
  • Status.
  • User.
  • Module.
  • Workflow number.
  • References.
  • The customer.
  • Supplier or staff member it is for.
• WS_Remind_All: All the reminders on the Workspace:
  • Note.
  • Reminder.
  • Due times.
  • Status.
  • User.
  • Module.
  • Who each is for.

Signatures#

The following Data Pipelines can be used on Signatures Output Templates.

• Trans_SignDocs: All the signed documents on the transaction:
  • Document.
  • Transaction number.
  • Location.
  • Who signed.
  • When.

Custom Reports#

The following Data Pipelines can be used on Custom Reports Output Templates.

• Rep_All: All the rows the custom report returns.
• Rep_Rec: The selected row of the custom report.
• Rep_Filters: The custom report's filter selections.

All Outputs#

The following Data Pipelines can be used on All Outputs Output Templates.

• Active_User: The logged-in user's staff details:
  • Name.
  • Position.
  • Contact details.
  • Addresses.
  • Cost Centre rate.
  • Business entity.