Difference between revisions of "Glossary"

From SVContheGO Online Manual
Jump to navigation Jump to search
m
m
 
(47 intermediate revisions by the same user not shown)
Line 1: Line 1:
  
 
{| border="0" cellpadding="1" cellspacing="1" style="width: 1538px;"
 
{| border="0" cellpadding="1" cellspacing="1" style="width: 1538px;"
 +
|-
 +
| colspan="1" id="Top" style="width: 1538px;" | <div class="fieldHeader">Glossary</div>
 
|-
 
|-
 
| <div id="job_acctmanager">&nbsp;</div>  
 
| <div id="job_acctmanager">&nbsp;</div>  
Line 7: Line 9:
 
|-
 
|-
 
|  
 
|  
     Account managers are responsible for the customer relationship.
+
     Account managers are responsible for the customer relationship. Account managers are assigned to customers and(or) jobs.
  
 
|-
 
|-
Line 16: Line 18:
 
|  
 
|  
 
     Indicates that the record can be used to produce results.
 
     Indicates that the record can be used to produce results.
 +
 +
|-
 +
| <div id="AgreementAnnvDate">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Anniversary Date</div>
 +
|-
 +
|
 +
    The date the agreement terms will end.
  
 
|-
 
|-
Line 23: Line 33:
 
|-
 
|-
 
|  
 
|  
     Indicates the amount percent of increase for the renewal.
+
     Indicates the amount percent of increase for the agreement renewal.
 +
 
 +
|-
 +
| <div id="AgreementBalance">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Balance</div>
 +
|-
 +
|
 +
    The current balance of the contract.
  
 
|-
 
|-
Line 31: Line 49:
 
|-
 
|-
 
|  
 
|  
     When checked, indicates that the agreement can be billed.
+
     When checked, indicates that the agreement will be included in the billing process.
  
 
|-
 
|-
Line 39: Line 57:
 
|-
 
|-
 
|  
 
|  
     The total contract amount.
+
     The total contract amount for the agreement.
  
 
|-
 
|-
Line 55: Line 73:
 
|-
 
|-
 
|  
 
|  
     The customer or site contact that handles the agreement.
+
     The person that should be contacted concerning the agreement.
  
 
|-
 
|-
| <div id="AgreementDefRevenuesTotal">&nbsp;</div>  
+
| <div id="AgreementMonths">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Deferred Revenues Total</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Contact Months</div>  
 
|-
 
|-
 
|  
 
|  
     The total deferred revenues posted to date.
+
     The number of months covered by the agreement.
  
 
|-
 
|-
| <div id="AgreementFrequency">&nbsp;</div>  
+
| <div id="AgreementCoverLabor">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Frequency</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Cover Labor</div>  
 
|-
 
|-
 
|  
 
|  
     The billing frequency.
+
     Indicates if the agreement covers labor transactions.
  
 
|-
 
|-
| <div id="AgreementGrossProfitContactBilledtoDate">&nbsp;</div>  
+
| <div id="AgreementCoverParts">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Gross Profit Contact Billed to Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Cover Parts</div>  
 
|-
 
|-
 
|  
 
|  
     The agreement's gross profit based on billings to date.
+
     Indicates if the agreement covers parts transactions.
 +
 
 +
&nbsp;
  
 
|-
 
|-
| <div id="AgreementGrossProfitContractTermtoDate">&nbsp;</div>  
+
| <div id="AgreementCurrentContractAmount">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Gross Profit Contract Term to Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Current Contract Amount</div>  
 
|-
 
|-
 
|  
 
|  
     The agreement's gross profit recorded on the contract to date.  
+
     The amount of the contract at the time of creation.
  
 
|-
 
|-
| <div id="AgreementLaborBudgetBalance">&nbsp;</div>  
+
| <div id="AgreementDefRevBalance">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Budget Balance&nbsp;%</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Deferred Revenue Balance</div>  
 
|-
 
|-
 
|  
 
|  
     Percentage of labor budget balance to date.  
+
     The current balance of deferred revenues for the contract.
  
 
|-
 
|-
| <div id="AgreementLaborBudgetUsed">&nbsp;</div>  
+
| <div id="AgreementDefRevenuesTotal">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Budget Used&nbsp;%</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Deferred Revenues Total</div>  
 
|-
 
|-
 
|  
 
|  
     Percentage of labor budget used to date.
+
     The total deferred revenues posted to date.
  
 
|-
 
|-
| <div id="AgreementLaborBudgetHoursUsedtoDate">&nbsp;</div>  
+
| <div id="AgreementEstDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Budget Hours Used to Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Established Date</div>  
 
|-
 
|-
 
|  
 
|  
     The number of budgeted hours billed to date.
+
     The date the agreement was first established
  
 
|-
 
|-
| <div id="AgreementHoursBalance">&nbsp;</div>  
+
| <div id="AgreementFreeMonths">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Hours Balance</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Free Months</div>  
 
|-
 
|-
 
|  
 
|  
     The remainder of the budgeted hours to date.
+
     The number of months the customer is being provide for free.
  
 
|-
 
|-
| <div id="AgreementLaborHoursBudget">&nbsp;</div>  
+
| <div id="AgreementFrequency">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Hours Budget</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Frequency</div>  
 
|-
 
|-
 
|  
 
|  
     The number of labor hours budgeted for the contract's term.  
+
     The billing frequency. i.e., Annually, Monthly
  
 
|-
 
|-
| <div id="AgreementLastIncrease">&nbsp;</div>  
+
| <div id="AgreementGrossProfitContactBilledtoDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Last Increase</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Gross Profit Contact Billed to Date</div>  
 
|-
 
|-
 
|  
 
|  
     The increase amount from the last renewal.
+
     The agreement's gross profit based on billings to date.
  
 
|-
 
|-
| <div id="agreements_Number">&nbsp;</div>  
+
| <div id="AgreementGrossProfitContractTermtoDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Gross Profit Contract Term to Date</div>  
 
|-
 
|-
 
|  
 
|  
     Agreement numbers are used the identify agreements.
+
     The agreement's gross profit recorded on the contract to date.  
  
 
|-
 
|-
| <div id="AgreementPartsBilledtoDate">&nbsp;</div>  
+
| <div id="AgreementLaborBudgetBalance">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Billed to Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Budget Balance&nbsp;%</div>  
 
|-
 
|-
 
|  
 
|  
     The amount billed to date for parts.
+
     Percentage of labor budget balance to date.  
  
 
|-
 
|-
| <div id="AgreementPartsBudget">&nbsp;</div>  
+
| <div id="AgreementLaborBudgetUsed">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Budget Used&nbsp;%</div>  
 
|-
 
|-
 
|  
 
|  
     The total amount budgeted for parts on the agreement contract.
+
     Percentage of labor budget used to date.
  
 
|-
 
|-
| <div id="AgreementPartsBudgetBalance">&nbsp;</div>  
+
| <div id="AgreementLaborBudgetHoursUsedtoDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget Balance</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Budget Hours Used to Date</div>  
 
|-
 
|-
 
|  
 
|  
     The remainer of the amount budgeted for parts to date.
+
     The number of budgeted hours billed to date.
  
 
|-
 
|-
| <div id="AgreementPartsBudgetBalance.25">&nbsp;</div>  
+
| <div id="AgreementHoursBalance">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget Balance&nbsp;%</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Hours Balance</div>  
 
|-
 
|-
 
|  
 
|  
     Percentage of parts budget balance to date.  
+
     The remainder of the budgeted hours to date.
  
 
|-
 
|-
| <div id="AgreementPartsBudgetUsed">&nbsp;</div>  
+
| <div id="AgreementLaborHoursBudget">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget Used&nbsp;%</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Labor Hours Budget</div>  
 
|-
 
|-
 
|  
 
|  
     The amount of the parts budget billed to date.
+
     The number of labor hours budgeted for the contract's term.  
  
 
|-
 
|-
| <div id="AgreementPriceLevel">&nbsp;</div>  
+
| <div id="AgreementLastIncrease">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Price Level</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Last Increase</div>  
 
|-
 
|-
 
|  
 
|  
     The price level that will be used when billing the agreement.
+
     The increase amount from the last renewal.
  
 
|-
 
|-
| <div id="agreements_PricingMethod">&nbsp;</div>  
+
| <div id="agreements_Number">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Pricing Method</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Number</div>  
 
|-
 
|-
 
|  
 
|  
     Agreements can be priced based on the different methods. 
+
     Agreement numbers are used to identify agreements. On the Job forms it indicates the agreement that may be used to cover transactions. On the PM Schedule form it indicates the agreement that is attached to the schedule.
        Blanket: One price covers all items on the agreement
 
        By Site: Each site can have a different price.
 
        By Equipment: Each equipment record can have a different price.  
 
  
 
|-
 
|-
| <div id="AgreementPurchaseOrder">&nbsp;</div>  
+
| <div id="AgreementOriginalContractAmount">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Purchase Order</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Original Contract Amount</div>  
 
|-
 
|-
 
|  
 
|  
     The purchase order provided by the customer for the agreement.
+
     The total price for the contract when started.
  
 
|-
 
|-
| <div id="AgreementRenewable">&nbsp;</div>  
+
| <div id="AgreementPartsBilledtoDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewable</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Billed to Date</div>  
 
|-
 
|-
 
|  
 
|  
     Indicates that the agreement is eligible for renewal.
+
     The amount billed to date for parts.
  
 
|-
 
|-
| <div id="AgreementRenewalAmount">&nbsp;</div>  
+
| <div id="AgreementPartsBudget">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Amount</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget</div>  
 
|-
 
|-
 
|  
 
|  
     The amount that will be billed on agreement renewal.
+
     The total amount budgeted for parts on the agreement contract.
  
 
|-
 
|-
| <div id="AgreementRenewalMethod">&nbsp;</div>  
+
| <div id="AgreementPartsBudgetBalance">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Method</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget Balance</div>  
 
|-
 
|-
 
|  
 
|  
     The renewal method field is used when determining the renewal contract amount.  The contract amount can be a fixed amount, or changed based on a change percentage.
+
     The remainder of the amount budgeted for parts to date after invoicing.
        Fixed Amount: The renewal will use the exact amount in this field.
 
        Change Percent: Increases the contract amount by the percent in the Renewal Amount field.
 
  
 
|-
 
|-
| <div id="AgreementRenewalMonths">&nbsp;</div>  
+
| <div id="AgreementPartsBudgetBalance.25">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Months</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget Balance&nbsp;%</div>  
 
|-
 
|-
 
|  
 
|  
     The contract months to use on the renewal.
+
     Percentage of parts budget balance to date.  
  
 
|-
 
|-
| <div id="AgreementRenewalText">&nbsp;</div>  
+
| <div id="AgreementPartsBudgetUsed">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Text</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Parts Budget Used&nbsp;%</div>  
 
|-
 
|-
 
|  
 
|  
     The text that will be displayed on the agreement renewal invoice.  
+
     The amount of the parts budget billed to date.
  
 
|-
 
|-
| <div id="AgreementRenewAs">&nbsp;</div>  
+
| <div id="AgreementPriceLevel">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renew As</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Price Level</div>  
 
|-
 
|-
 
|  
 
|  
     Used to indicate the type of invoice that will be created upon renewal.
+
     The price level that will be used when billing the agreement.
  
 
|-
 
|-
| <div id="AgreementRevenuesTotal">&nbsp;</div>  
+
| <div id="agreements_PricingMethod">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Revenues Total</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Pricing Method</div>  
 
|-
 
|-
 
|  
 
|  
     The total amount billed for the contract to date.
+
     Agreements can be priced based on the different methods. 
 +
        Blanket: One price covers all sites and equipment on the agreement. 
 +
        By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price.
 +
        By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price.  
  
 
|-
 
|-
| <div id="AgreementSalesperson">&nbsp;</div>  
+
| <div id="AgreementPriority">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Salesperson</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Priority</div>  
 
|-
 
|-
 
|  
 
|  
     The salesperson that should be assigned to the invoices when billing occurs.
+
     The priority code that would be used for jobs created for agreement coverage.
  
 
|-
 
|-
| <div id="AgreementStatusCode">&nbsp;</div>  
+
| <div id="AgreementPurchaseOrder">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Status Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Purchase Order</div>  
 
|-
 
|-
 
|  
 
|  
     The status code is used to track the agreements progress through the renewal process.
+
     The purchase order provided by the customer for the agreement.
  
 
|-
 
|-
| <div id="AgreementType">&nbsp;</div>  
+
| <div id="AgreementRenewable">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewable</div>  
 
|-
 
|-
 
|  
 
|  
     Used to organize agreements by type. Agreement types are also used to establish setting for agreements by default.  
+
     Indicates that the agreement is eligible for renewal. Eligible agreements will be included in the renewal process.
  
 
|-
 
|-
| <div id="agreeType_Code">&nbsp;</div>  
+
| <div id="AgreementRenewalAmount">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Amount</div>  
 
|-
 
|-
 
|  
 
|  
     The code used to identify the agreement type.
+
     The amount that will be billed on agreement renewal.
  
 
|-
 
|-
| <div id="agreeType_Desc">&nbsp;</div>  
+
| <div id="AgreementRenewalMethod">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Method</div>  
 
|-
 
|-
 
|  
 
|  
     The description used to identify the agreement type.
+
     The renewal method field is used when determining the renewal contract amount. The contract amount can be a fixed amount or changed based on a change percentage.
 +
        Fixed Amount: The renewal will use the exact amount in this field.
 +
        Change Percent: Increases the contract amount by the percent in the Renewal Amount field.
  
 
|-
 
|-
| <div id="agreeType_coveredMths">&nbsp;</div>  
+
| <div id="AgreementRenewalMonths">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Contract Months</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Months</div>  
 
|-
 
|-
 
|  
 
|  
     The number of months for new agreements.
+
     The contract months to use on the agreement's renewal.
  
 
|-
 
|-
| <div id="agreeType_coverparts">&nbsp;</div>  
+
| <div id="AgreementRenewalText">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Cover Parts Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renewal Text</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the parts covered by the agreement will have no charge.
+
     The text that will be displayed on the agreement renewal invoice.  
  
 
|-
 
|-
| <div id="agreeType_coverLabor">&nbsp;</div>  
+
| <div id="AgreementRenewAs">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Cover Labor Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Renew As</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the parts covered by the agreement will have no charge.
+
     Used to indicate the type of invoice that will be created upon renewal.
  
 
|-
 
|-
| <div id="agreeType_SLA">&nbsp;</div>  
+
| <div id="AgreementRevenuesTotal">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: SLA Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Revenues Total</div>  
 
|-
 
|-
 
|  
 
|  
     Check this box, if the agreement qualifies for SLA service.  
+
     The total amount billed for the contract to date.
  
 
|-
 
|-
| <div id="agreeType_SLAPC">&nbsp;</div>  
+
| <div id="AgreementSalesperson">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: SLA Priority Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Salesperson</div>  
 
|-
 
|-
 
|  
 
|  
     The SLA qualified priority code to use for new agreements.
+
     The salesperson that should be assigned to the invoices when billing occurs.
  
 
|-
 
|-
| <div id="agreeType_Message">&nbsp;</div>  
+
| <div id="AgreementSLA">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Message</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: SLA</div>  
 
|-
 
|-
 
|  
 
|  
     This message will appear on the agreement.
+
     Indicates that the jobs created for this agreement are covered by SLA priority.
  
 
|-
 
|-
| <div id="agreeType_LaborHoursBudget">&nbsp;</div>  
+
| <div id="AgreementStartDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Labor Hours Budget</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Start Date</div>  
 
|-
 
|-
 
|  
 
|  
     The budgeted number of labor hours.
+
     The date the agreement terms will begin.
  
 
|-
 
|-
| <div id="agreeType_PartsDollarsBudget">&nbsp;</div>  
+
| <div id="AgreementStatusCode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Parts Dollars Budget</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement: Status Code</div>  
 
|-
 
|-
 
|  
 
|  
     The budgeted parts dollars.
+
     The status code is used to track the agreements progress through the renewal process.
  
 
|-
 
|-
| <div id="agreeType_PercentUsed">&nbsp;</div>  
+
| <div id="AgreementType">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Percent Used >=</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type</div>  
 
|-
 
|-
 
|  
 
|  
     Percentage of labor budget used.
+
     Used to organize agreements by type. Agreement types are also used to establish settings for agreements by default.  
  
 
|-
 
|-
| <div id="agreeType_DollarsUsed">&nbsp;</div>  
+
| <div id="agreeType_Code">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Dollars Used >=</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Code</div>  
 
|-
 
|-
 
|  
 
|  
     Percentage of parts dollars used.
+
     The agreement type code code is used to identify the agreement type.
  
 
|-
 
|-
| <div id="agreeTypePIO_Billable">&nbsp;</div>  
+
| <div id="agreeType_Desc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Auto Number by Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Description</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, new agreements will auto-number using the value int he Next Number field.
+
     The description used to identify the agreement type.
  
 
|-
 
|-
| <div id="agreeTypePIO_Frequency">&nbsp;</div>  
+
| <div id="agreeType_coveredMths">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Next Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Contract Months</div>  
 
|-
 
|-
 
|  
 
|  
     Used when auto-numbering agreements.  
+
     The number of months for new agreements.
  
 
|-
 
|-
| <div id="agreeTypePIO_TaxClass">&nbsp;</div>  
+
| <div id="agreeType_coverparts">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Enforce Defaults</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Cover Parts Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the agreement type defaults cannot be changed on the agreement.
+
     When checked, the parts covered by the agreement will have no charge.
  
 
|-
 
|-
| <div id="agreeTypePIO_Billable">&nbsp;</div>  
+
| <div id="agreeType_coverLabor">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Billable</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Cover Labor Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the agreements assigned to the agreement type will be billable by default.
+
     When checked, the parts covered by the agreement will have no charge.
  
 
|-
 
|-
| <div id="agreeTypePIO_Frequency">&nbsp;</div>  
+
| <div id="agreeType_SLA">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Frequency</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: SLA Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The billing frequency.
+
     Check this box if the agreement qualifies for SLA service.  
  
 
|-
 
|-
| <div id="agreeTypePIO_TaxClass">&nbsp;</div>  
+
| <div id="agreeType_SLAPC">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Tax Class</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: SLA Priority Code</div>  
 
|-
 
|-
 
|  
 
|  
     The tax class assigned to invoice billing invoices.
+
     The SLA qualified priority code to use for new agreements.
  
 
|-
 
|-
| <div id="agreeTypePIO_Allocation">&nbsp;</div>  
+
| <div id="agreeType_Message">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Allocation</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Message</div>  
 
|-
 
|-
 
|  
 
|  
     The allocation that will be assigned used when processing agreements.
+
     This message will appear on the agreement.
  
 
|-
 
|-
| <div id="agreeTypePIO_DefRev">&nbsp;</div>  
+
| <div id="agreeType_LaborHoursBudget">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Deferred Revenues</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Labor Hours Budget</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, new agreements will use the deferred revenue feature.
+
     The budgeted number of labor hours.
  
 
|-
 
|-
| <div id="agreeTypePIO_PricingMethod">&nbsp;</div>  
+
| <div id="agreeType_PartsDollarsBudget">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Pricing Method</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Parts Dollars Budget</div>  
 
|-
 
|-
 
|  
 
|  
     The pricing method used when processing agreement transactions.
+
     The budgeted parts dollars.
        Blanket: One price covers all items on the agreement. 
 
        By Site: Each site can have a different price.
 
        By Equipment: Each equipment record can have a different price.  
 
  
 
|-
 
|-
| <div id="agreeTypePIO_IncludeSiteDetailsonInvoice">&nbsp;</div>  
+
| <div id="agreeType_PercentUsed">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Site Details on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Percent Used >=</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the site details will appear on agreement invoices.
+
     Percentage of labor budget used.
  
 
|-
 
|-
| <div id="agreeTypePIO_IncludeEquipDetailsonInvoice">&nbsp;</div>  
+
| <div id="agreeType_DollarsUsed">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Equipment Details on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Dollars Used >=</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, equipment details will appear on agreement invoices.
+
     Percentage of parts dollars used.
  
 
|-
 
|-
| <div id="agreeTypePIO_IncludeSiteSummaryonInvoice">&nbsp;</div>  
+
| <div id="agreeTypePIO_Billable">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Site Summary on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Auto Number by Type</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, a site summary will appear on agreement invoices.
+
     When checked, new agreements will auto-number using the value in the Next Number field based on the Agreement Type.
  
 
|-
 
|-
| <div id="agreeTypePIO_IncludeSiteSummaryonInvoice">&nbsp;</div>  
+
| <div id="agreeTypePIO_Frequency">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Equipment Summary on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Next Number</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, an equipment summary will appear on agreement invoices.
+
     Used when auto-numbering agreements.  
  
 
|-
 
|-
| <div id="agreeTypePRO_IncludeSiteDetailsonInvoice">&nbsp;</div>  
+
| <div id="agreeTypePIO_TaxClass">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renewable Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type: Enforce Defaults</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the agreement will be marked renewable on creation.
+
     When checked, the agreement type defaults cannot be changed on the agreement.
  
 
|-
 
|-
| <div id="agreeTypePRO_Months">&nbsp;</div>  
+
| <div id="agreeTypePIO_Billable">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renewal Months</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Billable</div>  
 
|-
 
|-
 
|  
 
|  
     The number of default renewal months on new agreements.
+
     When checked, the agreements assigned to the agreement type will be billable by default.
  
 
|-
 
|-
| <div id="agreeTypePRO_AS">&nbsp;</div>  
+
| <div id="agreeTypePIO_Frequency">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renew As</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Frequency</div>  
 
|-
 
|-
 
|  
 
|  
     The default renew as value for new agreements.
+
     The billing frequency. i.e., Annually, Monthly
  
 
|-
 
|-
| <div id="agreeTypePRO_Include_Site_Details_on_Renewal_Details">&nbsp;</div>  
+
| <div id="agreeTypePIO_TaxClass">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Site Details on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Tax Class</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the site details will appear on renewal invoices.
+
     The tax class that should be assigned to the invoice when the agreement is billed.
  
 
|-
 
|-
| <div id="agreeTypePRO_Include_Equip_Details_on_Renewal_Details">&nbsp;</div>  
+
| <div id="agreeTypePIO_Allocation">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Equipment Details on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Allocation</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, equipment details will appear on renewal invoices.
+
     The allocation that will be assigned when processing agreements. Allocations are used to establish the general ledger posting accounts and amounts.
  
 
|-
 
|-
| <div id="agreeTypePRO_Include_Site_Summary_on_Renewal_Details">&nbsp;</div>  
+
| <div id="agreeTypePIO_DefRev">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Site Summary on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Deferred Revenues</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, a site summary will appear on renewal invoices.
+
     When checked, new agreements will use the deferred revenue feature during the billing process.
  
 
|-
 
|-
| <div id="agreeTypePRO_Include_Equip_Summary_on_Renewal_Details">&nbsp;</div>  
+
| <div id="agreeTypePIO_PricingMethod">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Equipment Summary on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Pricing Method</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, an equipment summary will appear on renewal invoices.
+
     The pricing method used when processing agreement transactions.
 +
        Blanket: One price covers all sites and equipment on the agreement. 
 +
        By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price.
 +
        By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price.  
  
 
|-
 
|-
| <div id="agreeTypePRO_Include_Equip_Details_on_Renewal_Details">&nbsp;</div>  
+
| <div id="agreeTypePIO_IncludeSiteDetailsonInvoice">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Create a Job for each Equipment</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Site Details on Invoice</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, planned maintenance will create a separate job for each equipment record assigned to the schedule.
+
     When checked, the site details will appear on agreement invoices.
  
 
|-
 
|-
| <div id="agreeTypePRO_Include_Site_Summary_on_Renewal_Details">&nbsp;</div>  
+
| <div id="agreeTypePIO_IncludeEquipDetailsonInvoice">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Create Transactions</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Equipment Details on Invoice</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, planned maintenance will automatically add the transactions to the generated jobs.
+
     When checked, equipment details will appear on agreement invoices.
  
 
|-
 
|-
| <div id="agreeTypePRO_Include_Equip_Summary_on_Renewal_Details">&nbsp;</div>  
+
| <div id="agreeTypePIO_IncludeSiteSummaryonInvoice">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Price Transactions</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Site Summary on Invoice</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, planned maintenance will add the transactions, with pricing, to the generated jobs.
+
     When checked, a site summary will appear on agreement invoices.
  
 
|-
 
|-
| <div id="Allocation">&nbsp;</div>  
+
| <div id="agreeTypePIO_IncludeSiteSummaryonInvoice">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Invoice Options: Include Equipment Summary on Invoice</div>  
 
|-
 
|-
 
|  
 
|  
     Allocations are used to distribute the agreement dollars to the required general ledger accounts.
+
     When checked, an equipment summary will appear on agreement invoices.
  
 
|-
 
|-
| <div id="alloc_Desc">&nbsp;</div>  
+
| <div id="agreeTypePRO_IncludeSiteDetailsonInvoice">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renewable Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The description used to identify the allocation.
+
     When checked, the agreement will be marked renewable on creation.
  
 
|-
 
|-
| <div id="alloc_revType">&nbsp;</div>  
+
| <div id="agreeTypePRO_Months">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Revenue Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renewal Months</div>  
 
|-
 
|-
 
|  
 
|  
     Indicates if the allocation will be a percentage or fixed amount.
+
     The number of default renewal months on new agreements.
  
 
|-
 
|-
| <div id="alloc_pricingMethod">&nbsp;</div>  
+
| <div id="agreeTypePRO_AS">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Pricing Method</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Renew As</div>  
 
|-
 
|-
 
|  
 
|  
     Agreements can be priced based on the different methods. Allocations define the price method the can be assigned in agreement types.
+
     The default renew as value for new agreements.   
        Blanket: One price covers all items on the agreement.   
 
        By Site: Each site can have a different price.
 
        By Equipment: Each equipment record can have a different price.
 
  
 
|-
 
|-
| <div id="alloc_price">&nbsp;</div>  
+
| <div id="agreeTypePRO_Include_Site_Details_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Price</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Site Details on Invoice</div>  
 
|-
 
|-
 
|  
 
|  
     The allocation price. 
+
     When checked, the site details will appear on renewal invoices.
        Blanket - Enter one price for the entire contract.
 
        By Site - Enter the price for each site.
 
        By Equipment - Enter ethe price for each equipment.  
 
  
 
|-
 
|-
| <div id="alloc_Type">&nbsp;</div>  
+
| <div id="agreeTypePRO_Include_Equip_Details_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Equipment Details on Invoice</div>  
 
|-
 
|-
 
|  
 
|  
     The type of general ledger entry.
+
     When checked, equipment details will appear on renewal invoices.
        Deferred Revenue: Posts to a deferred revenue account.
 
        Revenue: Post to a sales revenue account.
 
  
 
|-
 
|-
| <div id="alloc_miscItem">&nbsp;</div>  
+
| <div id="agreeTypePRO_Include_Site_Summary_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Miscellaneous Item</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Site Summary on Invoice</div>  
 
|-
 
|-
 
|  
 
|  
     The miscellaneous item to use when posting to the ERP system.
+
     When checked, a site summary will appear on renewal invoices.
  
 
|-
 
|-
| <div id="alloc_Account">&nbsp;</div>  
+
| <div id="agreeTypePRO_Include_Equip_Summary_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Allocations Account</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Renewal Options: Include Equipment Summary on Invoice</div>  
 
|-
 
|-
 
|  
 
|  
     The account that should be affected by the allocation transaction.
+
     When checked, an equipment summary will appear on renewal invoices.
  
 
|-
 
|-
| <div id="alloc_Amount">&nbsp;</div>  
+
| <div id="agreeTypePRO_Include_Equip_Details_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Amount</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Create a Job for each Equipment</div>  
 
|-
 
|-
 
|  
 
|  
     The amount of the allocation transaction.
+
     When checked, planned maintenance will create a separate job for each equipment record assigned to the schedule.
  
 
|-
 
|-
| <div id="servicetype_AssignedBtn">&nbsp;</div>  
+
| <div id="agreeTypePRO_Include_Site_Summary_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Assigned</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Create Transactions</div>  
 
|-
 
|-
 
|  
 
|  
     When clicked, displays all items assigned to the selected record.
+
     When checked, planned maintenance will automatically add the transactions to the generated jobs.
  
 
|-
 
|-
| <div id="servicetype_NotAssingedBtn">&nbsp;</div>  
+
| <div id="agreeTypePRO_Include_Equip_Summary_on_Renewal_Details">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Not Assigned</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Agreement Type Planned Maintenance Options: Price Transactions</div>  
 
|-
 
|-
 
|  
 
|  
     When clicked, displays all the records not assigned to the selected item.
+
     When checked, planned maintenance will add the transactions, with pricing, to the generated jobs.
  
 
|-
 
|-
| <div id="chain_Name">&nbsp;</div>  
+
| <div id="Allocation">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation</div>  
 
|-
 
|-
 
|  
 
|  
     Sites can grouped by chain.
+
     Allocations are used to distribute the agreement dollars to the required general ledger accounts.
  
 
|-
 
|-
| <div id="chain_Name">&nbsp;</div>  
+
| <div id="alloc_Desc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Description</div>  
 
|-
 
|-
 
|  
 
|  
     The name used to identify the chain.
+
     The description used to identify the allocation.
  
 
|-
 
|-
| <div id="chain_SLA">&nbsp;</div>  
+
| <div id="alloc_revType">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: SLA</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Revenue Type</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, indicates the chain is an SLA chain. SLA chains have a expiration time for when the work is expected to be completed.
+
     Indicates if the allocation will be a percentage or fixed amount.
  
 
|-
 
|-
| <div id="chain_Inbound">&nbsp;</div>  
+
| <div id="alloc_pricingMethod">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Inbound Path</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Pricing Method</div>  
 
|-
 
|-
| The inbound path.
+
|  
|-
+
    Agreements can be priced based on the different methods. Allocations define the price method the can be assigned in agreement types.
| <div id="chain_Outbound">&nbsp;</div>
+
        Blanket: One price covers all sites and equipment on the agreement. 
 +
        By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price.  
 +
        By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Outbound Path</div>  
+
| <div id="alloc_price">&nbsp;</div>  
 
|-
 
|-
| The outbound path.
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation: Price</div>
 
|-
 
|-
| <div id="chain_storeTypeCode">&nbsp;</div>
+
|  
 +
    The allocation price. 
 +
        Blanket: One price covers all sites and equipment on the agreement.  Enter the price that will cover the entire contract.
 +
        By Site: The contract amount is a total of all site prices on the agreement. Enter the default price for a site.
 +
        By Equipment: The contract amount is a total of all equipment prices on the agreement. Enter the default price for an equipment item.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Store Type Code</div>  
+
| <div id="alloc_Type">&nbsp;</div>  
 
|-
 
|-
| Stores can be organized by type.
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Type</div>
 
|-
 
|-
| <div id="chain_storeTypeName">&nbsp;</div>
+
|  
 +
    The type of general ledger entry.
 +
        Deferred Revenue: Posts to a deferred revenue account.
 +
        Revenue: Post to a sales revenue account.
 +
 
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Store Type Name</div>  
+
| <div id="alloc_miscItem">&nbsp;</div>  
 
|-
 
|-
| The name used to identify the store type.
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Miscellaneous Item</div>  
|-
 
| <div id="Classification">&nbsp;</div>
 
|-
 
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Classification</div>  
 
 
|-
 
|-
 
|  
 
|  
     The classification is used in sales and cost account assignments. Classifications are assigned to Cost Types and Items.
+
     The miscellaneous item to use when posting to the ERP system.
  
 
|-
 
|-
| <div id="servicetype_RemoveallAssnBtn">&nbsp;</div>  
+
| <div id="alloc_Account">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Remove all Assignments</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Allocations Account</div>  
 
|-
 
|-
 
|  
 
|  
     When clicked, removes all assignments from the selected record.
+
     The account that should be affected by the allocation transaction.
  
 
|-
 
|-
| <div id="corep_commrate">&nbsp;</div>  
+
| <div id="alloc_Amount">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Commission Rate</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Allocation Details: Amount</div>  
 
|-
 
|-
 
|  
 
|  
     The amount of commission that is earned when an item is sold.  
+
     The amount of the allocation transaction.
  
 
|-
 
|-
| <div id="contact_address">&nbsp;</div>  
+
| <div id="boTransEntry_WO">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Address</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Work Order</div>  
 
|-
 
|-
 
|  
 
|  
     The contacts mailing address.
+
     The transaction will be assigned to the selected work order.  
  
 
|-
 
|-
| <div id="contact_City">&nbsp;</div>  
+
| <div id="boTransEntry_Stock">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: City</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Stock Radio Button</div>  
 
|-
 
|-
 
|  
 
|  
     The city of the mailing address.
+
     Toggles the Inventory search to include only material items.
  
 
|-
 
|-
| <div id="contact_country">&nbsp;</div>  
+
| <div id="boTransEntry_Nonstock">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Country</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Non-stock Radio Button</div>  
 
|-
 
|-
 
|  
 
|  
     The country of the mailing address.
+
     Toggles the Inventory search to include only non-inventory material items.
  
 
|-
 
|-
| <div id="contact_email">&nbsp;</div>  
+
| <div id="boTransEntry_FindCode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Email</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Find by Item Code</div>  
 
|-
 
|-
 
|  
 
|  
     The contact's email address.
+
     Used to search for an item by the item's code.
  
 
|-
 
|-
| <div id="contact_estDate">&nbsp;</div>  
+
| <div id="boTransEntry_FindDesc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Established Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Find by Item Description</div>  
 
|-
 
|-
 
|  
 
|  
     The date the contact record was established.
+
     Used to search for an item by item's description.
  
 
|-
 
|-
| <div id="contact_fax">&nbsp;</div>  
+
| <div id="boTransEntry_Servicer">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Fax Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Servicer</div>  
 
|-
 
|-
 
|  
 
|  
     The contact's fax number.
+
     The servicer that will be assigned to the transaction. This field controls the warehouse list.
  
 
|-
 
|-
| <div id="contact_firstName">&nbsp;</div>  
+
| <div id="boTransEntry_Agreement">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: First Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Agreement</div>  
 
|-
 
|-
 
|  
 
|  
     The contact's first name.  
+
     The agreement assigned to the selected work order.
  
 
|-
 
|-
| <div id="contact_lastName">&nbsp;</div>  
+
| <div id="boTransEntry_Warehouse">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Last Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Warehouse</div>  
 
|-
 
|-
 
|  
 
|  
     The contact's last name.
+
     The warehouse from where the item will be allocated.
  
 
|-
 
|-
| <div id="contact_ContactName">&nbsp;</div>  
+
| <div id="boTransEntry_CT">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Cost Type</div>  
 
|-
 
|-
 
|  
 
|  
     The contacts full name.
+
     Used to assign general ledger account allocations.
  
 
|-
 
|-
| <div id="contact_WorkPhone">&nbsp;</div>  
+
| <div id="boTransEntry_EQ">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Phone</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Equipment</div>  
 
|-
 
|-
 
|  
 
|  
     The contact's telephone number.
+
     The equipment assigned to the selected work order.
  
 
|-
 
|-
| <div id="contact_Salutation">&nbsp;</div>  
+
| <div id="boTransEntry_Covered">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Salutation</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Covered</div>  
 
|-
 
|-
 
|  
 
|  
     The salutation that should be used when communicating with the contact.
+
     Indicates whether or not the transaction should be covered by either warranty or agreement. The software will determine the coverage based on the availably of coverage based on warranty and agreement settings.  If coverage exists, the price will change to 0.
  
 
|-
 
|-
| <div id="contact_state">&nbsp;</div>  
+
| <div id="boTransEntry_ItemCode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: State</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Item Code</div>  
 
|-
 
|-
 
|  
 
|  
     The state of the mailing address.
+
     The item code that will be used to identify the item.  
  
 
|-
 
|-
| <div id="contact_Title">&nbsp;</div>  
+
| <div id="boTransEntry_TransDesc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Title</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Trans Description</div>  
 
|-
 
|-
 
|  
 
|  
     The contact title. ex: Mr., Mrs.
+
     The transaction description that will appear on the invoice. This can be different from the item description.
  
 
|-
 
|-
| <div id="contact_Type">&nbsp;</div>  
+
| <div id="boTransEntry_VendorList">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Vendor List</div>  
 
|-
 
|-
 
|  
 
|  
     Types can be used to organize contacts.
+
     Used to attach a vendor to the transaction.  Purchase transactions only.
  
 
|-
 
|-
| <div id="contact_zip">&nbsp;</div>  
+
| <div id="boTransEntry_StartDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Zip</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Start Date</div>  
 
|-
 
|-
 
|  
 
|  
     The postal code of the mailing address.
+
     The date the labor transaction started.  Labor transactions only.
  
 
|-
 
|-
| <div id="CostType">&nbsp;</div>  
+
| <div id="boTransEntry_TransDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Trans Date</div>  
 
|-
 
|-
 
|  
 
|  
     Cost types are used to manage general ledger sales and cost account allocations on transactions and billing.
+
     The transaction date.  Inventory and Purchase transactions only.
  
 
|-
 
|-
| <div id="costtype_CostAcct">&nbsp;</div>  
+
| <div id="boTransEntry_StartTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Cost Account</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Start Time</div>  
 
|-
 
|-
 
|  
 
|  
     The cost account that will be assigned to transactions assigned this job type and cost type.  
+
     The time the labor transaction started.  Labor transactions only.
  
 
|-
 
|-
| <div id="costtype_CostSubacct">&nbsp;</div>  
+
| <div id="boTransEntry_EndDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Cost Subaccount</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: End Date</div>  
 
|-
 
|-
 
|  
 
|  
     The cost sub-account that will be assigned to transactions assigned this job type and cost type.  
+
     The date the labor transaction ended.  Labor transactions only. This field is only available for use when multiple day transactions is on.
  
 
|-
 
|-
| <div id="costtype_Desc">&nbsp;</div>  
+
| <div id="boTransEntry_EndTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: End Time</div>  
 
|-
 
|-
 
|  
 
|  
     Used to describe the cost type.  
+
     The time the labor transaction ended.  Labor transactions only.  
  
 
|-
 
|-
| <div id="costtype_InventoryCB">&nbsp;</div>  
+
| <div id="boTransEntry_NoUnits">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Inventory Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: No Units</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, indicates that the cost type can be used for inventory transactions.  
+
     The number of units sold.
  
 
|-
 
|-
| <div id="costtype_LaborCB">&nbsp;</div>  
+
| <div id="boTransEntry_Taxable">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Labor Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Taxable</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, indicates that the cost type can be used for labor transactions.  
+
     Checked when the transaction is taxable.
  
 
|-
 
|-
| <div id="costtype_PurchasesCB">&nbsp;</div>  
+
| <div id="boTransEntry_Price">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Purchases Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Price</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, indicates that the cost type can be used for purchase transactions.  
+
     The price of the item.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customeraccountmanager">&nbsp;</div>  
+
| <div id="boTransEntry_Hidden">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Account Manager</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Hidden Line</div>  
 
|-
 
|-
 
|  
 
|  
     The company representative that manages the customer's account.
+
     When checked the item will not display on the invoice. It will be in the invoice total.
  
 
|-
 
|-
| colspan="1" style="width: 706px;" | <div id="customeraddress">&nbsp;</div>  
+
| <div id="boTransEntry_UOM">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Address</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: UOM</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's mailing address.
+
     The selected item's unit of measure.  
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerbillingcontact">&nbsp;</div>  
+
| <div id="boTransEntry_ExtPrice">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Billing Contact</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Ext Price</div>  
 
|-
 
|-
 
|  
 
|  
     The primary billing contact assigned to the customer.  
+
     The unit price multiplied by the number of units.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customercity">&nbsp;</div>  
+
| <div id="boTransEntry_BilledStatus">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: City</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Back Office Transaction Entry: Billed Status</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's mailing address city.
+
     Indicates the transaction's position in the billing process.
 +
        N = Not billed
 +
        I = On an unposted invoice
 +
        Y = On a posted invoice
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customercountry">&nbsp;</div>  
+
| <div id="servicetype_AssignedBtn">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Country</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Assigned</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's mailing address country.
+
     When clicked, displays all items assigned to the selected record.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customeremail">&nbsp;</div>  
+
| <div id="servicetype_NotAssingedBtn">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Email</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Not Assigned</div>  
 
|-
 
|-
 
|  
 
|  
     The email address for the primary customer contact.
+
     When clicked, displays all the records not assigned to the selected item.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerext">&nbsp;</div>  
+
| <div id="callboards_FormName">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Ext</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Form Name</div>  
 
|-
 
|-
 
|  
 
|  
     The main telephone numbers extension.
+
     The board name is used to identify the board.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerfacebook">&nbsp;</div>  
+
| <div id="callboards_BoardType">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Facebook</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Board Type</div>  
 
|-
 
|-
 
|  
 
|  
     Link to the customer's Facebook account.
+
     There are three types of boards. 1) Call Central 2) Dispatch 3) Call Center
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerfax">&nbsp;</div>  
+
| <div id="callboards_Private">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Fax</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Private</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's contact fax number.
+
     Private boards will only appear in the list of the user that created the board.  
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerlinkedin">&nbsp;</div>  
+
| <div id="callboards_Default">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: LinkedIn</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Default</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's linked in accounnt handle.
+
     The default form will be the top form in the boards form list.
  
 
|-
 
|-
| colspan="1" style="width: 706px;" | <div id="Cust_Name">&nbsp;</div>  
+
| <div id="callboards_PastDuePosition">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer: Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Past Due Position</div>  
 
|-
 
|-
 
|  
 
|  
     The name of the organization that will be billed.  Jobs can be created without a customer assignment, but not billed.  
+
     If a position is selected from this list, any jobs that are past due will color the cell according to the color settings in the selected position.  
  
 
|-
 
|-
| colspan="1" style="width: 706px;" | <div id="customer_number">&nbsp;</div>  
+
| <div id="callboards_DueWithinPosition">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer: Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Due Within Position</div>  
 
|-
 
|-
 
|  
 
|  
     Customer numbers can be used to help identify a customer. Customer number requirement is based on ERP system.
+
     If a position is selected from this list, any jobs that match the Due Within setting will color the cell according to the settings in the selected position.  
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerpricelevel">&nbsp;</div>  
+
| <div id="callboards_PriorityPosition">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Price Level</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Priority Code Position</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's price level.  Price level requirement is based on ERP settings.
+
     If a position is selected from this list and the color settings for priority codes are setup, the board will use the color settings in the selected position.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerphone">&nbsp;</div>  
+
| <div id="callboards_JobTypesPosition">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Phone</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Job Type Position</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's business telephone number.
+
     If a position is selected from this list and the color settings for Job Types are setup, the board will use the color settings in the selected position.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customersalesperson">&nbsp;</div>  
+
| <div id="callboards_StatusCodesPosition">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Salesperson</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Call Boards: Status Code Position</div>  
 
|-
 
|-
 
|  
 
|  
     The salesperson assigned to the customer's account.  
+
     If a position is selected from this list and the color settings for Status Codes are setup, the board will use the color settings in the selected position.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerstate">&nbsp;</div>  
+
| <div id="chain_Name">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: State</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains</div>  
 
|-
 
|-
 
|  
 
|  
     The customers address state.
+
     Sites can be grouped by chain.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customertwitter">&nbsp;</div>  
+
| <div id="chain_Name">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Twitter</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Name</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's twitter handle.
+
     The name used to identify the chain.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerzip">&nbsp;</div>  
+
| <div id="chain_SLA">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Zip Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: SLA</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's address zip code.
+
     When checked, indicates the chain is an SLA chain. SLA chains have an expiration time for when the work is expected to be started.
  
 
|-
 
|-
| <div id="equip_code">&nbsp;</div>  
+
| <div id="chain_Inbound">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Inbound Path</div>  
 
|-
 
|-
 
|  
 
|  
     Equipment codes are used to identify equipment.  Codes can be manually, or automatically assigned.
+
     The inbound path.
  
 
|-
 
|-
| <div id="equip_comment">&nbsp;</div>  
+
| <div id="chain_Outbound">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Comment</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Outbound Path</div>  
 
|-
 
|-
 
|  
 
|  
     Comments related to the equipment record.
+
     The outbound path.
  
 
|-
 
|-
| <div id="equip_coverageDate">&nbsp;</div>  
+
| <div id="chain_storeTypeCode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Coverage Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Store Type Code</div>  
 
|-
 
|-
 
|  
 
|  
     The date coverage begins for the equipment record.
+
     Stores can be organized by type.
  
 
|-
 
|-
| <div id="equip_description">&nbsp;</div>  
+
| <div id="chain_storeTypeName">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Chains: Store Type Name</div>  
 
|-
 
|-
 
|  
 
|  
     Used to describe the equipment.
+
     The name used to identify the store type.
  
 
|-
 
|-
| <div id="equip_item">&nbsp;</div>  
+
| <div id="Classification">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Item</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Classification</div>  
 
|-
 
|-
 
|  
 
|  
     Equipment records that are also inventory items will have the Item Code in this field.  
+
     The classification is used in sales and cost account assignments. Classifications are assigned to Cost Types and Items.
  
 
|-
 
|-
| <div id="equip_installdate">&nbsp;</div>  
+
| <div id="servicetype_RemoveallAssnBtn">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Install Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Button: Remove all Assignments</div>  
 
|-
 
|-
 
|  
 
|  
     The date the equipment was installed on site.
+
     When clicked, removes all assignments from the selected record.
  
 
|-
 
|-
| <div id="equip_warrlabor">&nbsp;</div>  
+
| <div id="corep_commrate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Commission Rate</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, indicates the equipment is covered by a labor warranty.
+
     The amount of commission that is earned when an item is sold.  
  
 
|-
 
|-
| <div id="equip_warrlaborend">&nbsp;</div>  
+
| <div id="contact_address">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty End</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Address</div>  
 
|-
 
|-
 
|  
 
|  
     The date the labor warranty ends.
+
     The contacts mailing address.
  
 
|-
 
|-
| <div id="equip_warrlaborstart">&nbsp;</div>  
+
| <div id="contact_City">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty Start</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: City</div>  
 
|-
 
|-
 
|  
 
|  
     The date the labor warranty begins.
+
     The city of the contact's mailing address.
  
 
|-
 
|-
| <div id="equip_level">&nbsp;</div>  
+
| <div id="ContactbyEmail">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Level</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Contact by Email Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     Levels are linked to models.  If the level does not appear in the Level drop-list, check the selected model’s setup.
+
     When checked, indicates the customer would permit contact by email.
  
 
|-
 
|-
| <div id="equip_manufacturer">&nbsp;</div>  
+
| <div id="ContactbyFax">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Manufacturer</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Contact by Fax Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The equipment's manufacturer.  Manufacturers are linked to the equipment type.  If you do not see the manufacturer in this list, verify that it is linked to the selected equipment type.  
+
     When checked, indicates the customer would permit contact by fax.
  
 
|-
 
|-
| <div id="equip_mode">&nbsp;</div>  
+
| <div id="ContactbyMail">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Model</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Contact by Mail Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The equipment model. Models are linked to a manufacturer.  If the model does not appear in the model drop-list, check the selected manufacturer's setup.  
+
     When checked, indicates the customer would permit contact by mail.
  
 
|-
 
|-
| <div id="equip_warrparts">&nbsp;</div>  
+
| <div id="ContactbyPhone">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Contact by Phone Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, indicates the equipment is covered by a parts warranty.
+
     When checked, indicates the customer would permit contact by telephone.
  
 
|-
 
|-
| <div id="equip_warrpartsend">&nbsp;</div>  
+
| <div id="contact_country">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty End</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Country</div>  
 
|-
 
|-
 
|  
 
|  
     The date the parts warranty ends.
+
     The country of the mailing address.
  
 
|-
 
|-
| <div id="equip_warrpartsstart">&nbsp;</div>  
+
| <div id="contact_email">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty Start</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Email</div>  
 
|-
 
|-
 
|  
 
|  
     The date the parts warranty begins.
+
     The contact's email address.
  
 
|-
 
|-
| <div id="equip_saledate">&nbsp;</div>  
+
| <div id="contact_estDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Sale Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Established Date</div>  
 
|-
 
|-
 
|  
 
|  
     The date the equipment was sold to the customer.
+
     The date the contact record was established.
  
 
|-
 
|-
| <div id="equip_serialno">&nbsp;</div>  
+
| <div id="contact_fax">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Serial Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Fax Number</div>  
 
|-
 
|-
 
|  
 
|  
     The equipment's serial number. This is not required. 
+
     The contact's fax number.
  
 
|-
 
|-
| <div id="equip_type">&nbsp;</div>  
+
| <div id="contact_firstName">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: First Name</div>  
 
|-
 
|-
 
|  
 
|  
     Equipment types are used to organize equipment.  Manufacturers are assigned by equipment type.  
+
     The contact's first name.  
  
 
|-
 
|-
| <div id="equip_positionLocation">&nbsp;</div>  
+
| <div id="contact_lastName">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Position/Locations</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Last Name</div>  
 
|-
 
|-
 
|  
 
|  
     Indicates the physical location.
+
     The contact's last name.
  
 
|-
 
|-
| <div id="EQType_CODE">&nbsp;</div>  
+
| <div id="contactLinkedIn">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: LinkedIn</div>  
 
|-
 
|-
 
|  
 
|  
     Equipment types are used to groups equipment. Grouping can include manufacturer, model and levels.
+
     The contact's LinkedIn handle.
  
 
|-
 
|-
| <div id="EQType_CODE">&nbsp;</div>  
+
| <div id="contact_ContactName">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Name</div>  
 
|-
 
|-
 
|  
 
|  
     The code that identifies the equipment type.
+
     The contact's full name.
  
 
|-
 
|-
| <div id="EQType_Desc">&nbsp;</div>  
+
| <div id="OptOut">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Opt Out Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The description used to identify the equipment type.  
+
     When checked, indicates that the contact does not want to be contacted for the purpose of marketing.
  
 
|-
 
|-
| <div id="EQType_Prefix">&nbsp;</div>  
+
| <div id="contact_WorkPhone">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Prefix</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Phone</div>  
 
|-
 
|-
 
|  
 
|  
     The three digit prefix to use when auto-numbering new equipment records.
+
     The contact's telephone number.
  
 
|-
 
|-
| <div id="estDollars">&nbsp;</div>  
+
| <div id="contact_Salutation">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Estimated Dollars</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Salutation</div>  
 
|-
 
|-
 
|  
 
|  
     The estimated billing amount required to complete the work.  
+
     The salutation that should be used when communicating with the contact.
  
 
|-
 
|-
| <div id="estHours">&nbsp;</div>  
+
| <div id="contact_state">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Estimated Hours</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: State</div>  
 
|-
 
|-
 
|  
 
|  
     The hours estimated to complete the work.  
+
     The state of the contact's mailing address.
  
 
|-
 
|-
| <div id="Commissionable">&nbsp;</div>  
+
| <div id="contactTeams">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Commissionable</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Teams</div>  
 
|-
 
|-
 
|  
 
|  
     When checked the item is commissionable.
+
     The contact's Teams handle.
  
 
|-
 
|-
| <div id="EQBuild">&nbsp;</div>  
+
| <div id="contact_Title">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">&nbsp;</div> Inventory: Equipment Build Checkbox
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Title</div>  
 
|-
 
|-
| When checked, an equipment record will be generated each time the item is billed. Equipment build has a set of defaults that are defined for use during the process.
+
|  
        Prefix: Used when equipment auto-numbering is activated.
+
    The contact title. ex: Mr., Mrs.
        [[Glossary#equip_type|EQ Type]]
 
        [[Glossary#equip_mode|Model]]
 
        [[Glossary#equip_manufacturer|Manufacturer]]
 
        Labor Warranty Period: The number of months for labor warranty coverage.
 
        Parts Warranty Period: The number of months for parts warranty coverage.
 
        [[Glossary#equip_comment|Comment]]
 
  
 
|-
 
|-
| <div id="inv_ItemCode">&nbsp;</div>  
+
| <div id="contactTwitter">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Twitter</div>  
 
|-
 
|-
 
|  
 
|  
     Used to identify the item.  
+
     The contact's Twitter handle.
  
 
|-
 
|-
| <div id="inv_ItemDescription">&nbsp;</div>  
+
| <div id="contact_Type">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Type</div>  
 
|-
 
|-
 
|  
 
|  
     Describes the item. This information comes from the ERP system.
+
     Contact Types can be used to organize contacts.
  
 
|-
 
|-
| <div id="inv_ItemType">&nbsp;</div>  
+
| <div id="contactWeb">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Web</div>  
 
|-
 
|-
 
|  
 
|  
     Indicates the type of Item.
+
     The contact's website address.
  
 
|-
 
|-
| <div id="itemPrefix">&nbsp;</div>  
+
| <div id="contact_zip">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Prefix</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Contact: Zip</div>  
 
|-
 
|-
 
|  
 
|  
     Used for equipment auto numbering.  If a matrix is in use that calls for this prefix, the system will use the value in this field.  
+
     The postal code of the contact's mailing address.
  
 
|-
 
|-
| <div id="PriceCode">&nbsp;</div>  
+
| <div id="CostType">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Price Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type</div>  
 
|-
 
|-
 
|  
 
|  
     The item's price code. The price code is used when calculating transaction pricing.  
+
     Cost types are used to manage general ledger sales and cost account allocations on transactions and billings.
  
 
|-
 
|-
| <div id="ProductLine">&nbsp;</div>  
+
| <div id="costtype_CostAcct">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Product Line</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Cost Account</div>  
 
|-
 
|-
 
|  
 
|  
     The item's product line.  
+
     The cost account that will be assigned to transactions that match the job type and cost type.  
  
 
|-
 
|-
| <div id="SalesUOM">&nbsp;</div>  
+
| <div id="costtype_CostSubacct">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Sales UOM</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Cost Subaccount</div>  
 
|-
 
|-
 
|  
 
|  
     The item's unit of measure.
+
     The cost sub-account that will be assigned to transactions that match the job type and cost type.  
  
 
|-
 
|-
| <div id="MobileButton">&nbsp;</div>  
+
| <div id="costtype_Desc">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Inventory: Servicer Mobile Button</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Description</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, a mobile button will be made available in mobile for quick entry.
+
     Used to describe the cost type.  
  
 
|-
 
|-
| <div id="shordesc">&nbsp;</div>  
+
| <div id="costtype_InventoryCB">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Short Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Inventory Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     A short description for the item.  
+
     When checked, indicates that the cost type can be used for inventory transactions.  
  
 
|-
 
|-
| <div id="SplitCommission">&nbsp;</div>  
+
| <div id="costtype_LaborCB">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Split Commission</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Labor Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, commission on the item can be slit.
+
     When checked, indicates that the cost type can be used for labor transactions.  
  
 
|-
 
|-
| <div id="TradeDiscount">&nbsp;</div>  
+
| <div id="costtype_PurchasesCB">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Trade Discount</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Type: Purchases Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, discounts are allowed.
+
     When checked, indicates that the cost type can be used for purchase transactions.  
  
 
|-
 
|-
| <div id="unitcost">&nbsp;</div>  
+
| <div id="costVisibility">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Unit Cost</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Cost Visibility</div>  
 
|-
 
|-
 
|  
 
|  
     The item's cost.  
+
     Cost visibility is the ability to hide cost from users.  Cost visibility is set at the user level in Account Management. If the checkbox is marked, the user will be able to view cost.
  
 
|-
 
|-
| <div id="UnitPrice">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customeraccountmanager">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Unit Price</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Account Manager</div>  
 
|-
 
|-
 
|  
 
|  
     The price for the item when added to a transaction.
+
     The company representative that manages the customer's account.
  
 
|-
 
|-
| <div id="UseinMobile">&nbsp;</div>  
+
| colspan="1" style="width: 706px;" | <div id="customeraddress">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Inventory: Use in Mobile</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Address</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the item will be available for use in mobile.  
+
     The customer's mailing address.
  
 
|-
 
|-
| <div id="Warehouse">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customerbillingcontact">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Warehouse</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Billing Contact</div>  
 
|-
 
|-
 
|  
 
|  
     The item's default warehouse.
+
     The primary billing contact assigned to the customer.  
  
 
|-
 
|-
| <div id="job_billed">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customercity">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Billed Status</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: City</div>  
 
|-
 
|-
 
|  
 
|  
     Indicates where the job is in the billing process.
+
     The customer's mailing address city.
  
 
|-
 
|-
| <div id="job_contact">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customercountry">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Contact</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Country</div>  
 
|-
 
|-
 
|  
 
|  
     The site or customer contact assigned to the job.  
+
     The customer's mailing address country.
  
 
|-
 
|-
| <div id="job_contactemail">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customeremail">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Contact Email</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Email</div>  
 
|-
 
|-
 
|  
 
|  
     The email address for the job contact.
+
     The email address for the primary customer contact.
  
 
|-
 
|-
| <div id="job_ext">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customerext">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Extension</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Ext</div>  
 
|-
 
|-
 
|  
 
|  
     The extension number for the contact telephone number
+
     The main telephone numbers extension.
  
 
|-
 
|-
| <div id="jobtype_Code">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customerfacebook">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Job Type Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Facebook</div>  
 
|-
 
|-
 
|  
 
|  
     Used to recognize the job type.
+
     Link to the customer's Facebook account.
  
 
|-
 
|-
| <div id="job_mainno">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customerfax">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Main Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Fax</div>  
 
|-
 
|-
 
|  
 
|  
     The job's main contact telephone number
+
     The customer's contact fax number.
  
 
|-
 
|-
| <div id="job_number">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customerlinkedin">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: LinkedIn</div>  
 
|-
 
|-
 
|  
 
|  
     Used to identify the job.
+
     The customer's linked in account handle.
  
 
|-
 
|-
| <div id="job_pmtmethod">&nbsp;</div>  
+
| colspan="1" style="width: 706px;" | <div id="Cust_Name">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Payment Method</div>  
+
| colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer: Name</div>  
 
|-
 
|-
 
|  
 
|  
     The default payment method.
+
     The name of the organization that will be billed.  Jobs can be created without a customer assignment, but not billed.  
  
 
|-
 
|-
| <div id="job_phone">&nbsp;</div>  
+
| colspan="1" style="width: 706px;" | <div id="customer_number">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Phone</div>  
+
| colspan="1" style="width: 706px;" | <div class="fieldHeader">Customer: Number</div>  
 
|-
 
|-
 
|  
 
|  
     The contact telephone number for the job.  
+
     Customer numbers can be used to help identify a customer. Customer number requirement is based on ERP system.
  
 
|-
 
|-
| <div id="primaryservicer">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customerpricelevel">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Primary Servicer</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Price Level</div>  
 
|-
 
|-
 
|  
 
|  
     The primary servicer for the job. New jobs will automatically use the primary servicer.
+
     The customer's price level. Price level requirement is based on ERP settings.
  
 
|-
 
|-
| <div id="job_receiveddate">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customerphone">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Received Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Phone</div>  
 
|-
 
|-
 
|  
 
|  
     The date the job was received from the customer.  
+
     The customer's business telephone number.
  
 
|-
 
|-
| <div id="job_refno">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customersalesperson">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Reference Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Salesperson</div>  
 
|-
 
|-
 
|  
 
|  
     The default payment reference number.
+
     The salesperson assigned to the customer's account.  
  
 
|-
 
|-
| <div id="job_saleperson">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customerstate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Salesperson</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: State</div>  
 
|-
 
|-
 
|  
 
|  
     The salesperson for the job.  *Certain ERP systems require a salesperson.
+
     The customer's address state.
  
 
|-
 
|-
| <div id="job_sendtomobile">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customertwitter">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Job: Send to Mobile Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Twitter</div>  
 
|-
 
|-
| On save, if this checkbox is checked, the job will be made available in mobile.
+
|  
 +
    The customer's twitter handle.
 +
 
 
|-
 
|-
| <div id="job_servicetype">&nbsp;</div>  
+
| colspan="1" style="width: 1538px;" | <div id="customerzip">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Service Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Customer: Zip Code</div>  
 
|-
 
|-
 
|  
 
|  
     Service types are used to organize jobs.  Service type are organized by job type.  
+
     The customer's address zip code.
  
 
|-
 
|-
| <div id="job_sla">&nbsp;</div>  
+
| <div id="DispatchCardNumber">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Card Number</div>  
 
|-
 
|-
 
|  
 
|  
     Check this box, if the job qualifies for SLA service. This defaults from the site.
+
     Dispatch cards are numbered from 0 up.
  
 
|-
 
|-
| <div id="job_slaExp">&nbsp;</div>  
+
| <div id="Dispatch_Number">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Expiration Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Number</div>  
 
|-
 
|-
 
|  
 
|  
     The date the technician has to start the work in order to meet the SLA criteria.
+
     The number used to identify the dispatch card.
  
 
|-
 
|-
| <div id="job_slaExpTime">&nbsp;</div>  
+
| <div id="DispatchCardPriority">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Expiration Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Priority</div>  
 
|-
 
|-
 
|  
 
|  
     The time the technician has to start the work in order to meet the SLA criteria.
+
     The priority assigned to the dispatch card.  
  
 
|-
 
|-
| <div id="job_status">&nbsp;</div>  
+
| <div id="PrimaryDispatchCard">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Status</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Primary Dispatch Card</div>  
 
|-
 
|-
 
|  
 
|  
     Status codes are used to determine the job's position in the work process.  
+
     Once a job is created, the primary dispatch card is created. Users can also generate additional dispatch cards.
  
 
|-
 
|-
| <div id="job_statusbar">&nbsp;</div>  
+
| <div id="DispatchCardScheduleDate">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Job: Status Bar</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Schedule Date</div>  
 
|-
 
|-
 
|  
 
|  
     The status bar indicates the job's status progress.
+
     The dispatch card's schedule date.  
  
 
|-
 
|-
| <div id="jobtype_Desc">&nbsp;</div>  
+
| <div id="DispatchCardScheduleTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Schedule Time</div>  
 
|-
 
|-
 
|  
 
|  
     Used to describe the job type.  
+
     The dispatch card's schedule time.  
  
 
|-
 
|-
| <div id="EstHours">&nbsp;</div>  
+
| <div id="Servicer">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Estimated Hours</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Servicer</div>  
 
|-
 
|-
 
|  
 
|  
     The hours estimated to complete the job.  
+
     The servicer that is assigned the work.
  
 
|-
 
|-
| <div id="jobType">&nbsp;</div>  
+
| <div id="DispatchCardStatus">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Dispatch: Status</div>  
 
|-
 
|-
 
|  
 
|  
     Job types are used to organize jobs by type and service types. Job types are tied to the billing sales and cost accounts for transactions.  
+
     The status assigned to the individual dispatch card.
  
 
|-
 
|-
| <div id="KPICallCount">&nbsp;</div>  
+
| <div id="equip_code">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: KPI Call Count Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Code</div>  
 
|-
 
|-
 
|  
 
|  
     When checked the jobs assigned the job type will be counted in the KPI analytics.
+
     Equipment codes are used to identify equipment.  Codes can be manually, or automatically assigned.
  
 
|-
 
|-
| <div id="Opportunity">&nbsp;</div>  
+
| <div id="equip_comment">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Opportunity</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Comments</div>  
 
|-
 
|-
 
|  
 
|  
     Marks the job type as a job opportunity.
+
     Comments related to the equipment record.
  
 
|-
 
|-
| <div id="jt_QuotedDollars">&nbsp;</div>  
+
| <div id="equip_coverageDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Quoted $s</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Coverage Date</div>  
 
|-
 
|-
 
|  
 
|  
     The dollars quoted for the job.  
+
     The date coverage begins for the equipment record.
  
 
|-
 
|-
| <div id="kpi">&nbsp;</div>  
+
| <div id="equip_description">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Description</div>  
 
|-
 
|-
 
|  
 
|  
     KPI fields are indicators of job profit and profitability.
+
     Used to describe the equipment.
  
 
|-
 
|-
| <div id="DepartureDate">&nbsp;</div>  
+
| <div id="equip_item">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Departure Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Item</div>  
 
|-
 
|-
 
|  
 
|  
     The date the job was changed to the departed status code.
+
     Equipment records that are also inventory items will have the Item Code in this field.  
  
 
|-
 
|-
| <div id="DepartureTime">&nbsp;</div>  
+
| <div id="equip_installdate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Departure Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Install Date</div>  
 
|-
 
|-
 
|  
 
|  
     The time the job was changed to the departed status code.
+
     The date the equipment was installed on site.
  
 
|-
 
|-
| <div id="JobStartDate">&nbsp;</div>  
+
| <div id="equip_warrlabor">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Start Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The date the job started.
+
     When checked, indicates the equipment is covered by a labor warranty.
  
 
|-
 
|-
| <div id="JobStartTime">&nbsp;</div>  
+
| <div id="equip_warrlaborend">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Start Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty End</div>  
 
|-
 
|-
 
|  
 
|  
     The time the job started.
+
     The date the labor warranty ends.
  
 
|-
 
|-
| <div id="JobCompleteDate">&nbsp;</div>  
+
| <div id="equip_warrlaborstart">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Complete Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Labor Warranty Start</div>  
 
|-
 
|-
 
|  
 
|  
     The date the job was marked complete.
+
     The date the labor warranty begins.
  
 
|-
 
|-
| <div id="JobCompleteTime">&nbsp;</div>  
+
| <div id="equip_level">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Complete Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Level</div>  
 
|-
 
|-
 
|  
 
|  
     The time the job was marked complete.
+
     Levels are linked to models.  If the level does not appear in the Level drop-list, check the selected model’s setup.
  
 
|-
 
|-
| <div id="JobRevenue">&nbsp;</div>  
+
| <div id="equip_manufacturer">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Revenues</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Manufacturer</div>  
 
|-
 
|-
 
|  
 
|  
     The total revenues to date.
+
     The equipment's manufacturer.  Manufacturers are linked to the equipment type.  If you do not see the manufacturer in this list, verify that it is linked to the selected equipment type.  
  
 
|-
 
|-
| <div id="JobElapseTime">&nbsp;</div>  
+
| <div id="equip_mode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Elapse Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Model</div>  
 
|-
 
|-
 
|  
 
|  
     The time between the received date/time and the job close date/time. If the job is not closed the current date is used as the cut-off.  
+
     The equipment model. Models are linked to a manufacturer. If the model does not appear in the model drop-list, check the selected manufacturer's setup.  
  
 
|-
 
|-
| <div id="JobRepairTime">&nbsp;</div>  
+
| <div id="equip_warrparts">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Repair Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The labor hours posted to date.
+
     When checked, indicates the equipment is covered by a parts warranty.
  
 
|-
 
|-
| <div id="JobResponseTime">&nbsp;</div>  
+
| <div id="equip_warrpartsend">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Response Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty End</div>  
 
|-
 
|-
 
|  
 
|  
     The time between the received date/time and the arrival date/time.
+
     The date the parts warranty ends.
  
 
|-
 
|-
| <div id="JobProfit">&nbsp;</div>  
+
| <div id="equip_warrpartsstart">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Profit</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Parts Warranty Start</div>  
 
|-
 
|-
 
|  
 
|  
     The job's profit to date.
+
     The date the parts warranty begins.
  
 
|-
 
|-
| <div id="Jobbilledstatus">&nbsp;</div>  
+
| <div id="equip_saledate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Invoice Status</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Sale Date</div>  
 
|-
 
|-
 
|  
 
|  
     The job's billing status.
+
     The date the equipment was sold to the customer.
  
 
|-
 
|-
| <div id="JobinvoiceDate">&nbsp;</div>  
+
| <div id="equip_serialno">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Invoice Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Serial Number</div>  
 
|-
 
|-
 
|  
 
|  
     The date the job was first invoiced.
+
     The equipment's serial number. This is not required. 
  
 
|-
 
|-
| <div id="level_Code">&nbsp;</div>  
+
| <div id="equip_type">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Type</div>  
 
|-
 
|-
 
|  
 
|  
     Models can be grouped by levels. Levels can be grouped by type.
+
     Equipment types are used to organize equipment. Manufacturers are assigned by equipment type.  
  
 
|-
 
|-
| <div id="level_Code">&nbsp;</div>  
+
| <div id="equip_positionLocation">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment: Position/Locations</div>  
 
|-
 
|-
 
|  
 
|  
     The code used to identify the level.  
+
     Indicates the equipment's physical location.
  
 
|-
 
|-
| <div id="level_Desc">&nbsp;</div>  
+
| <div id="EQType_CODE">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type</div>  
 
|-
 
|-
 
|  
 
|  
     The description that identifies the level.
+
     Equipment types are used to groups equipment. Grouping can include manufacturer, model and levels.
  
 
|-
 
|-
| <div id="level_prefix">&nbsp;</div>  
+
| <div id="EQType_CODE">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Prefix</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Code</div>  
 
|-
 
|-
 
|  
 
|  
     The three digit prefix to use when auto-numbering new equipment records.
+
     The code that identifies the equipment type.
  
 
|-
 
|-
| <div id="levelType">&nbsp;</div>  
+
| <div id="EQType_Desc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Description</div>  
 
|-
 
|-
 
|  
 
|  
     Level types are used to group levels.
+
     The description used to identify the equipment type.  
  
 
|-
 
|-
| <div id="Location">&nbsp;</div>  
+
| <div id="EQType_Prefix">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Location</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Equipment Type: Prefix</div>  
 
|-
 
|-
 
|  
 
|  
     Indicates the phusical location of a piece of equipment at a site.
+
     The three digit prefix to use when auto-numbering new equipment records.
  
 
|-
 
|-
| <div id="Manufacturer">&nbsp;</div>  
+
| <div id="estDollars">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Estimated Dollars</div>  
 
|-
 
|-
 
|  
 
|  
     The manufacturer is assigned to equipment records. The manufacturer is assigned models. 
+
     The estimated billing amount required to complete the work.  
  
 
|-
 
|-
| <div id="Manu_Code">&nbsp;</div>  
+
| <div id="estHours">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Estimated Hours</div>  
 
|-
 
|-
 
|  
 
|  
     The code used to identify the manufacturer.
+
     The hours estimated to complete the work.  
  
 
|-
 
|-
| <div id="Manu_Desc">&nbsp;</div>  
+
| <div id="ftpServer">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">FTP Server</div>  
 
|-
 
|-
 
|  
 
|  
     The description that identifies the manufacturer.
+
     The server address required to log into your ftp server account.  
  
 
|-
 
|-
| <div id="Manu_Prefix">&nbsp;</div>  
+
| <div id="ftpuser">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Prefix</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">FTP Username</div>  
 
|-
 
|-
 
|  
 
|  
     The three digit prefix to use when auto-numbering new equipment records.
+
     The server username required to log into your ftp server account.  
  
 
|-
 
|-
| <div id="model_Code">&nbsp;</div>  
+
| <div id="ftppassword">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">FTP Password</div>  
 
|-
 
|-
 
|  
 
|  
     The code used to identify the model.
+
     The server password that is required to log into your ftp server account.  
  
 
|-
 
|-
| <div id="model_Desc">&nbsp;</div>  
+
| <div id="hiddenCheckbox">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Hidden Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The description that identifies the model.
+
     When checked, the item to which the checkbox is assigned will be hidden on invoices.  
  
 
|-
 
|-
| <div id="model_prefix">&nbsp;</div>  
+
| <div id="Commissionable">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Prefix</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Commissionable</div>  
 
|-
 
|-
 
|  
 
|  
     The three digit prefix to use when auto-numbering new equipment records.
+
     When checked the item is commissionable.
  
 
|-
 
|-
| <div id="NoteCategory">&nbsp;</div>  
+
| <div id="EQBuild">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Category</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">&nbsp;</div> Inventory: Equipment Build Checkbox
 
|-
 
|-
 
|  
 
|  
     Notes can be organized by category.
+
     When checked, an equipment record will be generated each time the item is billed. Equipment build has a set of defaults that are defined for use during the process.
 +
        Prefix: Used when equipment auto-numbering is activated.
 +
        [[Glossary#equip_type|EQ Type]]
 +
        [[Glossary#equip_mode|Model]]
 +
        [[Glossary#equip_manufacturer|Manufacturer]]
 +
        Labor Warranty Period: The number of months for labor warranty coverage.
 +
        Parts Warranty Period: The number of months for parts warranty coverage.
 +
        [[Glossary#equip_comment|Comment]]
  
 
|-
 
|-
| <div id="NoteContent">&nbsp;</div>  
+
| <div id="inv_ItemCode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Content</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Code</div>  
 
|-
 
|-
 
|  
 
|  
     The note content that will display on the form and print on any documents.
+
     Used to identify the item.  
  
 
|-
 
|-
| <div id="NoteInternal">&nbsp;</div>  
+
| <div id="inv_ItemDescription">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Internal Note Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Description</div>  
 
|-
 
|-
 
|  
 
|  
     Internal notes do not print on invoices and dispatch cards.
+
     Describes the item. This information comes from the ERP system.
  
 
|-
 
|-
| <div id="NotePrintOnTicket">&nbsp;</div>  
+
| <div id="inv_ItemType">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Print Note on Ticket Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Item Type</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the note will print on the dispatch card.
+
     Indicates the type of Item.
  
 
|-
 
|-
| <div id="PlannedMaintenanceType">&nbsp;</div>  
+
| <div id="itemPrefix">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Prefix</div>  
 
|-
 
|-
 
|  
 
|  
     Planned maintenance types are used to organize schedules and establish default values.
+
     Used for equipment auto numbering.  If a matrix is in use that calls for this prefix, the system will use the value in this field.  
  
 
|-
 
|-
| <div id="PlannedMaintenanceID">&nbsp;</div>  
+
| <div id="PriceCode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: ID</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Price Code</div>  
 
|-
 
|-
 
|  
 
|  
     The ID is used to identify the schedule.
+
     The item's price code. The price code is used when calculating transaction pricing.  
  
 
|-
 
|-
| <div id="PlannedMaintenanceDescription">&nbsp;</div>  
+
| <div id="ProductLine">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Product Line</div>  
 
|-
 
|-
 
|  
 
|  
     Descriptions can also help in identification.
+
     The item's product line.  
  
 
|-
 
|-
| <div id="MaterialGroupCode">&nbsp;</div>  
+
| <div id="SalesUOM">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Material Group Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Sales UOM</div>  
 
|-
 
|-
 
|  
 
|  
     Matieral Group Codes provide the ability to add materials to schedules by grouping.  
+
     The item's unit of measure.
  
 
|-
 
|-
| <div id="PlannedMaintenanceTaskCode">&nbsp;</div>  
+
| <div id="MobileButton">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Task Code</div>  
+
| <div class="fieldHeader">Inventory: Servicer Mobile Button</div>  
 
|-
 
|-
 
|  
 
|  
     PM task codes are used to organize schedules and establish material group codes.
+
     When checked, a mobile button will be made available in mobile for quick entry.
  
 
|-
 
|-
| <div id="Priority">&nbsp;</div>  
+
| <div id="shordesc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Short Description</div>  
 
|-
 
|-
 
|  
 
|  
     The default priority that will be used when creating new jobs to establish schedule date and timePriorities are assigned to sites as a default for new jobs.  
+
     A short description for the item. This description may be limited by ERP systemsUsers can set the size of this field. When changed the software will replace the existing short description with a new short description using the number of characters stored in this field.  
  
 
|-
 
|-
| <div id="PriorityCode">&nbsp;</div>  
+
| <div id="SplitCommission">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Split Commission</div>  
 
|-
 
|-
 
|  
 
|  
     Priority codes are used to establish the response time when scheduling jobs.
+
     When checked, commission on the item can be slit.
  
 
|-
 
|-
| <div id="prio_dow">&nbsp;</div>  
+
| <div id="TradeDiscount">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Day of the Week</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Trade Discount</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, indicates that jobs can be schedules on that day of the week.
+
     When checked, discounts are allowed.
  
 
|-
 
|-
| <div id="">&nbsp;</div>  
+
| <div id="unitcost">&nbsp;</div>  
 
|-
 
|-
| &nbsp;
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Unit Cost</div>  
|-
 
| <div id="prio_Desc">&nbsp;</div>
 
|-
 
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Description</div>  
 
 
|-
 
|-
 
|  
 
|  
     Describe the priority.
+
     The item's cost.  
  
 
|-
 
|-
| <div id="prio_endtime">&nbsp;</div>  
+
| <div id="UnitPrice">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: End Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Unit Price</div>  
 
|-
 
|-
 
|  
 
|  
     Indicates the latest time a job can be scheduled on each day of the week.
+
     The price for the item when added to a transaction.
  
 
|-
 
|-
| <div id="ResponseTime">&nbsp;</div>  
+
| <div id="UseinMobile">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Response Time</div>  
+
| <div class="fieldHeader">Inventory: Use in Mobile</div>  
 
|-
 
|-
 
|  
 
|  
     Indicates the number of hours between the received time and the schedule time.  
+
     When checked, the item will be available for use in mobile.  
  
 
|-
 
|-
| <div id="prio_SLA">&nbsp;</div>  
+
| <div id="Warehouse">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: SLA</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Inventory: Warehouse</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, indicates the priority is an SLA code. Only priority codes marked SLA will appear for jobs created on and SLA site.
+
     The item's default warehouse.
  
 
|-
 
|-
| <div id="prio_SLAExp">&nbsp;</div>  
+
| <div id="job_billed">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: SLA Expiration</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Billed Status</div>  
 
|-
 
|-
 
|  
 
|  
     The number of hours that are required to meet the SLA deadline.  
+
     Indicates where the job is in the billing process.
  
 
|-
 
|-
| <div id="prio_starttime">&nbsp;</div>  
+
| <div id="job_contact">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Start Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Contact</div>  
 
|-
 
|-
 
|  
 
|  
     Indicated the earliest time a job can be scheduled on each day of the week.
+
     The site or customer contact assigned to the job.  
  
 
|-
 
|-
| <div id="QuotedDollars">&nbsp;</div>  
+
| <div id="job_contactemail">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Quoted Dollars</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Contact Email</div>  
 
|-
 
|-
 
|  
 
|  
     The billing amount quoted for the job.  
+
     The email address for the job contact.
  
 
|-
 
|-
| <div id="QuotedHours">&nbsp;</div>  
+
| <div id="job_ext">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Quoted Hours</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Extension</div>  
 
|-
 
|-
 
|  
 
|  
     The hours quoted for the job.   
+
     The extension number for the contact telephone number
  
 
|-
 
|-
| <div id="ReportingGroups">&nbsp;</div>  
+
| <div id="jobtype_Code">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Reporting Groups</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Job Type Code</div>  
 
|-
 
|-
 
|  
 
|  
     A group code can be assigned to a miscellaneous charge code to group like Item codes.  
+
     Used to recognize the job type.
  
 
|-
 
|-
| <div id="corep_repaddress">&nbsp;</div>  
+
| <div id="job_mainno">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Address</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Main Number</div>  
 
|-
 
|-
 
|  
 
|  
     The mailing address for the representative.
+
     The job's main contact telephone number
  
 
|-
 
|-
| <div id="corep_city">&nbsp;</div>  
+
| <div id="job_notes">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: City</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Notes</div>  
 
|-
 
|-
 
|  
 
|  
     The city for the mailing address
+
     Job notes are unlimited and can be printed on documents. 
  
 
|-
 
|-
| <div id="corep_country">&nbsp;</div>  
+
| <div id="job_number">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Country</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Number</div>  
 
|-
 
|-
 
|  
 
|  
     The country for the mailing address.
+
     Used to identify the job.
  
 
|-
 
|-
| <div id="corep_repdivision">&nbsp;</div>  
+
| <div id="job_pmtmethod">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Division</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Payment Method</div>  
 
|-
 
|-
 
|  
 
|  
     If division are in use, the representative division can be assigned.
+
     The default payment method.
  
 
|-
 
|-
| <div id="corep_repemail">&nbsp;</div>  
+
| <div id="job_phone">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Email</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Phone</div>  
 
|-
 
|-
 
|  
 
|  
     The email address used to contact the representative.
+
     The contact telephone number for the job.  
  
 
|-
 
|-
| <div id="corep_repname">&nbsp;</div>  
+
| <div id="primaryservicer">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Primary Servicer</div>  
 
|-
 
|-
 
|  
 
|  
     The name of the representative.
+
     The primary servicer for the job. New jobs will automatically use the primary servicer. Set up on the site level servicer #1
  
 
|-
 
|-
| <div id="corep_repno">&nbsp;</div>  
+
| <div id="job_receiveddate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Received Date</div>  
 
|-
 
|-
 
|  
 
|  
     The representative number can be used to recognize a representative.
+
     The date the job was entered into the system by a user.  
  
 
|-
 
|-
| <div id="corep_repphone">&nbsp;</div>  
+
| <div id="job_receivedtime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Phone</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Received Time</div>  
 
|-
 
|-
 
|  
 
|  
     The telephone number used to contact the representative.
+
     The time the job was received from the customer.  
  
 
|-
 
|-
| <div id="corep_state">&nbsp;</div>  
+
| <div id="job_refno">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: State</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Reference Number</div>  
 
|-
 
|-
 
|  
 
|  
     The state for the mailing address.
+
     The default payment reference number.
  
 
|-
 
|-
| <div id="corep_reptype">&nbsp;</div>  
+
| <div id="job_saleperson">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Salesperson</div>  
 
|-
 
|-
 
|  
 
|  
     Types are used to organize representatives.
+
     The salesperson for the job.  *Certain ERP systems require a salesperson.
  
 
|-
 
|-
| <div id="corep_zip">&nbsp;</div>  
+
| <div id="job_servicetype">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Zip</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Service Type</div>  
 
|-
 
|-
 
|  
 
|  
     The postal code for the mailing address.
+
     Service types are used to organize and recognize jobs.  Service types are organized by job type.  
  
 
|-
 
|-
| <div id="job_request">&nbsp;</div>  
+
| <div id="job_sla">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Request</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     Requests are defined using the Request Management feature. The request defines the work requested.  
+
     Check this box if the job qualifies for SLA service. This defaults from the site.
  
 
|-
 
|-
| <div id="job_requestnote">&nbsp;</div>  
+
| <div id="job_slaExp">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Request Notes</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Expiration Date</div>  
 
|-
 
|-
 
|  
 
|  
     Request notes are used to further define the work requested.
+
     The date the technician must start the work to meet the SLA criteria.
  
 
|-
 
|-
| <div id="costtype_RevAcct">&nbsp;</div>  
+
| <div id="job_slaExpTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue Account</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: SLA Expiration Time</div>  
 
|-
 
|-
 
|  
 
|  
     The sales account that will be assigned to transactions assigned this job type and cost type.  
+
     The time the technician must start the work to meet the SLA criteria.
  
 
|-
 
|-
| <div id="costtype_RevSubacct">&nbsp;</div>  
+
| <div id="job_status">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue subaccount</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job: Status</div>  
 
|-
 
|-
 
|  
 
|  
     The sales sub-account that will be assigned to transactions assigned this job type and cost type.  
+
     Status codes are used to determine the job's position in the work process.  
  
 
|-
 
|-
| <div id="job_scheduledate">&nbsp;</div>  
+
| <div id="job_statusbar">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Date</div>  
+
| <div class="fieldHeader">Job: Status Bar</div>  
 
|-
 
|-
 
|  
 
|  
     The date the technician is schedule to do the work.
+
     The status bar indicates the job's status progress.
  
 
|-
 
|-
| <div id="job_scheduletime">&nbsp;</div>  
+
| <div id="jobtype_Desc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Description</div>  
 
|-
 
|-
 
|  
 
|  
     The time the technician is schedule to do the work.
+
     Used to describe the job type.  
  
 
|-
 
|-
| <div id="servicer_Number">&nbsp;</div>  
+
| <div id="EstHours">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Estimated Hours</div>  
 
|-
 
|-
 
|  
 
|  
     The technician that will perform the work.
+
     The hours estimated to complete the job.  
  
 
|-
 
|-
| <div id="servicer_Number">&nbsp;</div>  
+
| <div id="jobType">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type</div>  
 
|-
 
|-
 
|  
 
|  
     The number used to identify the technician.
+
     Job types are used to organize jobs by type and service types. Job types are tied to the billing sales and cost accounts for transactions.  
  
 
|-
 
|-
| <div id="servicer_employee">&nbsp;</div>  
+
| <div id="KPICallCount">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Employee Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: KPI Call Count Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     If the servicer is also an employee, the employee number can be stored in this field.  
+
     When checked the jobs assigned the job type will be counted in the KPI analytics.
  
 
|-
 
|-
| <div id="servicer_subcontractor">&nbsp;</div>  
+
| <div id="Opportunity">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Subcontractor Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Opportunity</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, indicates that the servicer is a contracted employee or vendor.
+
     Marks the job type as a job opportunity.
  
 
|-
 
|-
| <div id="svr_Name">&nbsp;</div>  
+
| <div id="jt_QuotedDollars">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Job Type: Quoted $s</div>  
 
|-
 
|-
 
|  
 
|  
     The name of the technician.
+
     The dollars quoted for the job.  
  
 
|-
 
|-
| <div id="svr_Vendor">&nbsp;</div>  
+
| <div id="kpi">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Vendor</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI</div>  
 
|-
 
|-
 
|  
 
|  
     If the servicers is a vendor, the vendor can be recorded on this record.
+
     KPI fields are indicators of job profit and profitability.
  
 
|-
 
|-
| <div id="svr_Address">&nbsp;</div>  
+
| <div id="DepartureDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Address</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Departure Date</div>  
 
|-
 
|-
 
|  
 
|  
     The technician's mailing address.
+
     The date the job was changed to the departed status code.
  
 
|-
 
|-
| <div id="svr_BillingRate">&nbsp;</div>  
+
| <div id="DepartureTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Billing Rate</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Departure Time</div>  
 
|-
 
|-
 
|  
 
|  
     The technicians hourly labor billing rate.
+
     The time the job was changed to the departed status code.
  
 
|-
 
|-
| <div id="svr_PORequired">&nbsp;</div>  
+
| <div id="JobStartDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: PO Required Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Start Date</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the vendor requires a purchase order for all requested work.
+
     The date the job started.
  
 
|-
 
|-
| <div id="svr_HrlyCost">&nbsp;</div>  
+
| <div id="JobStartTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Hourly Cost</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Start Time</div>  
 
|-
 
|-
 
|  
 
|  
     The hourly cost for the technician.
+
     The time the job started.
  
 
|-
 
|-
| <div id="svr_InsCert">&nbsp;</div>  
+
| <div id="JobCompleteDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Insurance Certificate on File Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Complete Date</div>  
 
|-
 
|-
 
|  
 
|  
     For use with vendors or contract employees only. Indicates that a Certificate of Insurance is on file.
+
     The date the job was marked complete.
  
 
|-
 
|-
| <div id="svr_burden">&nbsp;</div>  
+
| <div id="JobCompleteTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Burden</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Complete Time</div>  
 
|-
 
|-
 
|  
 
|  
     The hourly burden for the technician.  
+
     The time the job was marked complete.
  
 
|-
 
|-
| <div id="svr_certFile">&nbsp;</div>  
+
| <div id="JobRevenue">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Certificate File Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Revenues</div>  
 
|-
 
|-
 
|  
 
|  
     The file name for the Certificate of Insurance.
+
     The total revenues to date.
  
 
|-
 
|-
| <div id="svr_city">&nbsp;</div>  
+
| <div id="JobElapseTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: City</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Elapse Time</div>  
 
|-
 
|-
 
|  
 
|  
     The servicer's mailing address city.
+
     The time between the received date/time and the job close date/time. If the job is not closed the current date is used as the cut-off.  
  
 
|-
 
|-
| <div id="svr_warehouse">&nbsp;</div>  
+
| <div id="JobRepairTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Warehouse</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Repair Time</div>  
 
|-
 
|-
 
|  
 
|  
     The servicer's default warehouse.
+
     The labor hours posted to date.
  
 
|-
 
|-
| <div id="svr_terms">&nbsp;</div>  
+
| <div id="JobResponseTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Terms</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Response Time</div>  
 
|-
 
|-
 
|  
 
|  
     If the servicer is a vendor or contract employee, the terms for payment.  
+
     The time between the received date/time and the arrival date/time.
  
 
|-
 
|-
| <div id="svr_State">&nbsp;</div>  
+
| <div id="JobProfit">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: State</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Profit</div>  
 
|-
 
|-
 
|  
 
|  
     The servicer's mailing address state.
+
     The job's profit to date.
  
 
|-
 
|-
| <div id="svr_Zip">&nbsp;</div>  
+
| <div id="Jobbilledstatus">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Zip</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Job Invoice Status</div>  
 
|-
 
|-
 
|  
 
|  
     The servicer's mailing address postal code.
+
     The job's billing status.
  
 
|-
 
|-
| <div id="svr_Email">&nbsp;</div>  
+
| <div id="JobinvoiceDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Email</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">KPI: Invoice Date</div>  
 
|-
 
|-
 
|  
 
|  
     The servicer's email address.
+
     The date the job was first invoiced.
  
 
|-
 
|-
| <div id="svr_Mobile">&nbsp;</div>  
+
| <div id="level_Code">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Mobile Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the servicer's jobs will appear on the mobile board.
+
     Models can be grouped by levels. Levels can be grouped by type.
  
 
|-
 
|-
| <div id="svr_country">&nbsp;</div>  
+
| <div id="level_Code">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Country</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Code</div>  
 
|-
 
|-
 
|  
 
|  
     The servicer's mailing address country
+
     The code used to identify the level.
  
 
|-
 
|-
| <div id="svr_estDate">&nbsp;</div>  
+
| <div id="level_Desc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Established Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Description</div>  
 
|-
 
|-
 
|  
 
|  
     The date the servicer relationship was established.
+
     The description that identifies the level.
  
 
|-
 
|-
| <div id="svr_userList">&nbsp;</div>  
+
| <div id="level_prefix">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: User List</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Prefix</div>  
 
|-
 
|-
 
|  
 
|  
     Servicers must be attached to a user login in order to use the mobile system.
+
     The three digit prefix to use when auto-numbering new equipment records.
  
 
|-
 
|-
| <div id="svr_phone">&nbsp;</div>  
+
| <div id="levelType">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Phone</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Levels: Type</div>  
 
|-
 
|-
 
|  
 
|  
     The telephone number for contacting the servicer.
+
     Level types are used to group levels.
  
 
|-
 
|-
| <div id="svr_imgFile">&nbsp;</div>  
+
| <div id="Location">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Servicer Image File</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Location</div>  
 
|-
 
|-
 
|  
 
|  
     The name of the file that contain an image of the technician.
+
     Indicates the physical location of a piece of equipment at a site.
  
 
|-
 
|-
| <div id="svr_dispatchBatch">&nbsp;</div>  
+
| <div id="Manufacturer">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Service Dispatch Batch</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer</div>  
 
|-
 
|-
 
|  
 
|  
     Mobile jobs can be grouped by batch for posting to the back office.  
+
     The manufacturer is assigned to equipment records. The manufacturer is assigned models. 
  
 
|-
 
|-
| <div id="svr_tomtom">&nbsp;</div>  
+
| <div id="Manu_Code">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Tom Tom ID</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Code</div>  
 
|-
 
|-
 
|  
 
|  
     The Tom Tom ID for the servicer.   
+
     The code used to identify the manufacturer.   
  
 
|-
 
|-
| <div id="svr_userMapPin">&nbsp;</div>  
+
| <div id="Manu_Desc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: User Map Pin</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Description</div>  
 
|-
 
|-
 
|  
 
|  
     Technicians can be mapped using pins.
+
     The description that identifies the manufacturer.
  
 
|-
 
|-
| <div id="svr_userMapPin">&nbsp;</div>  
+
| <div id="Manu_Prefix">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults: New Job Defaults</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Manufacturer: Prefix</div>  
 
|-
 
|-
 
|  
 
|  
     The values that will be used by default when adding new jobs. Some of these values can be changed at the job level.
+
     The three digit prefix to use when auto-numbering new equipment records.
        [[Glossary#job_request|Request]]
 
        [[Glossary#ss_OverrideJobNo|Override Job No]]
 
        [[Glossary#ss_SendJobEmail|Send Job Email]]
 
        [[Glossary#jobType|Job Type]]
 
        [[Glossary#servicetype|Service Type]]
 
        [[Glossary#Priority|Priority]]
 
        [[Glossary#ss_EstHours|Est Hours]]
 
        [[Glossary#ss_JobNextNo|Job Next No]]
 
        [[Glossary#ss_JobLength|Job Length]]
 
        [[Glossary#ss_JobLeadingCharacters|Job Leading Characters]]
 
  
 
|-
 
|-
| <div id="ss_OverrideJobNo">&nbsp;</div>  
+
| <div id="Message_TargetType">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Override Job No Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Target Type</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, users are allowed to alter the job number.  Warning! This could interrupt the job numbering system.
+
     Defines the type of target audience for the message.
  
 
|-
 
|-
| <div id="ss_SendJobEmail">&nbsp;</div>  
+
| <div id="Message_DefaultTargetType">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Send Job Email Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Default Target Type</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the send email form will be displayed when a new job is saved.
+
     Defines the type of target audience for the message as the default value for new messages.
  
 
|-
 
|-
| <div id="ss_EstHours">&nbsp;</div>  
+
| <div id="Message_Target">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Est Hours</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Target</div>  
 
|-
 
|-
 
|  
 
|  
     The hours estimated to complete the job. This value will be added to the primary work order.
+
     Defines a specific target for a message. Targets are Users, Servicers or Dispatch groups.  
  
 
|-
 
|-
| <div id="ss_JobNextNo">&nbsp;</div>  
+
| <div id="Message_StartDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Next No</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Start Date</div>  
 
|-
 
|-
 
|  
 
|  
     The number that will be assigned to the next job.  
+
     The first date active messages are displayed.  
  
 
|-
 
|-
| <div id="ss_JobLength">&nbsp;</div>  
+
| <div id="Message_EndDate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Length</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: End Date</div>  
 
|-
 
|-
 
|  
 
|  
     The number of characters in the job number.
+
     The last date active messages will be displayed.  Note: All messages are removed after 72 hours.  
 
 
 
|-
 
|-
| <div id="ss_JobLeadingCharacters">&nbsp;</div>  
+
| <div id="Message_MessageText">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Leading Characters</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Message Text</div>  
 
|-
 
|-
 
|  
 
|  
     The character(s) that will lead the job number. This is not required.
+
     The content of the message.  
  
 
|-
 
|-
| <div id="ss_ShortDescSize">&nbsp;</div>  
+
| <div id="Message_FieldComplete">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Field Complete</div>  
 
|-
 
|-
 
|  
 
|  
     The defaults that affect the inventory feature.
+
     When checked an automatic message will generate when jobs are changed to the Field Complete status.  
  
 
|-
 
|-
| <div id="ss_ShortDescSize">&nbsp;</div>  
+
| <div id="Message_AutoShow">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults: Short Desc Size</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Auto Show Messages</div>  
 
|-
 
|-
 
|  
 
|  
     The number of characters to use for the short description for items.
+
     When checked the message window will automatically display when users load the Dashboard. When not checked the use will have to click a button to open the messages window.
  
 
|-
 
|-
| <div id="ss_ShortDescSize">&nbsp;</div>  
+
| <div id="MLTE_Servicer">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults: Button: Update Item Short Descriptions</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Mobile Transaction Entry: Servicer</div>  
 
|-
 
|-
 
|  
 
|  
     When clicked the system will copy the first characters, based on the Short Desc Size field, to the Short Description field for all items. Warning! This cannot be reversed.
+
     The servicer that should be used when posting the transaction.
  
 
|-
 
|-
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
+
| <div id="model_Code">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Status Code Defaults</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Code</div>  
 
|-
 
|-
 
|  
 
|  
     Status codes are used to move jobs through the work flow processEach status code on this form has a purpose.  Assign a status code to each slot.  *These are required.
+
     The code used to identify the model.   
  
 
|-
 
|-
| <div id="ss_ed">&nbsp;</div>  
+
| <div id="model_Desc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Description</div>  
 
|-
 
|-
 
|  
 
|  
     Default values for new equipment records.  
+
     The description that identifies the model.
  
 
|-
 
|-
| <div id="sd_ed_warrantyBasedOn">&nbsp;</div>  
+
| <div id="model_prefix">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Warranty Based On</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Model: Prefix</div>  
 
|-
 
|-
 
|  
 
|  
     Warranties can be set based on the Sale Date or the installation date.
+
     The three digit prefix to use when auto-numbering new equipment records.
  
 
|-
 
|-
| <div id="sd_ed_allocationBasedOn">&nbsp;</div>  
+
| <div id="NoteCategory">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Allocation Based On</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Category</div>  
 
|-
 
|-
 
|  
 
|  
     General ledger allocations can be based on the inventory item, or the model.  
+
     Notes can be organized by category.
  
 
|-
 
|-
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
+
| <div id="NoteContent">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Auto No/EQ Defaults Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Content</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the system will automatically number new equipment records.
+
     The note content that will display on the form and print on any documents.
  
 
|-
 
|-
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
+
| <div id="NoteInternal">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Options</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Internal Note Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     Auto-numbering can be defined using a prefix or a matrix.  
+
     Internal notes do not print on invoices and dispatch cards.
  
 
|-
 
|-
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
+
| <div id="NotePrintOnTicket">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Prefix Missing Grid Column</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Note: Print Note on Ticket Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The number of records that do not contain a prefix for the matrix to work properly.
+
     When checked, the note will print on the dispatch card.
  
 
|-
 
|-
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
+
| <div id="PlannedMaintenanceType">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Type</div>  
 
|-
 
|-
 
|  
 
|  
     Defaults values for new sites.
+
     Planned maintenance types are used to organize schedules and establish default values.
  
 
|-
 
|-
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
+
| <div id="PlannedMaintenanceID">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Site Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: ID</div>  
 
|-
 
|-
 
|  
 
|  
     The default site type for new sites.
+
     The ID is used to identify the schedule.
  
 
|-
 
|-
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
+
| <div id="PlannedMaintenanceDescription">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Tax Schedule</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Description</div>  
 
|-
 
|-
 
|  
 
|  
     The default tax schedule for new sites. This value is only used if the tax schedule is not filled from the customer record.
+
     Descriptions can also help with identification.
  
 
|-
 
|-
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
+
| <div id="MaterialGroupCode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Use Customer Name and Address Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Material Group Code</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the customer’s name and address automatically fill the site form when adding a new site.
+
     Material Group Codes provide the ability to add materials to schedules by grouping.  
  
 
|-
 
|-
| <div id="ss_tad">&nbsp;</div>  
+
| <div id="PlannedMaintenanceTaskCode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Task Code</div>  
 
|-
 
|-
 
|  
 
|  
     The defaults and settings for new transactions.
+
     PM task codes are used to organize schedules and establish material group codes.
  
 
|-
 
|-
| <div id="ss_tad_Warehouse">&nbsp;</div>  
+
| <div id="Priority">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Warehouse</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority</div>  
 
|-
 
|-
 
|  
 
|  
     The warehouse to assign to any transaction for which a warehouse has not been assigned.
+
     The default priority that will be used when creating new jobs to establish schedule date and time.  Priorities are assigned to sites as a default for new jobs.  
  
 
|-
 
|-
| <div id="taxOnCustomer">&nbsp;</div>  
+
| <div id="PriorityCode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Tax on Customer Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Code</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, invoices will automatically use the customer's tax schedule.
+
     Priority codes are used to establish the response time when scheduling jobs.
  
 
|-
 
|-
| <div id="multiBranch">&nbsp;</div>  
+
| <div id="prio_dow">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Multi-branch Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Day of the Week</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the multi-branch feature becomes active and its rules applied.
+
     When checked, indicates that jobs can be scheduled on that day of the week.
  
 
|-
 
|-
| <div id="multiBranchSegment">&nbsp;</div>  
+
| <div id="prio_Desc">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Segment</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Description</div>  
 
|-
 
|-
 
|  
 
|  
     When the Multi-Branch checkbox is checked, this field becomes active. Use it to set the default branch segment to use when a branch segment is missing.
+
     Describe the priority.
  
 
|-
 
|-
| <div id="salesAcct">&nbsp;</div>  
+
| <div id="prio_endtime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Default Sales Account</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: End Time</div>  
 
|-
 
|-
 
|  
 
|  
     The sales account to assign to any transaction for which a sales account has not been assigned.
+
     Indicates the latest time a job can be scheduled on each day of the week.
  
 
|-
 
|-
| <div id="costAcct">&nbsp;</div>  
+
| <div id="ResponseTime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Default Cost Account</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Response Time</div>  
 
|-
 
|-
 
|  
 
|  
     The cost account to assign to any transaction for which a cost account has not been assigned.
+
     Indicates the number of hours between the received time and the scheduled time.  
  
 
|-
 
|-
| <div id="ss_inv">&nbsp;</div>  
+
| <div id="prio_SLA">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: SLA</div>  
 
|-
 
|-
 
|  
 
|  
     The defaults and settings for new transactions.
+
     When checked, indicates the priority is an SLA code. Only priority codes marked SLA will appear for jobs created on and SLA site.
  
 
|-
 
|-
| <div id="sd_Invoice_RequireSalesTax">&nbsp;</div>  
+
| <div id="prio_SLAExp">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Require Sales Tax Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: SLA Expiration</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, sales tax will be required on all invoices.
+
     The number of hours that are required to meet the SLA deadline.  
  
 
|-
 
|-
| <div id="sd_Invoice_Non">&nbsp;</div>  
+
| <div id="prio_starttime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Non-Tax Schedule</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Priority: Start Time</div>  
 
|-
 
|-
 
|  
 
|  
     Certin ERP system require a tax schedule on all invoices, even those that are non-tax.  This schedule fills that requirement.
+
     Indicated the earliest time a job can be scheduled on each day of the week.
  
 
|-
 
|-
| <div id="sd_Invoice_NextBatchNumber">&nbsp;</div>  
+
| <div id="QuotedDollars">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Next Batch Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Quoted Dollars</div>  
 
|-
 
|-
 
|  
 
|  
     The next batch to use when invoices are created automatically.
+
     The billing amount quoted for the job.  
  
 
|-
 
|-
| <div id="sd_Invoice_NextNumber">&nbsp;</div>  
+
| <div id="QuotedHours">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Next No</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Quoted Hours</div>  
 
|-
 
|-
 
|  
 
|  
     The next invoice number.
+
     The hours quoted for the job.    
  
 
|-
 
|-
| <div id="sd_Invoice_Length">&nbsp;</div>  
+
| <div id="PurchaseOrderNumber">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Length</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Purchase Order Number</div>  
 
|-
 
|-
 
|  
 
|  
     The invoice number lengthThis value cannot be shortened.
+
     The purchase order number issued by the customer for the work.   
  
 
|-
 
|-
| <div id="sd_Invoice_LeadingCharacters">&nbsp;</div>  
+
| <div id="ReportingGroups">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Leading Characters</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Reporting Groups</div>  
 
|-
 
|-
 
|  
 
|  
     The leading character for invoice numbers.  This is not required.
+
     A group code can be assigned to a miscellaneous charge code to group like Item codes.  
  
 
|-
 
|-
| <div id="sd_PM">&nbsp;</div>  
+
| <div id="corep_repaddress">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Address</div>  
 
|-
 
|-
 
|  
 
|  
     The defaults and settings for planned maintenance jobs.
+
     The mailing address for the representative.
  
 
|-
 
|-
| <div id="sd_PM_Priority">&nbsp;</div>  
+
| <div id="corep_city">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Priority</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: City</div>  
 
|-
 
|-
 
|  
 
|  
     The default priority for new planned maintenance jobs.
+
     The city for the mailing address
  
 
|-
 
|-
| <div id="sd_PM_StatusCode">&nbsp;</div>  
+
| <div id="corep_country">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Status Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Country</div>  
 
|-
 
|-
 
|  
 
|  
     The defaults status code for new planned maintenance jobs.
+
     The country for the mailing address.
  
 
|-
 
|-
| <div id="sd_PM_IncludeSiteinfoascomment">&nbsp;</div>  
+
| <div id="corep_repdivision">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Include Site info as comment</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Division</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the site information will appear on planned maintenance invoices.
+
     If division are in use, the representative division can be assigned.
  
 
|-
 
|-
| <div id="sd_PM_IncludeEquipmentinfoascomment">&nbsp;</div>  
+
| <div id="corep_repemail">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Include Equipment info as comment</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Email</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the equipment information will appear on planned maintenance invoices.
+
     The email address can be used to contact the representative.
  
 
|-
 
|-
| <div id="sd_AG">&nbsp;</div>  
+
| <div id="corep_repname">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Name</div>  
 
|-
 
|-
| The settings and defaults for new agreements.
+
|  
 +
    The name of the representative.
 +
 
 
|-
 
|-
| <div id="sd_AG_AutoNo">&nbsp;</div>  
+
| <div id="corep_repno">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Auto No Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Number</div>  
 
|-
 
|-
| When checked, the system will automatically number any agreements that are created using an agreement type that is not also set to auto number.
+
|  
 +
    The representative number can be used to recognize a representative.
 +
 
 
|-
 
|-
| <div id="sd_AG_AgreementNoLength">&nbsp;</div>  
+
| <div id="corep_repphone">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Next Agreement No</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Phone</div>  
 
|-
 
|-
| The next number that will be used when creating agreements.
+
|  
 +
    The telephone number can be used to contact the representative.
 +
 
 
|-
 
|-
| <div id="sd_AG_AgreementNoLength">&nbsp;</div>  
+
| <div id="corep_state">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreeement No Length</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: State</div>  
 
|-
 
|-
| The maximum length of the agreement numbers.
+
|  
 +
    The mailing address state.
 +
 
 
|-
 
|-
| <div id="sd_AG_AgreementNoLength">&nbsp;</div>  
+
| <div id="corep_reptype">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Default Agreement Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Type</div>  
 
|-
 
|-
| The agreement type that will be automatically assigned to new agreements.
+
|  
 +
    Types are used to organize representatives.
 +
 
 
|-
 
|-
| <div id="sd_AG_PB_autoProcess">&nbsp;</div>  
+
| <div id="corep_zip">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Planned Billing Auto Process Checkbox</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Representative: Zip</div>  
 
|-
 
|-
| When checked, the planned billing nightly auto-processing feature is active.
+
|  
 +
    The postal code for the mailing address.
 +
 
 
|-
 
|-
| <div id="sd_AG_PB_ProcessingDate">&nbsp;</div>  
+
| <div id="job_request">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Processing Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Request</div>  
 
|-
 
|-
| Indicates the date to use when processing planned billing.
+
|  
 +
    Requests are defined using the Request Management feature. The request defines the work requested.
 +
 
 
|-
 
|-
| <div id="sd_AG_DR_autoProcess">&nbsp;</div>  
+
| <div id="job_requestnote">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Deferred Revenue Auto Process</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Request Notes</div>  
 
|-
 
|-
| When checked, the deferred revenues nightly auto-renewal feature is active.
+
|  
 +
    Request notes are used to further define the work requested.
 +
 
 
|-
 
|-
| <div id="sd_AG_AR_autoProcess">&nbsp;</div>  
+
| <div id="costtype_RevAcct">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Renewals Auto Process</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue Account</div>  
 
|-
 
|-
| When checked, the planned billing nightly auto-renewal feature is active.
+
|  
 +
    The sales account that will be assigned to transactions that match the job type and cost type.  
 +
 
 
|-
 
|-
| <div id="sd_AG_AR_IncludeSiteDetailsascomment">&nbsp;</div>  
+
| <div id="costtype_RevSubacct">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Site Details on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Revenue subaccount</div>  
 
|-
 
|-
| When checked, the site details will appear on the invoices.
+
|  
 +
    The sales sub-account that will be assigned to transactions that match the job type and cost type.
 +
 
 
|-
 
|-
| <div id="sd_AG_AR_IncludeEquipDetailsascomment">&nbsp;</div>  
+
| <div id="rolemanagement">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements:Agreement Type PRO Include Equipment Details on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Role Management</div>  
 
|-
 
|-
| When checked, the equipment details will appear on the invoices.
+
|  
 +
    User roles provide access to assigned forms while restricting access to unassigned forms.  
 +
 
 
|-
 
|-
| <div id="sd_AG_AR_IncludeSiteSummaryascomment">&nbsp;</div>  
+
| <div id="job_scheduledate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Site Summary on Invoice</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Date</div>  
 
|-
 
|-
| When checked, the site summary information will appear on the invoices.
+
|  
 +
    The date the technician is scheduled to do the work.
 +
 
 
|-
 
|-
| <div id="sd_AG_AR_IncludeEquipSummaryascomment">&nbsp;</div>  
+
| <div id="job_scheduletime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, AgreementsAgreement Type PRO Include Equipment Summary on Invoice:</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Schedule Time</div>  
 
|-
 
|-
| When checked, the equipment summary information will appear on the invoices.
+
|  
 +
    The time the technician is scheduled to do the work.
 +
 
 
|-
 
|-
| <div id="sd_AG_ALL_DefRevAccount">&nbsp;</div>  
+
| <div id="scheduleTime_ReasonCode">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Revenue Account</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: Reason Code</div>  
 
|-
 
|-
| The default revenue account that will be assigned to new allocations.
+
|  
 +
    Describe the reason the servicer is not available for work.
 +
 
 
|-
 
|-
| <div id="sd_AG_ALL_DefRevAccount">&nbsp;</div>  
+
| <div id="scheduleTime_startdate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Deferred Revenue Account</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: Start Date</div>  
 
|-
 
|-
| The default deferred revenue account that will be assigned to new allocations.
+
|  
 +
    The first date for the time off schedule.
 +
 
 
|-
 
|-
| <div id="Item">&nbsp;</div>  
+
| <div id="scheduleTime_enddate">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Item</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: End Date</div>  
 
|-
 
|-
| Desc here: The default item that will be assigned to new allocations.
+
|  
 +
    The last date for the time off schedule.
 +
 
 
|-
 
|-
| <div id="servicetype">&nbsp;</div>  
+
| <div id="scheduleTime_starttime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: Start Time</div>  
 
|-
 
|-
 
|  
 
|  
     Service Types are used to organize jobs using a job type, service type relationship.
+
     The starting time for the scheduled time off. If the scheduled time off spans dates and the replicate time option is not used, this date will be the start of the day for all dates except the first date.  
  
 
|-
 
|-
| <div id="servicetype_Code">&nbsp;</div>  
+
| <div id="scheduleTime_endtime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: End Time</div>  
 
|-
 
|-
 
|  
 
|  
     Used to identify the service type.
+
     The End time for the scheduled time off. If the scheduled time off spans dates and the replicate time option is not used, this date will be the end of the day for all dates except the last date.  
  
 
|-
 
|-
| <div id="servicetype_Desc">&nbsp;</div>  
+
| <div id="scheduleTime_replicatetime">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Desc</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Scheduling: Replicate Time</div>  
 
|-
 
|-
 
|  
 
|  
     Used to describe the service type.
+
     The replicate time option is used for date spans.  When checked the time on each day will match the start and end times in the fields.  If not, the first day will use the start time, the last day will use the end time and all days in between will display 24 hours of time.
  
 
|-
 
|-
| <div id="site_Address">&nbsp;</div>  
+
| <div id="job_sendtomobile">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Address</div>  
+
| <div class="fieldHeader">Send to Mobile Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The physical address for the site.  This field is used in dispatching.
+
     On save, if this checkbox is checked, the job will be made available in mobile.  
  
 
|-
 
|-
| <div id="site_Branch">&nbsp;</div>  
+
| <div id="servicer_Number">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Branch</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer</div>  
 
|-
 
|-
 
|  
 
|  
     The site branch is required if multi-branching is in use.
+
     The technician that will perform the work.
  
 
|-
 
|-
| <div id="site_Chain">&nbsp;</div>  
+
| <div id="servicer_Number">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Chain</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Number</div>  
 
|-
 
|-
 
|  
 
|  
     The site's chain.  Chains are not required.
+
     The number used to identify the technician.
  
 
|-
 
|-
| <div id="site_City">&nbsp;</div>  
+
| <div id="servicer_employee">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: City</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Employee Number</div>  
 
|-
 
|-
 
|  
 
|  
     The address city for the site.  This field is used in dispatching.
+
     If the servicer is also an employee, the employee number can be stored in this field.  
  
 
|-
 
|-
| <div id="site_CloneAddress">&nbsp;</div>  
+
| <div id="servicer_subcontractor">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Customer Address</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Subcontractor Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     When clicked, this button will clone the customer's address to the site.
+
     When checked, indicates that the servicer is a contracted employee or vendor.
  
 
|-
 
|-
| <div id="site_CloneShipTo">&nbsp;</div>  
+
| <div id="svr_Name">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Ship To</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Name</div>  
 
|-
 
|-
 
|  
 
|  
     When an item is selected, the ship to address will be copied to the site address fields.
+
     The name of the technician.
  
 
|-
 
|-
| <div id="site_Code">&nbsp;</div>  
+
| <div id="svr_Vendor">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Vendor</div>  
 
|-
 
|-
 
|  
 
|  
     The site code can be used to identify the site. It is not required.
+
     This field is used when the servicer is a vendor. The vendor is selected from the list and other vendor fields become available for use.
  
 
|-
 
|-
| <div id="site_EST">&nbsp;</div>  
+
| <div id="svr_Address">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Established Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Address</div>  
 
|-
 
|-
 
|  
 
|  
     The date the site was added.
+
     The technician's mailing address.
  
 
|-
 
|-
| <div id="site_Fax">&nbsp;</div>  
+
| <div id="svr_BillingRate">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Fax Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Billing Rate</div>  
 
|-
 
|-
 
|  
 
|  
     The site's Fax number.  
+
     The technicians hourly labor billing rate.
  
 
|-
 
|-
| <div id="site_Labor1">&nbsp;</div>  
+
| <div id="svr_PORequired">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Labor #1</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: PO Required Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the first button.
+
     When checked, the vendor requires a purchase order for all requested work.
  
 
|-
 
|-
| <div id="site_Labor2">&nbsp;</div>  
+
| <div id="svr_HrlyCost">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Labor #2</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Hourly Cost</div>  
 
|-
 
|-
 
|  
 
|  
     Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the second button.
+
     The hourly cost for the technician.
  
 
|-
 
|-
| <div id="site_Lat">&nbsp;</div>  
+
| <div id="svr_InsCert">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Latitude</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Insurance Certificate on File Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The latitude for the site location.  
+
     For use with vendors or contract employees only. Indicates that a Certificate of Insurance is on file.
  
 
|-
 
|-
| <div id="site_Long">&nbsp;</div>  
+
| <div id="svr_burden">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Longitude</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Burden</div>  
 
|-
 
|-
 
|  
 
|  
     The longitude for the site location.
+
     The hourly burden for the technician.  
  
 
|-
 
|-
| <div id="site_MainNo">&nbsp;</div>  
+
| <div id="svr_certFile">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Main Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Certificate File Name</div>  
 
|-
 
|-
 
|  
 
|  
     The main business contact telephone number for the site.
+
     The file name for the Certificate of Insurance.
  
 
|-
 
|-
| <div id="site_MapCode">&nbsp;</div>  
+
| <div id="svr_city">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Map Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: City</div>  
 
|-
 
|-
 
|  
 
|  
     When using Key Maps or Rand McNally's Street Finders this will be the code to associate the location with a particular map page.
+
     The servicer's mailing address city.
  
 
|-
 
|-
| <div id="site_Name">&nbsp;</div>  
+
| <div id="svr_warehouse">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Name</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Warehouse</div>  
 
|-
 
|-
 
|  
 
|  
     The name of the site location. This is used to identify the site.
+
     The servicer's default warehouse.
  
 
|-
 
|-
| <div id="site_PriceLevels">&nbsp;</div>  
+
| <div id="svr_terms">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Price Level</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Terms</div>  
 
|-
 
|-
 
|  
 
|  
     The price level that should be used when billing jobs.
+
     If the servicer is a vendor or contract employee, the terms for payment.  
  
 
|-
 
|-
| <div id="site_PContact">&nbsp;</div>  
+
| <div id="svr_State">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Primary Contact</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: State</div>  
 
|-
 
|-
 
|  
 
|  
     The site's primary contact.  Contacts are management using the Contact Management system.  
+
     The servicer's mailing address state.
  
 
|-
 
|-
| <div id="site_Referral">&nbsp;</div>  
+
| <div id="svr_Zip">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Referral Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Zip</div>  
 
|-
 
|-
 
|  
 
|  
     The site's referral code.  Referral codes are not required.
+
     The servicer's mailing address postal code.
  
 
|-
 
|-
| <div id="site_Servicer1">&nbsp;</div>  
+
| <div id="svr_Email">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Servicer #1</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Email</div>  
 
|-
 
|-
 
|  
 
|  
     The default primary servicer. New jobs will be automatically assigned to this servicer. 
+
     The servicer's email address.
  
 
|-
 
|-
| <div id="site_Servicer2">&nbsp;</div>  
+
| <div id="svr_Mobile">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Servicer #2</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Mobile Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The secondary servicer for new jobs.
+
     When checked, the servicer's jobs will appear on the mobile board.
  
 
|-
 
|-
| <div id="site_SLA">&nbsp;</div>  
+
| <div id="svr_country">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: SLA</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Country</div>  
 
|-
 
|-
 
|  
 
|  
     When checked, the site qualifies for SLA service.
+
     The servicer's mailing address country
  
 
|-
 
|-
| <div id="site_State">&nbsp;</div>  
+
| <div id="svr_estDate">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: State</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Established Date</div>  
 
|-
 
|-
 
|  
 
|  
     The address state code for the site.  This field is used in dispatching.
+
     The date the servicer relationship was established.
  
 
|-
 
|-
| <div id="site_StoreNo">&nbsp;</div>  
+
| <div id="svr_userList">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Store Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: User List</div>  
 
|-
 
|-
 
|  
 
|  
     The store number for the siteThe store number is directly tied to the Chains feature.
+
     Servicers must be assigned to a user login before the user can use the mobile system.   
   
 
  
 
|-
 
|-
| <div id="site_StoreType">&nbsp;</div>  
+
| <div id="svr_phone">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Store Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Phone</div>  
 
|-
 
|-
 
|  
 
|  
     The store type for the site.  The store number is directly tied to the Chains feature.  
+
     The telephone number for contacting the servicer.
  
 
|-
 
|-
| <div id="site_Type">&nbsp;</div>  
+
| <div id="svr_imgFile">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Servicer Image File</div>  
 
|-
 
|-
 
|  
 
|  
     Site types are used to organize sites. Site types are not required.  
+
     The name of the file that contains an image of the technician.
  
 
|-
 
|-
| <div id="site_Zip">&nbsp;</div>  
+
| <div id="svr_dispatchBatch">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Site: Zip Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Service Dispatch Batch</div>  
 
|-
 
|-
 
|  
 
|  
     The address postal code for the site.  This field is used in dispatching.
+
     Mobile jobs can be grouped by batch for posting to the back office.  
  
 
|-
 
|-
| <div id="sitetype_Code">&nbsp;</div>  
+
| <div id="svr_tomtom">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: Tom Tom ID</div>  
 
|-
 
|-
 
|  
 
|  
     Sites can be grouped by site type.
+
     The Tom Tom ID for the servicer.
  
 
|-
 
|-
| <div id="sitetype_Code">&nbsp;</div>  
+
| <div id="svr_userMapPin">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Code</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Servicer: User Map Pin</div>  
 
|-
 
|-
 
|  
 
|  
     The code used to identify the site type.
+
     Technicians can be mapped using pins.
  
 
|-
 
|-
| <div id="sitetype_Desc">&nbsp;</div>  
+
| <div id="svr_userMapPin">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Description</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults: New Job Defaults</div>  
 
|-
 
|-
 
|  
 
|  
     The description used to identify the site type.
+
     The values that will be used by default when adding new jobs.  Some of these values can be changed at the job level.  
 +
        [[Glossary#job_request|Request]]
 +
        [[Glossary#ss_OverrideJobNo|Override Job No]]
 +
        [[Glossary#ss_SendJobEmail|Send Job Email]]
 +
        [[Glossary#jobType|Job Type]]
 +
        [[Glossary#servicetype|Service Type]]
 +
        [[Glossary#Priority|Priority]]
 +
        [[Glossary#estHours|Est Hours]]
 +
        [[Glossary#ss_JobNextNo|Job Next No]]
 +
        [[Glossary#ss_JobLength|Job Length]]
 +
        [[Glossary#ss_JobLeadingCharacters|Job Leading Characters]]
  
 
|-
 
|-
| <div id="sitetype_Message">&nbsp;</div>  
+
| <div id="ss_OverrideJobNo">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Message</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Override Job No Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The message of the Service Site Type will default into the field or manually type a customer note into the field. If the Service Site Type is changed the message will not change.
+
     When checked, users are allowed to alter the job number. Warning! This could interrupt the job numbering system.
  
 
|-
 
|-
| <div id="job_solution">&nbsp;</div>  
+
| <div id="ss_SendJobEmail">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Send Job Email Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     Solutions are defined using the Solution Management feature.  The solution defines the work done to complete the work.
+
     When checked, the send email form will be displayed when a new job is saved.
  
 
|-
 
|-
| <div id="job_solutionnotes">&nbsp;</div>  
+
| <div id="ss_EstHours">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution Notes</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Est Hours</div>  
 
|-
 
|-
 
|  
 
|  
     Solution notes are used to further define the work performed.
+
     The hours estimated to complete the job. This value will be added to the primary work order.
  
 
|-
 
|-
| <div id="Subclass">&nbsp;</div>  
+
| <div id="ss_JobNextNo">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Subclass</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Next No</div>  
 
|-
 
|-
 
|  
 
|  
     The sub-classification is used in sales and cost account assignments.  
+
     The number that will be assigned to the next job.  
  
 
|-
 
|-
| <div id="TaskType">&nbsp;</div>  
+
| <div id="ss_JobLength">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Length</div>  
 
|-
 
|-
| Tasks can be organized by type.
+
|  
 +
    The number of characters in the job number.
 +
 
 
|-
 
|-
| <div id="TaskStatus">&nbsp;</div>  
+
| <div id="ss_JobLeadingCharacters">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Status</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, New Job Defaults: Job Leading Characters</div>  
 
|-
 
|-
| Tasks can be tracked by status.
+
|  
 +
    The character(s) that will lead the job number. Leading characters are not required.
 +
 
 
|-
 
|-
| <div id="TaskDetails">&nbsp;</div>  
+
| <div id="ss_ShortDescSize">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Details</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults</div>  
 
|-
 
|-
| Task details provide a description of the task.
+
|  
 +
    The defaults that affect the inventory feature.
 +
 
 
|-
 
|-
| <div id="TaskURL">&nbsp;</div>  
+
| <div id="ss_ShortDescSize">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: URL</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults: Short Desc Size</div>  
 
|-
 
|-
| The URL field is used to store the website related to the task.
+
|  
 +
    The number of characters to use for the short description for items. This can be changed, and the software will adjust the values of the field.
 +
 
 
|-
 
|-
| <div id="TaskNotes">&nbsp;</div>  
+
| <div id="ss_ShortDescSize">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Notes</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Inventory Defaults: Button: Update Item Short Descriptions</div>  
 
|-
 
|-
| Notes can be stored for each task.
+
|  
 +
    When clicked the system will copy the first characters, based on the Short Desc Size field, to the Short Description field for all items. Warning! This cannot be reversed.
 +
 
 
|-
 
|-
| <div id="TaskDueDate">&nbsp;</div>  
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Due Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Status Code Defaults</div>  
 
|-
 
|-
| Task can be tracked by due date.
+
|  
 +
    Status codes are used to move jobs through the workflow process. Each status code on this form has a purpose.  Assign a status code to each slot.  *These are required.
 +
 
 
|-
 
|-
| <div id="TaskDueTime">&nbsp;</div>  
+
| <div id="ss_ed">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Due Time</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults</div>  
 
|-
 
|-
| Task can be tracked by due time.
+
|  
 +
    Default values for new equipment records.  
 +
 
 
|-
 
|-
| <div id="TaskAssignmentType">&nbsp;</div>  
+
| <div id="sd_ed_warrantyBasedOn">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Assignment Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Warranty Based On</div>  
 
|-
 
|-
| Tasks can be assigned to individual by type.  
+
|  
        Account Manager
+
    Warranties can be set based on the Sale Date or the installation date.
        Salesperson
+
 
        Servicer
 
        User
 
 
 
 
|-
 
|-
| <div id="TaskAssignedTo">&nbsp;</div>  
+
| <div id="sd_ed_allocationBasedOn">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Assigned To</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Allocation Based On</div>  
 
|-
 
|-
| The individual that will handle the task.
+
|  
 +
    General ledger allocations can be based on the inventory item, or the model.  
 +
 
 
|-
 
|-
| <div id="TaskEmail">&nbsp;</div>  
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Email</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Auto No/EQ Defaults Checkbox</div>  
 
|-
 
|-
| An email can be stored with the task.
+
|  
 +
    When checked, the system will automatically number new equipment records.
 +
 
 
|-
 
|-
| <div id="TaskTextPhone">&nbsp;</div>  
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Text Phone</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Options</div>  
 
|-
 
|-
| A telephone number for texting can be stored with the task.
+
|  
 +
    Auto-numbering can be defined using a prefix or a matrix.
 +
    Prefix: The prefix option will create the number using the equipment prefix followed by the next number.
 +
    Matrix: The matrix option allows the user to establish a prefix order from the prefixes assigned to the equipment types, manufacturers and models.
 +
 
 
|-
 
|-
| <div id="TaxClass">&nbsp;</div>  
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
 
|-
 
|-
| <div class="fieldHeader">Tax Class</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Equipment Defaults: Prefix Missing Grid Column</div>  
 
|-
 
|-
 
|  
 
|  
     The item's task class.
+
     The number of records that do not contain a prefix for the matrix to work properly.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customertaxexemptno">&nbsp;</div>  
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Exempt Number</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults</div>  
 
|-
 
|-
 
|  
 
|  
     If the customer is tax exempt, a value must be used in this field.
+
     Defaults values for new sites.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customertaxschedule">&nbsp;</div>  
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Schedule</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Site Type</div>
 +
|-
 +
|
 +
    The default site type for new sites.
 +
 
 +
|-
 +
| <div id="ss_SiteCodeDefaults">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Tax Schedule</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's tax schedule. This information is assigned at the ERP level and cannot be altered when an ERP is in use.
+
     The default tax schedule for new sites. This value is only used if the tax schedule is not filled from the customer record.
  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div id="customerterms">&nbsp;</div>  
+
| <div id="ss_SiteCodeDefaults">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Terms</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Site Defaults: Use Customer Name and Address Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The customer's terms.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
+
     When checked, the customer’s name and address automatically fill in the site form when adding a new site.
  
 
|-
 
|-
| <div id="TransactionBilledStatus">&nbsp;</div>  
+
| <div id="ss_tad">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction Billed Status</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments</div>  
 
|-
 
|-
| Indicates the transaction's position in the billing process.  
+
|  
        N = Not billed
+
    The defaults and settings for new transactions.
        I = On an unposted invoice
 
        Y = On a posted invoice
 
  
 
|-
 
|-
| <div id="TransactionDate">&nbsp;</div>  
+
| <div id="ss_tad_Warehouse">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction Date</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Warehouse</div>  
 
|-
 
|-
| The date the transaction will post to the general ledger.
+
|  
 +
    The warehouse to assign to any transaction for which a warehouse has not been assigned.
 +
 
 
|-
 
|-
| <div id="TransactionType">&nbsp;</div>  
+
| <div id="taxOnCustomer">&nbsp;</div>  
 
|-
 
|-
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction Type</div>  
+
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Tax on Customer Checkbox</div>  
 
|-
 
|-
 
|  
 
|  
     The type of transaction.  The type is used to group the transactions by labor, materials or purchases.
+
     When checked, invoices will automatically use the customer's tax schedule.
  
 +
|-
 +
| <div id="multiBranch">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Multi-branch Checkbox</div>
 +
|-
 +
|
 +
    When checked, the multi-branch feature becomes active, and its rules applied.
 +
 +
|-
 +
| <div id="multiBranchSegment">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Segment</div>
 +
|-
 +
|
 +
    When the Multi-Branch checkbox is checked, this field becomes active. Use it to set the default branch segment to use when a branch segment is missing.
 +
 +
|-
 +
| <div id="salesAcct">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Default Sales Account</div>
 +
|-
 +
|
 +
    The sales account to assign to any transaction for which a sales account has not been assigned. 
 +
 +
|-
 +
| <div id="costAcct">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Transaction Assignments: Default Cost Account</div>
 +
|-
 +
|
 +
    The cost account to assign to any transaction for which a cost account has not been assigned. 
 +
 +
|-
 +
| <div id="ss_inv">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing</div>
 +
|-
 +
|
 +
    The defaults and settings for new transactions.
 +
 +
|-
 +
| <div id="sd_Invoice_RequireSalesTax">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Require Sales Tax Checkbox</div>
 +
|-
 +
|
 +
    When checked, sales tax will be required on all invoices.
 +
 +
|-
 +
| <div id="sd_Invoice_Non">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Non-Tax Schedule</div>
 +
|-
 +
|
 +
    Certain ERP system require a tax schedule on all invoices, even those that are non-tax.  This schedule fills that requirement.
 +
 +
|-
 +
| <div id="sd_Invoice_NextBatchNumber">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Next Batch Number</div>
 +
|-
 +
|
 +
    The next batch to use when invoices are created automatically.
 +
 +
|-
 +
| <div id="sd_Invoice_NextNumber">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Next No</div>
 +
|-
 +
|
 +
    The next invoice number.
 +
 +
|-
 +
| <div id="sd_Invoice_Length">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Length</div>
 +
|-
 +
|
 +
    The invoice number length.  This value cannot be shortened.
 +
 +
|-
 +
| <div id="sd_Invoice_LeadingCharacters">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Invoicing: Leading Characters</div>
 +
|-
 +
|
 +
    The leading character for invoice numbers.  Leading characters are not required.
 +
 +
|-
 +
| <div id="sd_PM">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance</div>
 +
|-
 +
|
 +
    The defaults and settings for planned maintenance jobs.
 +
 +
|-
 +
| <div id="sd_PM_Priority">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Priority</div>
 +
|-
 +
|
 +
    The default priority for new planned maintenance jobs.
 +
 +
|-
 +
| <div id="sd_PM_StatusCode">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Status Code</div>
 +
|-
 +
|
 +
    The defaults status code for new planned maintenance jobs.
 +
 +
|-
 +
| <div id="sd_PM_IncludeSiteinfoascomment">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Include Site info as comment</div>
 +
|-
 +
|
 +
    When checked, the site information will appear on planned maintenance invoices.
 +
 +
|-
 +
| <div id="sd_PM_IncludeEquipmentinfoascomment">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Planned Maintenance: Include Equipment info as comment</div>
 +
|-
 +
|
 +
    When checked, the equipment information will appear on planned maintenance invoices.
 +
 +
|-
 +
| <div id="sd_AG">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements</div>
 +
|-
 +
|
 +
    The settings and defaults for new agreements.
 +
 +
|-
 +
| <div id="sd_AG_AutoNo">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Auto No Checkbox</div>
 +
|-
 +
|
 +
    When checked, the system will automatically number any agreements that are created using an agreement type that is not also set to auto number.
 +
 +
|-
 +
| <div id="sd_AG_AgreementNoLength">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Next Agreement No</div>
 +
|-
 +
|
 +
    The next number that will be used when creating agreements.
 +
 +
|-
 +
| <div id="sd_AG_AgreementNoLength">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement No Length</div>
 +
|-
 +
|
 +
    The maximum length of the agreement numbers.
 +
 +
|-
 +
| <div id="sd_AG_AgreementNoLength">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Default Agreement Type</div>
 +
|-
 +
|
 +
    The agreement type that will be automatically assigned to new agreements.
 +
 +
|-
 +
| <div id="sd_AG_PB_autoProcess">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Planned Billing Auto Process Checkbox</div>
 +
|-
 +
|
 +
    When checked, the planned billing nightly auto-processing feature is active.
 +
 +
|-
 +
| <div id="sd_AG_PB_ProcessingDate">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Processing Date</div>
 +
|-
 +
|
 +
    Indicates the date to use when processing planned billing. 
 +
 +
|-
 +
| <div id="sd_AG_DR_autoProcess">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Deferred Revenue Auto Process</div>
 +
|-
 +
|
 +
    When checked, the deferred revenues nightly auto-renewal feature is active.
 +
 +
|-
 +
| <div id="sd_AG_AR_autoProcess">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Renewals Auto Process</div>
 +
|-
 +
|
 +
    When checked, the planned billing nightly auto-renewal feature is active.
 +
 +
|-
 +
| <div id="sd_AG_AR_IncludeSiteDetailsascomment">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Site Details on Invoice</div>
 +
|-
 +
|
 +
    When checked, the site details will appear on the invoices.
 +
 +
|-
 +
| <div id="sd_AG_AR_IncludeEquipDetailsascomment">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Equipment Details on Invoice</div>
 +
|-
 +
|
 +
    When checked, the equipment details will appear on the invoices.
 +
 +
|-
 +
| <div id="sd_AG_AR_IncludeSiteSummaryascomment">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Site Summary on Invoice</div>
 +
|-
 +
|
 +
    When checked, the site summary information will appear on the invoices.
 +
 +
|-
 +
| <div id="sd_AG_AR_IncludeEquipSummaryascomment">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Agreement Type PRO Include Equipment Summary on Invoice:</div>
 +
|-
 +
|
 +
    When checked, the equipment summary information will appear on the invoices.
 +
 +
|-
 +
| <div id="sd_AG_ALL_DefRevAccount">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Revenue Account</div>
 +
|-
 +
|
 +
    The default revenue account that will be assigned to new allocations.
 +
 +
|-
 +
| <div id="sd_AG_ALL_DefRevAccount">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Deferred Revenue Account</div>
 +
|-
 +
|
 +
    The default deferred revenue account that will be assigned to new allocations.
 +
 +
|-
 +
| <div id="Item">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Software Defaults, Agreements: Item</div>
 +
|-
 +
|
 +
    The default item that will be assigned to new allocations.
 +
 +
|-
 +
| <div id="servicetype">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type</div>
 +
|-
 +
|
 +
    Service Types are used to organize jobs using a job type, service type relationship.
 +
 +
|-
 +
| <div id="servicetype_Code">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Code</div>
 +
|-
 +
|
 +
    Used to identify the service type.
 +
 +
|-
 +
| <div id="servicetype_Desc">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Service Type: Desc</div>
 +
|-
 +
|
 +
    Used to describe the service type.
 +
 +
|-
 +
| <div id="site_Address">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Address</div>
 +
|-
 +
|
 +
    The physical address for the site.  This field is used in dispatching.
 +
 +
|-
 +
| <div id="site_Branch">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Branch</div>
 +
|-
 +
|
 +
    The site branch is required if multi-branching is in use.
 +
 +
|-
 +
| <div id="site_Chain">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Chain</div>
 +
|-
 +
|
 +
    The site's chain.  Chains are not required.
 +
 +
|-
 +
| <div id="site_City">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: City</div>
 +
|-
 +
|
 +
    The address city for the site.  This field is used in dispatching.
 +
 +
|-
 +
| <div id="site_CloneAddress">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Customer Address</div>
 +
|-
 +
|
 +
    When clicked, this button will clone the customer's address to the site.
 +
 +
|-
 +
| <div id="site_CloneShipTo">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Clone From Ship To</div>
 +
|-
 +
|
 +
    When an item is selected, the ship to address will be copied to the site address fields.
 +
 +
|-
 +
| <div id="site_Code">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site: Code</div>
 +
|-
 +
|
 +
    The site code can be used to identify the site.  It is not required.
 +
 +
|-
 +
| <div id="site_EST">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Established Date</div>
 +
|-
 +
|
 +
    The date the site was added.
 +
 +
|-
 +
| <div id="site_Fax">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Fax Number</div>
 +
|-
 +
|
 +
    The site's Fax number.
 +
 +
|-
 +
| <div id="site_Labor1">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Labor #1</div>
 +
|-
 +
|
 +
    Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the first button.
 +
 +
|-
 +
| <div id="site_Labor2">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Labor #2</div>
 +
|-
 +
|
 +
    Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the second button.
 +
 +
|-
 +
| <div id="site_Lat">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Latitude</div>
 +
|-
 +
|
 +
    The latitude for the site location.
 +
 +
|-
 +
| <div id="site_Long">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Longitude</div>
 +
|-
 +
|
 +
    The longitude for the site location.
 +
 +
|-
 +
| <div id="site_MainNo">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Main Number</div>
 +
|-
 +
|
 +
    The main business contact telephone number for the site.
 +
 +
|-
 +
| <div id="site_MapCode">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Map Code</div>
 +
|-
 +
|
 +
    When using Key Maps or Rand McNally's Street Finders this will be the code to associate the location with a particular map page.
 +
 +
|-
 +
| <div id="site_Name">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Name</div>
 +
|-
 +
|
 +
    The name of the site location. This is used to identify the site.
 +
 +
|-
 +
| <div id="site_PriceLevels">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Price Level</div>
 +
|-
 +
|
 +
    The price level that should be used when billing jobs.
 +
 +
|-
 +
| <div id="site_PContact">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Primary Contact</div>
 +
|-
 +
|
 +
    The site's primary contact.  Contacts are managed using the Contact Management system.
 +
 +
|-
 +
| <div id="site_Referral">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Referral Code</div>
 +
|-
 +
|
 +
    The site's referral code.  Referral codes are not required.
 +
 +
|-
 +
| <div id="site_Servicer1">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Servicer #1</div>
 +
|-
 +
|
 +
    The default primary servicer.  New jobs will be automatically assigned to this servicer. 
 +
 +
|-
 +
| <div id="site_Servicer2">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Servicer #2</div>
 +
|-
 +
|
 +
    The secondary servicer for new jobs.
 +
 +
|-
 +
| <div id="site_SLA">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: SLA</div>
 +
|-
 +
|
 +
    When checked, the site qualifies for SLA service.
 +
 +
|-
 +
| <div id="site_State">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: State</div>
 +
|-
 +
|
 +
    The address state code for the site.  This field is used in dispatching.
 +
 +
|-
 +
| <div id="site_StoreNo">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Store Number</div>
 +
|-
 +
|
 +
    The store number for the site.  The store number is directly tied to the Chains feature.
 +
   
 +
 +
|-
 +
| <div id="site_StoreType">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Store Type</div>
 +
|-
 +
|
 +
    The store type for the site.  The store number is directly tied to the Chains feature.
 +
 +
|-
 +
| <div id="site_Type">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Type</div>
 +
|-
 +
|
 +
    Site types are used to organize sites. Site types are not required.
 +
 +
|-
 +
| <div id="site_Zip">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Site: Zip Code</div>
 +
|-
 +
|
 +
    The address postal code for the site.  This field is used in dispatching.
 +
 +
|-
 +
| <div id="sitetype_Code">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type</div>
 +
|-
 +
|
 +
    Sites can be grouped by site type.
 +
 +
|-
 +
| <div id="sitetype_Code">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Code</div>
 +
|-
 +
|
 +
    The code used to identify the site type.
 +
 +
|-
 +
| <div id="sitetype_Desc">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Description</div>
 +
|-
 +
|
 +
    The description used to identify the site type.
 +
 +
|-
 +
| <div id="sitetype_Message">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Site Type: Message</div>
 +
|-
 +
|
 +
    The message of the Service Site Type will default into the field or manually type a customer note into the field. If the Service Site Type is changed the message will not change.
 +
 +
|-
 +
| <div id="job_solution">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution</div>
 +
|-
 +
|
 +
    Solutions are defined using the Solution Management feature.  The solution defines the work done to complete the work.
 +
 +
|-
 +
| <div id="job_solutionnotes">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Solution Notes</div>
 +
|-
 +
|
 +
    Solution notes are used to further define the work performed.
 +
 +
|-
 +
| <div id="statuscode_code">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: Code</div>
 +
|-
 +
|
 +
    The code used to identify the status code.
 +
 +
|-
 +
| <div id="statuscode_Desc">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: Description</div>
 +
|-
 +
|
 +
    The description used to identify the status code.
 +
 +
|-
 +
| <div id="statuscode_KPI">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: KPI</div>
 +
|-
 +
|
 +
    When marked the status code will be included in KPI counts.
 +
 +
|-
 +
| <div id="statuscode_InProcess">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: In Process</div>
 +
|-
 +
|
 +
    When marked the jobs assigned to this status code will be considered to be in process.  In process status codes do not appear in the status code list for new jobs.
 +
 +
&nbsp;
 +
 +
|-
 +
| <div id="statuscode_AllowInvoicing">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: Allow Invoicing</div>
 +
|-
 +
|
 +
    Invoicing is only allowed for jobs where the Allow Invoicing is checked.
 +
 +
&nbsp;
 +
 +
|-
 +
| <div id="statuscode_All">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Status Codes: All</div>
 +
|-
 +
|
 +
    Used for the search option.  When checked all status code records will be displayed during a search.
 +
 +
|-
 +
| <div id="Subclass">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Subclass</div>
 +
|-
 +
|
 +
    The sub-classification is used in sales and cost account assignments.
 +
 +
|-
 +
| <div id="TaskType">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Type</div>
 +
|-
 +
|
 +
    Tasks can be organized by type.
 +
 +
|-
 +
| <div id="TaskStatus">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Status</div>
 +
|-
 +
|
 +
    Tasks can be tracked by status.
 +
 +
|-
 +
| <div id="TaskDetails">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Details</div>
 +
|-
 +
|
 +
    Task details provide a description of the task.
 +
 +
|-
 +
| <div id="TaskURL">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: URL</div>
 +
|-
 +
|
 +
    The URL field is used to store the website related to the task.
 +
 +
|-
 +
| <div id="TaskNotes">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Notes</div>
 +
|-
 +
|
 +
    Notes can be stored for each task.
 +
 +
|-
 +
| <div id="TaskDueDate">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Due Date</div>
 +
|-
 +
|
 +
    Task can be tracked by due date.
 +
 +
|-
 +
| <div id="TaskDueTime">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Due Time</div>
 +
|-
 +
|
 +
    Tasks can be tracked by due time.
 +
 +
|-
 +
| <div id="TaskAssignmentType">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Assignment Type</div>
 +
|-
 +
|
 +
    Tasks can be assigned to individuals by type.
 +
        Account Manager
 +
        Salesperson
 +
        Servicer
 +
        User
 +
 +
|-
 +
| <div id="TaskAssignedTo">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Assigned To</div>
 +
|-
 +
|
 +
    The individual that will handle the task.
 +
 +
|-
 +
| <div id="TaskEmail">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Email</div>
 +
|-
 +
|
 +
    An email can be stored with the task.
 +
 +
|-
 +
| <div id="TaskTextPhone">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tasks: Text Phone</div>
 +
|-
 +
|
 +
    A telephone number for texting can be stored with the task.
 +
 +
|-
 +
| <div id="TaxClass">&nbsp;</div>
 +
|-
 +
| <div class="fieldHeader">Tax Class</div>
 +
|-
 +
|
 +
    The item's task class.
 +
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div id="customertaxexemptno">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Exempt Number</div>
 +
|-
 +
|
 +
    If the customer is tax exempt, a value must be used in this field. 
 +
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div id="customertaxschedule">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Tax Schedule</div>
 +
|-
 +
|
 +
    The customer's tax schedule.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
 +
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div id="customerterms">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Terms</div>
 +
|-
 +
|
 +
    The customer's terms.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
 +
 +
|-
 +
| <div id="TransactionBilledStatus">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Billed Status</div>
 +
|-
 +
|
 +
    Indicates the transaction's position in the billing process.
 +
        N = Not billed
 +
        I = On an unposted invoice
 +
        Y = On a posted invoice
 +
 +
|-
 +
| <div id="TransactionCovered">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Covered Checkbox</div>
 +
|-
 +
|
 +
    When checked, the transaction is covered by either a warranty or an agreement.
 +
 +
|-
 +
| <div id="TransactionDesc">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Description</div>
 +
|-
 +
|
 +
    The description of the transaction that will appear on the billing documents.
 +
 +
|-
 +
| <div id="TransactionDate">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Date</div>
 +
|-
 +
|
 +
    The date the transaction will post to the general ledger.
 +
 +
|-
 +
| <div id="TransactionEndDate">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: End Date</div>
 +
|-
 +
|
 +
    Used in labor transactions only, the date the labor ended. 
 +
 +
|-
 +
| <div id="TransactionEndTime">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: End Time</div>
 +
|-
 +
|
 +
    Used in labor transactions only, the time the labor ended. 
 +
 +
|-
 +
| <div id="TransactionExtPrice">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Extended Price</div>
 +
|-
 +
|
 +
    The price or rate multiplied by the number of units.   
 +
 +
|-
 +
| <div id="TransactionUnits">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Number of Units</div>
 +
|-
 +
|
 +
    The number of units to charge on the transaction. 
 +
 +
|-
 +
| <div id="TransactionPrice">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Price</div>
 +
|-
 +
|
 +
    Used in non-labor transaction only, the price of the item.   
 +
 +
|-
 +
| <div id="TransactionRate">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Rate</div>
 +
|-
 +
|
 +
    Used in labor transaction only, the hourly rate.   
 +
 +
|-
 +
| <div id="TransactionServicer">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Servicer</div>
 +
|-
 +
|
 +
    For labor transactions, the servicer that performed the work.  For other transactions, the servicer that is assigned the warehouse from where the parts originated.
 +
 +
|-
 +
| <div id="TransactionStartTime">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Start Time</div>
 +
|-
 +
|
 +
    Used in labor transaction only, the time the labor started.
 +
 +
|-
 +
| <div id="TransactionTaxable">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Taxable Checkbox</div>
 +
|-
 +
|
 +
    When checked, the transaction will be taxed.
 +
 +
|-
 +
| <div id="TransactionType">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Type</div>
 +
|-
 +
|
 +
    The type of transaction.  The type is used to group the transactions by labor, materials, or purchases.
 +
 +
|-
 +
| <div id="TransactionVendor">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Transaction: Vendor</div>
 +
|-
 +
|
 +
    The vendor from whom the item was purchased.
 +
 +
&nbsp;
 +
 +
|-
 +
| <div id="UserTimesetting">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">User Time Setting</div>
 +
|-
 +
|
 +
    Set the time fields in the software to either military time or AM/PM.
 +
 +
|-
 +
| <div id="workorder_agreement">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Agreement</div>
 +
|-
 +
|
 +
    The agreement that covers the work order's transactions.
 +
 +
|-
 +
| <div id="WorkOrderAgreementLabor">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Agreement Labor Checkbox</div>
 +
|-
 +
|
 +
    When checked, the labor posted to the work order is covered by an agreement.
 +
 +
|-
 +
| <div id="WorkOrderAgreementParts">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Agreement Parts Checkbox</div>
 +
|-
 +
|
 +
    When checked, the parts posted to the work order is covered by an agreement.
 +
 +
|-
 +
| <div id="WorkOrderCompletedDate">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Completed Date</div>
 +
|-
 +
|
 +
    The date the work order status changed to the complete status.
 +
 +
|-
 +
| <div id="WOCompleteTime">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Complete Time</div>
 +
|-
 +
|
 +
    The time the work order status changed to the complete status.
 +
 +
|-
 +
| <div id="WorkOrderDescription">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Description</div>
 +
|-
 +
|
 +
    The description that is used to identify the work order.
 +
 +
|-
 +
| <div id="DollarsEst">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Dollars Estimate</div>
 +
|-
 +
|
 +
    The total estimated dollars required to complete the work on the work order.
 +
 +
|-
 +
| <div id="WorkOrderNumber">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Number</div>
 +
|-
 +
|
 +
    The number used to identify the work order.
 +
 +
|-
 +
| <div id="WorkOrderStatus">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Status</div>
 +
|-
 +
|
 +
    The status of the work order.
 +
 +
|-
 +
| <div id="WorkOrderwarrLabor">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Warranty Labor Checkbox</div>
 +
|-
 +
|
 +
    Checking this checkbox indicates that the labor posted to the work order are covered by a warranty.
 +
 +
|-
 +
| <div id="WorkOrderwarrParts">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Work Order: Warranty Parts Checkbox</div>
 +
|-
 +
|
 +
    Checking this checkbox indicates that the parts posted to the work order are covered by a warranty.
 +
 +
----
 +
 +
|-
 +
| <div id="PMSchedule_coverparts">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Cover Parts Checkbox</div>
 +
|-
 +
|
 +
    Checking this checkbox indicates that the parts posted to the PM are covered by a warranty.
 +
 +
|-
 +
| <div id="PMSchedule_coverLabor">&nbsp;</div>
 +
|-
 +
| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Planned Maintenance: Cover Labor Checkbox</div>
 +
|-
 +
|
 +
    Checking this checkbox indicates that the Labor posted to the PM are covered by a warranty.
 +
 +
|-
 +
| colspan="1" | &nbsp;[[Glossary#top|Top]]
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 +
|-
 +
| &nbsp;
 
|}
 
|}

Latest revision as of 10:46, 18 February 2025

Glossary
 
Account Manager
   Account managers are responsible for the customer relationship. Account managers are assigned to customers and(or) jobs.
 
Active Status
   Indicates that the record can be used to produce results.
 
Agreement: Anniversary Date
   The date the agreement terms will end.
 
Agreement: Auto Renew%
   Indicates the amount percent of increase for the agreement renewal.
 
Agreement: Balance
   The current balance of the contract.
 
Agreement: Billable Checkbox
   When checked, indicates that the agreement will be included in the billing process.
 
Agreement: Billing Total
   The total contract amount for the agreement.
 
Agreement: Commission Rate
   The commission rate that will be used when billing the agreement.
 
Agreement: Contact
   The person that should be contacted concerning the agreement.
 
Agreement: Contact Months
   The number of months covered by the agreement.
 
Agreement: Cover Labor
   Indicates if the agreement covers labor transactions.
 
Agreement: Cover Parts
   Indicates if the agreement covers parts transactions.

 

 
Agreement: Current Contract Amount
   The amount of the contract at the time of creation.
 
Agreement: Deferred Revenue Balance
   The current balance of deferred revenues for the contract.
 
Agreement: Deferred Revenues Total
   The total deferred revenues posted to date.
 
Agreement: Established Date
   The date the agreement was first established
 
Agreement: Free Months
   The number of months the customer is being provide for free.
 
Agreement: Frequency
   The billing frequency. i.e., Annually, Monthly
 
Agreement: Gross Profit Contact Billed to Date
   The agreement's gross profit based on billings to date.
 
Agreement: Gross Profit Contract Term to Date
   The agreement's gross profit recorded on the contract to date. 
 
Agreement: Labor Budget Balance %
   Percentage of labor budget balance to date. 
 
Agreement: Labor Budget Used %
   Percentage of labor budget used to date.
 
Agreement: Labor Budget Hours Used to Date
   The number of budgeted hours billed to date.
 
Agreement: Labor Hours Balance
   The remainder of the budgeted hours to date.
 
Agreement: Labor Hours Budget
   The number of labor hours budgeted for the contract's term. 
 
Agreement: Last Increase
   The increase amount from the last renewal.
 
Agreement: Number
   Agreement numbers are used to identify agreements. On the Job forms it indicates the agreement that may be used to cover transactions. On the PM Schedule form it indicates the agreement that is attached to the schedule.
 
Agreement: Original Contract Amount
   The total price for the contract when started.
 
Agreement: Parts Billed to Date
   The amount billed to date for parts.
 
Agreement: Parts Budget
   The total amount budgeted for parts on the agreement contract.
 
Agreement: Parts Budget Balance
   The remainder of the amount budgeted for parts to date after invoicing.
 
Agreement: Parts Budget Balance %
   Percentage of parts budget balance to date. 
 
Agreement: Parts Budget Used %
   The amount of the parts budget billed to date.
 
Agreement: Price Level
   The price level that will be used when billing the agreement.
 
Agreement: Pricing Method
   Agreements can be priced based on the different methods.  
       Blanket: One price covers all sites and equipment on the agreement.  
       By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price. 
       By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price. 
 
Agreement: Priority
   The priority code that would be used for jobs created for agreement coverage.
 
Agreement: Purchase Order
   The purchase order provided by the customer for the agreement.
 
Agreement: Renewable
   Indicates that the agreement is eligible for renewal. Eligible agreements will be included in the renewal process.
 
Agreement: Renewal Amount
   The amount that will be billed on agreement renewal.
 
Agreement: Renewal Method
   The renewal method field is used when determining the renewal contract amount. The contract amount can be a fixed amount or changed based on a change percentage.
       Fixed Amount: The renewal will use the exact amount in this field.
       Change Percent: Increases the contract amount by the percent in the Renewal Amount field.
 
Agreement: Renewal Months
   The contract months to use on the agreement's renewal.
 
Agreement: Renewal Text
   The text that will be displayed on the agreement renewal invoice. 
 
Agreement: Renew As
   Used to indicate the type of invoice that will be created upon renewal.
 
Agreement: Revenues Total
   The total amount billed for the contract to date.
 
Agreement: Salesperson
   The salesperson that should be assigned to the invoices when billing occurs.
 
Agreement: SLA
   Indicates that the jobs created for this agreement are covered by SLA priority.
 
Agreement: Start Date
   The date the agreement terms will begin.
 
Agreement: Status Code
   The status code is used to track the agreements progress through the renewal process.
 
Agreement Type
   Used to organize agreements by type. Agreement types are also used to establish settings for agreements by default. 
 
Agreement Type: Code
   The agreement type code code is used to identify the agreement type.
 
Agreement Type: Description
   The description used to identify the agreement type.
 
Agreement Type: Contract Months
   The number of months for new agreements.
 
Agreement Type: Cover Parts Checkbox
   When checked, the parts covered by the agreement will have no charge.
 
Agreement Type: Cover Labor Checkbox
   When checked, the parts covered by the agreement will have no charge.
 
Agreement Type: SLA Checkbox
   Check this box if the agreement qualifies for SLA service. 
 
Agreement Type: SLA Priority Code
   The SLA qualified priority code to use for new agreements.
 
Agreement Type: Message
   This message will appear on the agreement.
 
Agreement Type: Labor Hours Budget
   The budgeted number of labor hours.
 
Agreement Type: Parts Dollars Budget
   The budgeted parts dollars.
 
Agreement Type: Percent Used >=
   Percentage of labor budget used.
 
Agreement Type: Dollars Used >=
   Percentage of parts dollars used.
 
Agreement Type: Auto Number by Type
   When checked, new agreements will auto-number using the value in the Next Number field based on the Agreement Type.
 
Agreement Type: Next Number
   Used when auto-numbering agreements. 
 
Agreement Type: Enforce Defaults
   When checked, the agreement type defaults cannot be changed on the agreement.
 
Agreement Type Planned Invoice Options: Billable
   When checked, the agreements assigned to the agreement type will be billable by default.
 
Agreement Type Planned Invoice Options: Frequency
   The billing frequency. i.e., Annually, Monthly
 
Agreement Type Planned Invoice Options: Tax Class
   The tax class that should be assigned to the invoice when the agreement is billed.
 
Agreement Type Planned Invoice Options: Allocation
   The allocation that will be assigned when processing agreements. Allocations are used to establish the general ledger posting accounts and amounts.
 
Agreement Type Planned Invoice Options: Deferred Revenues
   When checked, new agreements will use the deferred revenue feature during the billing process.
 
Agreement Type Planned Invoice Options: Pricing Method
   The pricing method used when processing agreement transactions. 
       Blanket: One price covers all sites and equipment on the agreement.  
       By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price. 
       By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price. 
 
Agreement Type Planned Invoice Options: Include Site Details on Invoice
   When checked, the site details will appear on agreement invoices.
 
Agreement Type Planned Invoice Options: Include Equipment Details on Invoice
   When checked, equipment details will appear on agreement invoices.
 
Agreement Type Planned Invoice Options: Include Site Summary on Invoice
   When checked, a site summary will appear on agreement invoices.
 
Agreement Type Planned Invoice Options: Include Equipment Summary on Invoice
   When checked, an equipment summary will appear on agreement invoices.
 
Agreement Type Planned Renewal Options: Renewable Checkbox
   When checked, the agreement will be marked renewable on creation.
 
Agreement Type Planned Renewal Options: Renewal Months
   The number of default renewal months on new agreements.
 
Agreement Type Planned Renewal Options: Renew As
   The default renew as value for new agreements.  
 
Agreement Type Planned Renewal Options: Include Site Details on Invoice
   When checked, the site details will appear on renewal invoices.
 
Agreement Type Planned Renewal Options: Include Equipment Details on Invoice
   When checked, equipment details will appear on renewal invoices.
 
Agreement Type Planned Renewal Options: Include Site Summary on Invoice
   When checked, a site summary will appear on renewal invoices.
 
Agreement Type Planned Renewal Options: Include Equipment Summary on Invoice
   When checked, an equipment summary will appear on renewal invoices.
 
Agreement Type Planned Maintenance Options: Create a Job for each Equipment
   When checked, planned maintenance will create a separate job for each equipment record assigned to the schedule.
 
Agreement Type Planned Maintenance Options: Create Transactions
   When checked, planned maintenance will automatically add the transactions to the generated jobs.
 
Agreement Type Planned Maintenance Options: Price Transactions
   When checked, planned maintenance will add the transactions, with pricing, to the generated jobs.
 
Allocation
   Allocations are used to distribute the agreement dollars to the required general ledger accounts.  
 
Allocation: Description
   The description used to identify the allocation.
 
Allocation: Revenue Type
   Indicates if the allocation will be a percentage or fixed amount.
 
Allocation: Pricing Method
   Agreements can be priced based on the different methods. Allocations define the price method the can be assigned in agreement types. 
       Blanket: One price covers all sites and equipment on the agreement.  
       By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price. 
       By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price. 
 
Allocation: Price
   The allocation price.  
       Blanket: One price covers all sites and equipment on the agreement.  Enter the price that will cover the entire contract.
       By Site: The contract amount is a total of all site prices on the agreement. Enter the default price for a site. 
       By Equipment: The contract amount is a total of all equipment prices on the agreement. Enter the default price for an equipment item. 
 
Allocation Details: Type
   The type of general ledger entry. 
       Deferred Revenue: Posts to a deferred revenue account.
       Revenue: Post to a sales revenue account.
 
Allocation Details: Miscellaneous Item
   The miscellaneous item to use when posting to the ERP system.
 
Allocation Details: Allocations Account
   The account that should be affected by the allocation transaction.
 
Allocation Details: Amount
   The amount of the allocation transaction.
 
Back Office Transaction Entry: Work Order
   The transaction will be assigned to the selected work order. 
 
Back Office Transaction Entry: Stock Radio Button
   Toggles the Inventory search to include only material items.
 
Back Office Transaction Entry: Non-stock Radio Button
   Toggles the Inventory search to include only non-inventory material items.
 
Back Office Transaction Entry: Find by Item Code
   Used to search for an item by the item's code.
 
Back Office Transaction Entry: Find by Item Description
   Used to search for an item by item's description.
 
Back Office Transaction Entry: Servicer
   The servicer that will be assigned to the transaction. This field controls the warehouse list.
 
Back Office Transaction Entry: Agreement
   The agreement assigned to the selected work order.
 
Back Office Transaction Entry: Warehouse
   The warehouse from where the item will be allocated.
 
Back Office Transaction Entry: Cost Type
   Used to assign general ledger account allocations.
 
Back Office Transaction Entry: Equipment
   The equipment assigned to the selected work order.
 
Back Office Transaction Entry: Covered
   Indicates whether or not the transaction should be covered by either warranty or agreement. The software will determine the coverage based on the availably of coverage based on warranty and agreement settings.  If coverage exists, the price will change to 0.
 
Back Office Transaction Entry: Item Code
   The item code that will be used to identify the item. 
 
Back Office Transaction Entry: Trans Description
   The transaction description that will appear on the invoice. This can be different from the item description.
 
Back Office Transaction Entry: Vendor List
   Used to attach a vendor to the transaction.  Purchase transactions only.
 
Back Office Transaction Entry: Start Date
   The date the labor transaction started.  Labor transactions only.
 
Back Office Transaction Entry: Trans Date
   The transaction date.  Inventory and Purchase transactions only.
 
Back Office Transaction Entry: Start Time
   The time the labor transaction started.  Labor transactions only.
 
Back Office Transaction Entry: End Date
   The date the labor transaction ended.  Labor transactions only. This field is only available for use when multiple day transactions is on.
 
Back Office Transaction Entry: End Time
   The time the labor transaction ended.  Labor transactions only. 
 
Back Office Transaction Entry: No Units
   The number of units sold.
 
Back Office Transaction Entry: Taxable
   Checked when the transaction is taxable.
 
Back Office Transaction Entry: Price
   The price of the item.
 
Back Office Transaction Entry: Hidden Line
   When checked the item will not display on the invoice. It will be in the invoice total.
 
Back Office Transaction Entry: UOM
   The selected item's unit of measure. 
 
Back Office Transaction Entry: Ext Price
   The unit price multiplied by the number of units.
 
Back Office Transaction Entry: Billed Status
   Indicates the transaction's position in the billing process.
       N = Not billed
       I = On an unposted invoice
       Y = On a posted invoice
 
Button: Assigned
   When clicked, displays all items assigned to the selected record.
 
Button: Not Assigned
   When clicked, displays all the records not assigned to the selected item.
 
Call Boards: Form Name
   The board name is used to identify the board.
 
Call Boards: Board Type
   There are three types of boards.  1) Call Central 2) Dispatch 3) Call Center
 
Call Boards: Private
   Private boards will only appear in the list of the user that created the board. 
 
Call Boards: Default
   The default form will be the top form in the boards form list.
 
Call Boards: Past Due Position
   If a position is selected from this list, any jobs that are past due will color the cell according to the color settings in the selected position. 
 
Call Boards: Due Within Position
   If a position is selected from this list, any jobs that match the Due Within setting will color the cell according to the settings in the selected position. 
 
Call Boards: Priority Code Position
   If a position is selected from this list and the color settings for priority codes are setup, the board will use the color settings in the selected position.
 
Call Boards: Job Type Position
   If a position is selected from this list and the color settings for Job Types are setup, the board will use the color settings in the selected position.
 
Call Boards: Status Code Position
   If a position is selected from this list and the color settings for Status Codes are setup, the board will use the color settings in the selected position.
 
Chains
   Sites can be grouped by chain.
 
Chains: Name
   The name used to identify the chain.
 
Chains: SLA
   When checked, indicates the chain is an SLA chain. SLA chains have an expiration time for when the work is expected to be started.
 
Chains: Inbound Path
   The inbound path.
 
Chains: Outbound Path
   The outbound path.
 
Chains: Store Type Code
   Stores can be organized by type.
 
Chains: Store Type Name
   The name used to identify the store type.
 
Classification
   The classification is used in sales and cost account assignments. Classifications are assigned to Cost Types and Items.
 
Button: Remove all Assignments
   When clicked, removes all assignments from the selected record.
 
Commission Rate
   The amount of commission that is earned when an item is sold. 
 
Contact: Address
   The contacts mailing address.
 
Contact: City
   The city of the contact's mailing address.
 
Contact: Contact by Email Checkbox
   When checked, indicates the customer would permit contact by email.
 
Contact: Contact by Fax Checkbox
   When checked, indicates the customer would permit contact by fax.
 
Contact: Contact by Mail Checkbox
   When checked, indicates the customer would permit contact by mail.
 
Contact: Contact by Phone Checkbox
   When checked, indicates the customer would permit contact by telephone.
 
Contact: Country
   The country of the mailing address.
 
Contact: Email
   The contact's email address.
 
Contact: Established Date
   The date the contact record was established.
 
Contact: Fax Number
   The contact's fax number.
 
Contact: First Name
   The contact's first name. 
 
Contact: Last Name
   The contact's last name.
 
Contact: LinkedIn
   The contact's LinkedIn handle.
 
Contact: Name
   The contact's full name.
 
Contact: Opt Out Checkbox
   When checked, indicates that the contact does not want to be contacted for the purpose of marketing.
 
Contact: Phone
   The contact's telephone number.
 
Contact: Salutation
   The salutation that should be used when communicating with the contact.
 
Contact: State
   The state of the contact's mailing address.
 
Contact: Teams
   The contact's Teams handle.
 
Contact: Title
   The contact title. ex: Mr., Mrs.
 
Contact: Twitter
   The contact's Twitter handle.
 
Contact: Type
   Contact Types can be used to organize contacts.
 
Contact: Web
   The contact's website address.
 
Contact: Zip
   The postal code of the contact's mailing address.
 
Cost Type
   Cost types are used to manage general ledger sales and cost account allocations on transactions and billings.
 
Cost Type: Cost Account
   The cost account that will be assigned to transactions that match the job type and cost type. 
 
Cost Type: Cost Subaccount
   The cost sub-account that will be assigned to transactions that match the job type and cost type. 
 
Cost Type: Description
   Used to describe the cost type. 
 
Cost Type: Inventory Checkbox
   When checked, indicates that the cost type can be used for inventory transactions. 
 
Cost Type: Labor Checkbox
   When checked, indicates that the cost type can be used for labor transactions. 
 
Cost Type: Purchases Checkbox
   When checked, indicates that the cost type can be used for purchase transactions. 
 
Cost Visibility
   Cost visibility is the ability to hide cost from users.  Cost visibility is set at the user level in Account Management. If the checkbox is marked, the user will be able to view cost.
 
Customer: Account Manager
   The company representative that manages the customer's account.
 
Customer: Address
   The customer's mailing address.  
 
Customer: Billing Contact
   The primary billing contact assigned to the customer. 
 
Customer: City
   The customer's mailing address city.
 
Customer: Country
   The customer's mailing address country.
 
Customer: Email
   The email address for the primary customer contact.
 
Customer: Ext
   The main telephone numbers extension.
 
Customer: Facebook
   Link to the customer's Facebook account.
 
Customer: Fax
   The customer's contact fax number.
 
Customer: LinkedIn
   The customer's linked in account handle.
 
Customer: Name
   The name of the organization that will be billed.  Jobs can be created without a customer assignment, but not billed. 
 
Customer: Number
   Customer numbers can be used to help identify a customer. Customer number requirement is based on ERP system.
 
Customer: Price Level
   The customer's price level.  Price level requirement is based on ERP settings.
 
Customer: Phone
   The customer's business telephone number.
 
Customer: Salesperson
   The salesperson assigned to the customer's account. 
 
Customer: State
   The customer's address state.
 
Customer: Twitter
   The customer's twitter handle.
 
Customer: Zip Code
   The customer's address zip code.
 
Dispatch: Card Number
   Dispatch cards are numbered from 0 up.
 
Dispatch: Number
   The number used to identify the dispatch card.
 
Dispatch: Priority
   The priority assigned to the dispatch card. 
 
Dispatch: Primary Dispatch Card
   Once a job is created, the primary dispatch card is created. Users can also generate additional dispatch cards.
 
Dispatch: Schedule Date
   The dispatch card's schedule date. 
 
Dispatch: Schedule Time
   The dispatch card's schedule time. 
 
Dispatch: Servicer
   The servicer that is assigned the work.  
 
Dispatch: Status
   The status assigned to the individual dispatch card.
 
Equipment: Code
   Equipment codes are used to identify equipment.  Codes can be manually, or automatically assigned.
 
Equipment: Comments
   Comments related to the equipment record.  
 
Equipment: Coverage Date
   The date coverage begins for the equipment record.
 
Equipment: Description
   Used to describe the equipment.
 
Equipment: Item
   Equipment records that are also inventory items will have the Item Code in this field. 
 
Equipment: Install Date
   The date the equipment was installed on site.
 
Equipment: Labor Warranty Checkbox
   When checked, indicates the equipment is covered by a labor warranty.
 
Equipment: Labor Warranty End
   The date the labor warranty ends.
 
Equipment: Labor Warranty Start
   The date the labor warranty begins.
 
Equipment: Level
   Levels are linked to models.  If the level does not appear in the Level drop-list, check the selected model’s setup.
 
Equipment: Manufacturer
   The equipment's manufacturer.  Manufacturers are linked to the equipment type.  If you do not see the manufacturer in this list, verify that it is linked to the selected equipment type. 
 
Equipment: Model
   The equipment model. Models are linked to a manufacturer.  If the model does not appear in the model drop-list, check the selected manufacturer's setup. 
 
Equipment: Parts Warranty Checkbox
   When checked, indicates the equipment is covered by a parts warranty.
 
Equipment: Parts Warranty End
   The date the parts warranty ends.
 
Equipment: Parts Warranty Start
   The date the parts warranty begins.
 
Equipment: Sale Date
   The date the equipment was sold to the customer.
 
Equipment: Serial Number
   The equipment's serial number.  This is not required.  
 
Equipment: Type
   Equipment types are used to organize equipment.  Manufacturers are assigned by equipment type. 
 
Equipment: Position/Locations
   Indicates the equipment's physical location.
 
Equipment Type
   Equipment types are used to groups equipment. Grouping can include manufacturer, model and levels.
 
Equipment Type: Code
   The code that identifies the equipment type.
 
Equipment Type: Description
   The description used to identify the equipment type. 
 
Equipment Type: Prefix
   The three digit prefix to use when auto-numbering new equipment records.
 
Estimated Dollars
   The estimated billing amount required to complete the work. 
 
Estimated Hours
   The hours estimated to complete the work. 
 
FTP Server
   The server address required to log into your ftp server account. 
 
FTP Username
   The server username required to log into your ftp server account. 
 
FTP Password
   The server password that is required to log into your ftp server account. 
 
Hidden Checkbox
   When checked, the item to which the checkbox is assigned will be hidden on invoices. 
 
Inventory: Commissionable
   When checked the item is commissionable.
 
 
Inventory: Equipment Build Checkbox
   When checked, an equipment record will be generated each time the item is billed. Equipment build has a set of defaults that are defined for use during the process.
       Prefix: Used when equipment auto-numbering is activated.
       EQ Type
       Model
       Manufacturer
       Labor Warranty Period: The number of months for labor warranty coverage.
       Parts Warranty Period: The number of months for parts warranty coverage.
       Comment
 
Inventory: Item Code
   Used to identify the item. 
 
Inventory: Item Description
   Describes the item. This information comes from the ERP system.
 
Inventory: Item Type
   Indicates the type of Item.
 
Inventory: Prefix
   Used for equipment auto numbering.  If a matrix is in use that calls for this prefix, the system will use the value in this field. 
 
Inventory: Price Code
   The item's price code. The price code is used when calculating transaction pricing. 
 
Inventory: Product Line
   The item's product line.    
 
Inventory: Sales UOM
   The item's unit of measure.
 
Inventory: Servicer Mobile Button
   When checked, a mobile button will be made available in mobile for quick entry.
 
Inventory: Short Description
   A short description for the item. This description may be limited by ERP systems.  Users can set the size of this field. When changed the software will replace the existing short description with a new short description using the number of characters stored in this field. 
 
Inventory: Split Commission
   When checked, commission on the item can be slit.
 
Inventory: Trade Discount
   When checked, discounts are allowed.  
 
Inventory: Unit Cost
   The item's cost.    
 
Inventory: Unit Price
   The price for the item when added to a transaction.
 
Inventory: Use in Mobile
   When checked, the item will be available for use in mobile. 
 
Inventory: Warehouse
   The item's default warehouse.
 
Job: Billed Status
   Indicates where the job is in the billing process.
 
Job: Contact
   The site or customer contact assigned to the job. 
 
Job: Contact Email
   The email address for the job contact.
 
Job: Extension
   The extension number for the contact telephone number
 
Job: Job Type Code
   Used to recognize the job type.
 
Job: Main Number
   The job's main contact telephone number
 
Job: Notes
   Job notes are unlimited and can be printed on documents.   
 
Job: Number
   Used to identify the job.
 
Job: Payment Method
   The default payment method.
 
Job: Phone
   The contact telephone number for the job. 
 
Job: Primary Servicer
   The primary servicer for the job. New jobs will automatically use the primary servicer. Set up on the site level servicer #1
 
Job: Received Date
   The date the job was entered into the system by a user. 
 
Job: Received Time
   The time the job was received from the customer.    
 
Job: Reference Number
   The default payment reference number.
 
Job: Salesperson
   The salesperson for the job.  *Certain ERP systems require a salesperson.
 
Job: Service Type
   Service types are used to organize and recognize jobs.  Service types are organized by job type. 
 
Job: SLA Checkbox
   Check this box if the job qualifies for SLA service. This defaults from the site.
 
Job: SLA Expiration Date
   The date the technician must start the work to meet the SLA criteria.
 
Job: SLA Expiration Time
   The time the technician must start the work to meet the SLA criteria.
 
Job: Status
   Status codes are used to determine the job's position in the work process. 
 
Job: Status Bar
   The status bar indicates the job's status progress.
 
Job Type: Description
   Used to describe the job type. 
 
Job Type: Estimated Hours
   The hours estimated to complete the job. 
 
Job Type
   Job types are used to organize jobs by type and service types. Job types are tied to the billing sales and cost accounts for transactions. 
 
Job Type: KPI Call Count Checkbox
   When checked the jobs assigned the job type will be counted in the KPI analytics.
 
Job Type: Opportunity
   Marks the job type as a job opportunity.
 
Job Type: Quoted $s
   The dollars quoted for the job. 
 
KPI
   KPI fields are indicators of job profit and profitability.
 
KPI: Departure Date
   The date the job was changed to the departed status code.
 
KPI: Departure Time
   The time the job was changed to the departed status code.
 
KPI: Job Start Date
   The date the job started.
 
KPI: Job Start Time
   The time the job started.
 
KPI: Job Complete Date
   The date the job was marked complete.
 
KPI: Job Complete Time
   The time the job was marked complete.
 
KPI: Job Revenues
   The total revenues to date.
 
KPI: Job Elapse Time
   The time between the received date/time and the job close date/time. If the job is not closed the current date is used as the cut-off. 
 
KPI: Job Repair Time
   The labor hours posted to date.
 
KPI: Job Response Time
   The time between the received date/time and the arrival date/time.
 
KPI: Job Profit
   The job's profit to date.
 
KPI: Job Invoice Status
   The job's billing status.
 
KPI: Invoice Date
   The date the job was first invoiced.
 
Levels
   Models can be grouped by levels. Levels can be grouped by type.
 
Levels: Code
   The code used to identify the level. 
 
Levels: Description
   The description that identifies the level.
 
Levels: Prefix
   The three digit prefix to use when auto-numbering new equipment records.
 
Levels: Type
   Level types are used to group levels.
 
Location
   Indicates the physical location of a piece of equipment at a site.
 
Manufacturer
   The manufacturer is assigned to equipment records.  The manufacturer is assigned models.  
 
Manufacturer: Code
   The code used to identify the manufacturer.  
 
Manufacturer: Description
   The description that identifies the manufacturer.
 
Manufacturer: Prefix
   The three digit prefix to use when auto-numbering new equipment records.
 
Messages: Target Type
   Defines the type of target audience for the message.
 
Messages: Default Target Type
   Defines the type of target audience for the message as the default value for new messages.
 
Messages: Target
   Defines a specific target for a message.  Targets are Users, Servicers or Dispatch groups. 
 
Messages: Start Date
   The first date active messages are displayed. 
 
Messages: End Date
   The last date active messages will be displayed.  Note: All messages are removed after 72 hours. 
 
Messages: Message Text
   The content of the message. 
 
Messages: Field Complete
   When checked an automatic message will generate when jobs are changed to the Field Complete status. 
 
Messages: Auto Show Messages
   When checked the message window will automatically display when users load the Dashboard. When not checked the use will have to click a button to open the messages window.
 
Mobile Transaction Entry: Servicer
   The servicer that should be used when posting the transaction.
 
Model: Code
   The code used to identify the model.  
 
Model: Description
   The description that identifies the model.
 
Model: Prefix
   The three digit prefix to use when auto-numbering new equipment records.
 
Note: Category
   Notes can be organized by category.
 
Note: Content
   The note content that will display on the form and print on any documents.
 
Note: Internal Note Checkbox
   Internal notes do not print on invoices and dispatch cards.
 
Note: Print Note on Ticket Checkbox
   When checked, the note will print on the dispatch card.
 
Planned Maintenance: Type
   Planned maintenance types are used to organize schedules and establish default values.
 
Planned Maintenance: ID
   The ID is used to identify the schedule.
 
Planned Maintenance: Description
   Descriptions can also help with identification.
 
Planned Maintenance: Material Group Code
   Material Group Codes provide the ability to add materials to schedules by grouping. 
 
Planned Maintenance: Task Code
   PM task codes are used to organize schedules and establish material group codes.
 
Priority
   The default priority that will be used when creating new jobs to establish schedule date and time.  Priorities are assigned to sites as a default for new jobs. 
 
Priority: Code
   Priority codes are used to establish the response time when scheduling jobs.
 
Priority: Day of the Week
   When checked, indicates that jobs can be scheduled on that day of the week.
 
Priority: Description
   Describe the priority.
 
Priority: End Time
   Indicates the latest time a job can be scheduled on each day of the week.
 
Priority: Response Time
   Indicates the number of hours between the received time and the scheduled time. 
 
Priority: SLA
   When checked, indicates the priority is an SLA code. Only priority codes marked SLA will appear for jobs created on and SLA site.
 
Priority: SLA Expiration
   The number of hours that are required to meet the SLA deadline. 
 
Priority: Start Time
   Indicated the earliest time a job can be scheduled on each day of the week.
 
Quoted Dollars
   The billing amount quoted for the job.   
 
Quoted Hours
   The hours quoted for the job.     
 
Purchase Order Number
   The purchase order number issued by the customer for the work.  
 
Reporting Groups
   A group code can be assigned to a miscellaneous charge code to group like Item codes. 
 
Representative: Address
   The mailing address for the representative.
 
Representative: City
   The city for the mailing address
 
Representative: Country
   The country for the mailing address.
 
Representative: Division
   If division are in use, the representative division can be assigned.
 
Representative: Email
   The email address can be used to contact the representative.
 
Representative: Name
   The name of the representative.
 
Representative: Number
   The representative number can be used to recognize a representative.
 
Representative: Phone
   The telephone number can be used to contact the representative.
 
Representative: State
   The mailing address state.
 
Representative: Type
   Types are used to organize representatives.
 
Representative: Zip
   The postal code for the mailing address.
 
Request
   Requests are defined using the Request Management feature. The request defines the work requested. 
 
Request Notes
   Request notes are used to further define the work requested.
 
Revenue Account
   The sales account that will be assigned to transactions that match the job type and cost type. 
 
Revenue subaccount
   The sales sub-account that will be assigned to transactions that match the job type and cost type.
 
Role Management
   User roles provide access to assigned forms while restricting access to unassigned forms. 
 
Schedule Date
   The date the technician is scheduled to do the work.
 
Schedule Time
   The time the technician is scheduled to do the work.
 
Scheduling: Reason Code
   Describe the reason the servicer is not available for work.
 
Scheduling: Start Date
   The first date for the time off schedule.
 
Scheduling: End Date
   The last date for the time off schedule.
 
Scheduling: Start Time
   The starting time for the scheduled time off. If the scheduled time off spans dates and the replicate time option is not used, this date will be the start of the day for all dates except the first date. 
 
Scheduling: End Time
   The End time for the scheduled time off. If the scheduled time off spans dates and the replicate time option is not used, this date will be the end of the day for all dates except the last date. 
 
Scheduling: Replicate Time
   The replicate time option is used for date spans.  When checked the time on each day will match the start and end times in the fields.  If not, the first day will use the start time, the last day will use the end time and all days in between will display 24 hours of time.
 
Send to Mobile Checkbox
   On save, if this checkbox is checked, the job will be made available in mobile.    
 
Servicer
   The technician that will perform the work.
 
Servicer: Number
   The number used to identify the technician.
 
Servicer: Employee Number
   If the servicer is also an employee, the employee number can be stored in this field. 
 
Servicer: Subcontractor Checkbox
   When checked, indicates that the servicer is a contracted employee or vendor.
 
Servicer: Name
   The name of the technician.
 
Servicer: Vendor
   This field is used when the servicer is a vendor. The vendor is selected from the list and other vendor fields become available for use.
 
Servicer: Address
   The technician's mailing address.
 
Servicer: Billing Rate
   The technicians hourly labor billing rate.
 
Servicer: PO Required Checkbox
   When checked, the vendor requires a purchase order for all requested work.
 
Servicer: Hourly Cost
   The hourly cost for the technician.
 
Servicer: Insurance Certificate on File Checkbox
   For use with vendors or contract employees only. Indicates that a Certificate of Insurance is on file.
 
Servicer: Burden
   The hourly burden for the technician. 
 
Servicer: Certificate File Name
   The file name for the Certificate of Insurance.
 
Servicer: City
   The servicer's mailing address city.
 
Servicer: Warehouse
   The servicer's default warehouse.
 
Servicer: Terms
   If the servicer is a vendor or contract employee, the terms for payment. 
 
Servicer: State
   The servicer's mailing address state.
 
Servicer: Zip
   The servicer's mailing address postal code.
 
Servicer: Email
   The servicer's email address.
 
Servicer: Mobile Checkbox
   When checked, the servicer's jobs will appear on the mobile board.
 
Servicer: Country
   The servicer's mailing address country
 
Servicer: Established Date
   The date the servicer relationship was established.
 
Servicer: User List
   Servicers must be assigned to a user login before the user can use the mobile system.  
 
Servicer: Phone
   The telephone number for contacting the servicer.
 
Servicer: Servicer Image File
   The name of the file that contains an image of the technician.
 
Servicer: Service Dispatch Batch
   Mobile jobs can be grouped by batch for posting to the back office. 
 
Servicer: Tom Tom ID
   The Tom Tom ID for the servicer.  
 
Servicer: User Map Pin
   Technicians can be mapped using pins.  
 
Software Defaults: New Job Defaults
   The values that will be used by default when adding new jobs.  Some of these values can be changed at the job level. 
       Request
       Override Job No
       Send Job Email
       Job Type
       Service Type
       Priority
       Est Hours
       Job Next No
       Job Length
       Job Leading Characters
 
Software Defaults, New Job Defaults: Override Job No Checkbox
   When checked, users are allowed to alter the job number.  Warning! This could interrupt the job numbering system.
 
Software Defaults, New Job Defaults: Send Job Email Checkbox
   When checked, the send email form will be displayed when a new job is saved.
 
Software Defaults, New Job Defaults: Est Hours
   The hours estimated to complete the job. This value will be added to the primary work order.
 
Software Defaults, New Job Defaults: Job Next No
   The number that will be assigned to the next job. 
 
Software Defaults, New Job Defaults: Job Length
   The number of characters in the job number.
 
Software Defaults, New Job Defaults: Job Leading Characters
   The character(s) that will lead the job number. Leading characters are not required.
 
Software Defaults, Inventory Defaults
   The defaults that affect the inventory feature.
 
Software Defaults, Inventory Defaults: Short Desc Size
   The number of characters to use for the short description for items. This can be changed, and the software will adjust the values of the field.
 
Software Defaults, Inventory Defaults: Button: Update Item Short Descriptions
   When clicked the system will copy the first characters, based on the Short Desc Size field, to the Short Description field for all items. Warning! This cannot be reversed.
 
Software Defaults, Status Code Defaults
   Status codes are used to move jobs through the workflow process.  Each status code on this form has a purpose.  Assign a status code to each slot.  *These are required.
 
Software Defaults, Equipment Defaults
   Default values for new equipment records. 
 
Software Defaults, Equipment Defaults: Warranty Based On
   Warranties can be set based on the Sale Date or the installation date.
 
Software Defaults, Equipment Defaults: Allocation Based On
   General ledger allocations can be based on the inventory item, or the model. 
 
Software Defaults, Equipment Defaults: Auto No/EQ Defaults Checkbox
   When checked, the system will automatically number new equipment records.
 
Software Defaults, Equipment Defaults: Options
   Auto-numbering can be defined using a prefix or a matrix. 
    Prefix: The prefix option will create the number using the equipment prefix followed by the next number.
    Matrix: The matrix option allows the user to establish a prefix order from the prefixes assigned to the equipment types, manufacturers and models.
 
Software Defaults, Equipment Defaults: Prefix Missing Grid Column
   The number of records that do not contain a prefix for the matrix to work properly.
 
Software Defaults, Site Defaults
   Defaults values for new sites.
 
Software Defaults, Site Defaults: Site Type
   The default site type for new sites.
 
Software Defaults, Site Defaults: Tax Schedule
   The default tax schedule for new sites. This value is only used if the tax schedule is not filled from the customer record.
 
Software Defaults, Site Defaults: Use Customer Name and Address Checkbox
   When checked, the customer’s name and address automatically fill in the site form when adding a new site.
 
Software Defaults, Transaction Assignments
   The defaults and settings for new transactions.
 
Software Defaults, Transaction Assignments: Warehouse
   The warehouse to assign to any transaction for which a warehouse has not been assigned.
 
Software Defaults, Transaction Assignments: Tax on Customer Checkbox
   When checked, invoices will automatically use the customer's tax schedule.
 
Software Defaults, Transaction Assignments: Multi-branch Checkbox
   When checked, the multi-branch feature becomes active, and its rules applied.
 
Software Defaults, Transaction Assignments: Segment
   When the Multi-Branch checkbox is checked, this field becomes active. Use it to set the default branch segment to use when a branch segment is missing.
 
Software Defaults, Transaction Assignments: Default Sales Account
   The sales account to assign to any transaction for which a sales account has not been assigned.  
 
Software Defaults, Transaction Assignments: Default Cost Account
   The cost account to assign to any transaction for which a cost account has not been assigned.  
 
Software Defaults, Invoicing
   The defaults and settings for new transactions.
 
Software Defaults, Invoicing: Require Sales Tax Checkbox
   When checked, sales tax will be required on all invoices.
 
Software Defaults, Invoicing: Non-Tax Schedule
   Certain ERP system require a tax schedule on all invoices, even those that are non-tax.  This schedule fills that requirement.
 
Software Defaults, Invoicing: Next Batch Number
   The next batch to use when invoices are created automatically.
 
Software Defaults, Invoicing: Next No
   The next invoice number.
 
Software Defaults, Invoicing: Length
   The invoice number length.  This value cannot be shortened.
 
Software Defaults, Invoicing: Leading Characters
   The leading character for invoice numbers.  Leading characters are not required.
 
Software Defaults, Planned Maintenance
   The defaults and settings for planned maintenance jobs.
 
Software Defaults, Planned Maintenance: Priority
   The default priority for new planned maintenance jobs.
 
Software Defaults, Planned Maintenance: Status Code
   The defaults status code for new planned maintenance jobs.
 
Software Defaults, Planned Maintenance: Include Site info as comment
   When checked, the site information will appear on planned maintenance invoices.
 
Software Defaults, Planned Maintenance: Include Equipment info as comment
   When checked, the equipment information will appear on planned maintenance invoices.
 
Software Defaults, Agreements
   The settings and defaults for new agreements.
 
Software Defaults, Agreements: Auto No Checkbox
   When checked, the system will automatically number any agreements that are created using an agreement type that is not also set to auto number.
 
Software Defaults, Agreements: Next Agreement No
   The next number that will be used when creating agreements.
 
Software Defaults, Agreements: Agreement No Length
   The maximum length of the agreement numbers.
 
Software Defaults, Agreements: Default Agreement Type
   The agreement type that will be automatically assigned to new agreements.
 
Software Defaults, Agreements: Planned Billing Auto Process Checkbox
   When checked, the planned billing nightly auto-processing feature is active. 
 
Software Defaults, Agreements: Processing Date
   Indicates the date to use when processing planned billing.   
 
Software Defaults, Agreements: Deferred Revenue Auto Process
   When checked, the deferred revenues nightly auto-renewal feature is active.
 
Software Defaults, Agreements: Agreement Renewals Auto Process
   When checked, the planned billing nightly auto-renewal feature is active.
 
Software Defaults, Agreements: Agreement Type PRO Include Site Details on Invoice
   When checked, the site details will appear on the invoices.
 
Software Defaults, Agreements: Agreement Type PRO Include Equipment Details on Invoice
   When checked, the equipment details will appear on the invoices.
 
Software Defaults, Agreements: Agreement Type PRO Include Site Summary on Invoice
   When checked, the site summary information will appear on the invoices.
 
Software Defaults, Agreements: Agreement Type PRO Include Equipment Summary on Invoice:
   When checked, the equipment summary information will appear on the invoices.
 
Software Defaults, Agreements: Revenue Account
   The default revenue account that will be assigned to new allocations.
 
Software Defaults, Agreements: Deferred Revenue Account
   The default deferred revenue account that will be assigned to new allocations.
 
Software Defaults, Agreements: Item
   The default item that will be assigned to new allocations.
 
Service Type
   Service Types are used to organize jobs using a job type, service type relationship.
 
Service Type: Code
   Used to identify the service type.
 
Service Type: Desc
   Used to describe the service type.
 
Site: Address
   The physical address for the site.  This field is used in dispatching.
 
Site: Branch
   The site branch is required if multi-branching is in use.
 
Site: Chain
   The site's chain.  Chains are not required.
 
Site: City
   The address city for the site.  This field is used in dispatching.
 
Site: Clone From Customer Address
   When clicked, this button will clone the customer's address to the site.
 
Site: Clone From Ship To
   When an item is selected, the ship to address will be copied to the site address fields.
 
Site: Code
   The site code can be used to identify the site.  It is not required.
 
Site: Established Date
   The date the site was added.
 
Site: Fax Number
   The site's Fax number. 
 
Site: Labor #1
   Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the first button.
 
Site: Labor #2
   Back office labor transaction entry can include two labor quick buttons.  This item will be linked to the second button.
 
Site: Latitude
   The latitude for the site location. 
 
Site: Longitude
   The longitude for the site location.
 
Site: Main Number
   The main business contact telephone number for the site.
 
Site: Map Code
   When using Key Maps or Rand McNally's Street Finders this will be the code to associate the location with a particular map page.
 
Site: Name
   The name of the site location. This is used to identify the site.
 
Site: Price Level
   The price level that should be used when billing jobs.
 
Site: Primary Contact
   The site's primary contact.  Contacts are managed using the Contact Management system. 
 
Site: Referral Code
   The site's referral code.  Referral codes are not required.
 
Site: Servicer #1
   The default primary servicer.  New jobs will be automatically assigned to this servicer.   
 
Site: Servicer #2
   The secondary servicer for new jobs.
 
Site: SLA
   When checked, the site qualifies for SLA service. 
 
Site: State
   The address state code for the site.  This field is used in dispatching.
 
Site: Store Number
   The store number for the site.  The store number is directly tied to the Chains feature. 
   
 
Site: Store Type
   The store type for the site.  The store number is directly tied to the Chains feature. 
 
Site: Type
   Site types are used to organize sites. Site types are not required. 
 
Site: Zip Code
   The address postal code for the site.  This field is used in dispatching.
 
Site Type
   Sites can be grouped by site type.
 
Site Type: Code
   The code used to identify the site type.
 
Site Type: Description
   The description used to identify the site type.
 
Site Type: Message
   The message of the Service Site Type will default into the field or manually type a customer note into the field. If the Service Site Type is changed the message will not change.
 
Solution
   Solutions are defined using the Solution Management feature.  The solution defines the work done to complete the work.
 
Solution Notes
   Solution notes are used to further define the work performed.
 
Status Codes: Code
   The code used to identify the status code.
 
Status Codes: Description
   The description used to identify the status code.
 
Status Codes: KPI
   When marked the status code will be included in KPI counts.
 
Status Codes: In Process
   When marked the jobs assigned to this status code will be considered to be in process.  In process status codes do not appear in the status code list for new jobs.

 

 
Status Codes: Allow Invoicing
   Invoicing is only allowed for jobs where the Allow Invoicing is checked.

 

 
Status Codes: All
   Used for the search option.  When checked all status code records will be displayed during a search.
 
Subclass
   The sub-classification is used in sales and cost account assignments. 
 
Tasks: Type
   Tasks can be organized by type.
 
Tasks: Status
   Tasks can be tracked by status.
 
Tasks: Details
   Task details provide a description of the task.
 
Tasks: URL
   The URL field is used to store the website related to the task.
 
Tasks: Notes
   Notes can be stored for each task.
 
Tasks: Due Date
   Task can be tracked by due date.
 
Tasks: Due Time
   Tasks can be tracked by due time.
 
Tasks: Assignment Type
   Tasks can be assigned to individuals by type. 
       Account Manager
       Salesperson
       Servicer
       User
 
Tasks: Assigned To
   The individual that will handle the task.
 
Tasks: Email
   An email can be stored with the task.
 
Tasks: Text Phone
   A telephone number for texting can be stored with the task.
 
Tax Class
   The item's task class.
 
Tax Exempt Number
   If the customer is tax exempt, a value must be used in this field.  
 
Tax Schedule
   The customer's tax schedule.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
 
Terms
   The customer's terms.  This information is assigned at the ERP level and cannot be altered when an ERP is in use.
 
Transaction: Billed Status
   Indicates the transaction's position in the billing process.
       N = Not billed
       I = On an unposted invoice
       Y = On a posted invoice
 
Transaction: Covered Checkbox
   When checked, the transaction is covered by either a warranty or an agreement. 
 
Transaction: Description
   The description of the transaction that will appear on the billing documents. 
 
Transaction: Date
   The date the transaction will post to the general ledger. 
 
Transaction: End Date
   Used in labor transactions only, the date the labor ended.  
 
Transaction: End Time
   Used in labor transactions only, the time the labor ended.  
 
Transaction: Extended Price
   The price or rate multiplied by the number of units.     
 
Transaction: Number of Units
   The number of units to charge on the transaction.  
 
Transaction: Price
   Used in non-labor transaction only, the price of the item.    
 
Transaction: Rate
   Used in labor transaction only, the hourly rate.     
 
Transaction: Servicer
   For labor transactions, the servicer that performed the work.  For other transactions, the servicer that is assigned the warehouse from where the parts originated.
 
Transaction: Start Time
   Used in labor transaction only, the time the labor started.
 
Transaction: Taxable Checkbox
   When checked, the transaction will be taxed. 
 
Transaction: Type
   The type of transaction.  The type is used to group the transactions by labor, materials, or purchases.
 
Transaction: Vendor
   The vendor from whom the item was purchased.

 

 
User Time Setting
   Set the time fields in the software to either military time or AM/PM.
 
Work Order: Agreement
   The agreement that covers the work order's transactions.
 
Work Order: Agreement Labor Checkbox
   When checked, the labor posted to the work order is covered by an agreement.
 
Work Order: Agreement Parts Checkbox
   When checked, the parts posted to the work order is covered by an agreement.
 
Work Order: Completed Date
   The date the work order status changed to the complete status.
 
Work Order: Complete Time
   The time the work order status changed to the complete status.
 
Work Order: Description
   The description that is used to identify the work order.
 
Work Order: Dollars Estimate
   The total estimated dollars required to complete the work on the work order.
 
Work Order: Number
   The number used to identify the work order.
 
Work Order: Status
   The status of the work order.
 
Work Order: Warranty Labor Checkbox
   Checking this checkbox indicates that the labor posted to the work order are covered by a warranty.
 
Work Order: Warranty Parts Checkbox
   Checking this checkbox indicates that the parts posted to the work order are covered by a warranty.

 
Planned Maintenance: Cover Parts Checkbox
   Checking this checkbox indicates that the parts posted to the PM are covered by a warranty.
 
Planned Maintenance: Cover Labor Checkbox
   Checking this checkbox indicates that the Labor posted to the PM are covered by a warranty.
 Top