Legal declarations. Copyright. Trademarks. Warranty. Limitation of liability. License agreement

Transcription

1

2 Legal declarations Copyright Trademarks Warranty Manual copyright 2008 WennSoft Inc. All rights reserved. Your right to copy this documentation is limited by copyright law and the terms of the software license agreement. As the software licensee, you may make a reasonable number of copies or printouts for your own use. Making unauthorized copies, adaptations, compilations, or derivative works for commercial distribution is prohibited and constitutes a punishable violation of the law. Portions of this manual are taken from materials and products by Microsoft Business Solutions. Copyright 2008 by Microsoft Business Solutions. Reprinted by permission of Microsoft Business Solutions. Unless otherwise noted, all names of companies, products, street addresses, and persons contained herein are fictitious and are used solely to document the use of this product. All company or product names mentioned are trademarks or registered trademarks of WennSoft Inc., Microsoft Business Solutions, or of their respective holders. WennSoft disclaims any warranty regarding the program, documentation, or sample code contained in this document, including the warranties of merchantability and fitness for a particular purpose. Limitation of liability The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by WennSoft. WennSoft assumes no responsibility or liability for any errors or inaccuracies that may appear in this manual. Neither WennSoft nor anyone else who has been involved in the creation, production, or delivery of this documentation shall be liable for any indirect, incidental, special, exemplary, or consequential damages, including but not limited to any loss of anticipated profit or benefits, resulting from the use of this documentation or sample code. License agreement Use of this product is covered by a license agreement provided by WennSoft Inc., with the software product. If you have any questions, please call WennSoft Sales at

3 Table of Contents Introduction to MobileTEC Host What s included in this document MobileTEC Client enhancements About Microsoft Message Queuing (MSMQ)? About event logs Installing and Configuring MobileTEC Host System requirements Installing the software Configuring MobileTEC Host Verifying security for MobileHOST private queues Verifying message queuing triggers are set to local system account Hiding inventory item costs from technicians Customizing the Call Summary Report for technicians Setting up and processing in Service Management What gets broadcasted from the host to the MobileTEC devices? Setting up technicians to use MobileTEC Setting up TimeTrack for unbilled transactions Creating transactions for inventory and non-inventory items entered by technicians Processing purchase orders created by technicians in the field Setting up custom task code responses Sending a note to a MobileTEC technician Index... Index-1 1

4 2

5 Introduction to MobileTEC Host MobileTEC Laptop wirelessly connects remote technicians to a host system. Technicians can receive appointments as they are created on the host system. Appointment details such as estimated hours, description, location, and service call history are transmitted with the appointment. The technician can update the appointment with expense and resolution details. MobileTEC Host-to-Client and Client-to-Host data flow diagrams appear at the end of this chapter. What s included in this document This document contains step-by-step instructions and information on: Installing MobileTEC Host Configuring MobileTEC Host to be able to send and receive information Setup procedures within WennSoft Service Management Series MobileTEC Client enhancements The following enhancements have been made to the MobileTEC client system. Field Purchase Orders - Technicians can now create purchase orders from their mobile devices in the field for items that need to be purchased while on the job. Purchase orders created (originated) in the field by technicians need to be reviewed and processed before PO s can be committed and costs associated with those purchase order are processed throughout the system. When purchase orders are sent to the host system, they can be accessed from a WennSoft Service Management window called Mobile Purchase Order. Introduction to MobileTEC Host About Microsoft Message Queuing (MSMQ)? MSMQ Microsoft Message Queuing (MSMQ) technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. MSMQ provides guaranteed message delivery, efficient routing, security, and priority-based messaging. It can be used to implement solutions for both asynchronous and synchronous messaging scenarios. How does MSMQ benefit MobileTEC users? With Microsoft Message Queuing (MSMQ), technicians no longer have to manually start the polling cycle to check for new messages or send out-going messages; this is now handled behind the scenes by MSMQ. In addition, once the technician logs in, MSMQ automatically checks to determine if a network is available. It also provides a list of internal

6 connections, which are dynamically populated in the Data Network drop-down in the MobileTEC Login window. Technicians can work on the device without worrying about initiating the communication layer. Another benefit of MSMQ is that it does not have to be installed on the same machine as the SQL Server. Message Queuing Private Queues After installation, you will use the MobileHost Admin window to create private message queues for each MobileTEC client system user (technician). Additional generic private queues will also be created. These queues store incoming and outgoing messages between the host system and client system. You can manage these message queues by clicking Start > Control Panel > Administrative Tools > Computer Management > Services and Applications > Message Queuing. (path may be different on other operating systems). About event logs MobileTEC contains two separate event logs, one for outbound communication (from host to client device) and another for inbound communication (from client device to host). You can view these logs using the Event Viewer in Windows. 1-2

7 1-3

8 1-4

9 Installing and Configuring MobileTEC Host Note: The procedures covered in this document should be performed ONLY by authorized technical personnel, such as an IT person or WennSoft Consultant. System requirements Windows Installer 3.1 Microsoft Message Queuing (MSMQ) - (install instructions provided) Microsoft.NET Framework 2.0 Internet Information Services (IIS) v 6.0 or later Microsoft SQL Server 2000 or 2005 Microsoft Dynamics GP 9.0 or 10.0 (SP1 compatible) WennSoft Service Management Series Windows Server 2003 (or Windows XP users for demo purposes only) Note: Microsoft Message Queuing (MSMQ) and Internet Information Services (IIS) MUST BE installed on the MobileTEC host computer - NOT on the SQL Server computer. Installing the software Installing MobileTEC Host involves the following: Step 1: Install Microsoft Message Queuing Step 2: Install MobileTEC Host program (on MobileTEC host computer) Step 3: Install TimeTrack Web Service Step 1: Installing Microsoft Message Queuing Microsoft Message Queuing is installed as part of Microsoft Windows Components. Installing and Configuring MobileTEC Host You must run this installation on the MobileTEC host computer only; DO NOT install on the SQL Server computer. 1. On your desktop, go to Start > Control Panel > Add or Remove Programs > Add/Remove Windows Components.

10 2. In the Windows Components Wizard window, scroll down until you see the Message Queuing checkbox. 3. Highlight Message Queuing; DO NOT mark the checkbox yet. 4. Click the Details button. The Message Queuing window opens. Mark Common and Triggers 5. Mark the Common and Triggers checkboxes and click OK. 6. Now make sure the Message Queuing checkbox is marked. 7. Click Next. 2-2

11 The Message Queuing status window appears. 8. Click Finish to complete the installation. 2-3

12 Step 2: Installing MobileHost Web Service You must perform this installation ONLY on the MobileTEC host computer. 1. Launch the MobileHostServiceSetup.msi. Click Next. 2. Accept the license agreement and click Next. 2-4

13 3. Verify the installation folder and click Next. 4. Click Install. 2-5

14 5. When the installation is complete, click Test Web Service. Note: If the test was not successful, it might be because the MobileHost Service is not set to use ASP.NET Framework 2.0. Refer to the After Installing MobileTEC Host section for instructions on changing the ASP.NET Framework version. 6. Click Finish to complete the installation. 2-6

15 Step 3: Installing the MobileTEC Host program You must perform this installation ONLY on the MobileTEC host computer. 1. Launch the MobileHostSetup.msi. Click Next. 2. Accept the license agreement and click Next. 2-7

16 3. Verify the installation folder and click Next. 4. Click Next, then click Test to test the web service. Note: If the test was not successful, it might be because the MobileHost Service is not set to use ASP.NET Framework 2.0. Refer to the After Installing MobileTEC Host section for instructions on changing the ASP.NET Framework version. 5. Enter the login information for your SQL database. The Username automatically fills with "mobiletec" and cannot be changed. Click Next. 2-8

17 Note: The Database is the SQL Server instance (for example, SQLSERVER\INSTANCENAME), not the ODBC connection name. Note: The "mobiletec" user is created automatically with the password that you provided. 6. Click Install. The WSMobileHost script drops old MobileTEC objects (cleanup), and creates MobileTEC tables, stored procedures, and views. 2-9

18 7. Enter the password for "sa" and click OK. Click Install again. 8. Click Finish to complete the installation. 2-10

19 Step 4: Installing the TimeTrack Web Service 1. Launch the etimetrackwebservicesetup.exe. Click Next. 2. Accept the license agreement and click Next. 2-11

20 3. Verify the installation folder and click Next. 4. Enter the login information for your SQL database. Click Next. Note: The Database is the SQL Server instance (for example, SQLSERVER\INSTANCENAME), not the ODBC connection name. 2-12

21 5. Click Install. 6. When the installation is complete, click Test Web Service. Note: If the test was not successful, it might be because the MobileHost Service is not set to use ASP.NET Framework 2.0. Refer to the After Installing MobileTEC Host section for instructions on changing the ASP.NET Framework version. 7. Click Finish to complete the installation. 2-13

22 After installing MobileTEC Host After you have installed the MobileHost programs, you must do the following: Step 1: Create a scheduled task for re-attempting failed TimeTrack transactions Step 2: Verify that the MobileHost Web Service is set to use ASP.NET Framework 2.0 Step 1: Create a scheduled task for re-attempted failed TimeTrack transactions Sometimes, when labor transactions are created, they cannot be saved if the TimeTrack batch is locked for some reason. By default, this scheduled task will attempt to save the transactions at 15-minute intervals for one 24 hour period. You can change this frequency. 1. Choose Start > All Programs > Accessories > System Tools > Scheduled Tasks. 2. Double-click Add Scheduled Task, then click Next. 3. Browse to the folder: C:\Program Files\WennSoft\MobileHost. Select WSLaborExpenseReset.exe and click Open. The Scheduled Task Wizard window opens. 4. Mark the Daily radio button, then click Next. 5. Enter 12:00AM, and select to perform the task Every Day. 6. Select a Start Date that is in the past. 2-14

23 7. Click Next. 8. Enter the password for the network user, then click Next. 9. Mark the checkbox: Open advanced properties for this task when I click Finish, and click Finish. 10. Select the Schedule tab and click the Advanced button. 2-15

24 11. Mark the Repeat Task checkbox and enter an interval of 15 minutes and duration of 24 hours. 12. Click OK TWICE. The new task is added to the list of scheduled tasks. 2-16

25 Step 2: Verify that the MobileHost Web Service is set to use ASP.NET Framework Choose Start > Control Panel > Administrative Tools > Internet Information Services (IIS) Manager. 2. Expand the <computer name>, Web Sites, and Default Web Site. 3. Right-click on MobileTECHost and select Properties. 4. Click the ASP.Net tab. 5. In ASP.NET version, select Click OK. Running the WSMobileHost SQL script If, for some reason, you would need to re-run the WSMobileHost.sql script AFTER install, instructions are provided below. The WSMobileHost script drops old MobileTEC objects (cleanup), and creates MobileTEC tables, stored procedures, and views. 1. Open Query Analyzer (if running Microsoft SQL 2000) or Server Management Studio (if running Microsoft SQL 2005). 2. Select the company database from the drop-down. 3. Run the following SQL script on your company database: WSMobileHost.sql. The script is located in C:\Program Files\WennSoft\MobileHost folder. Configuring MobileTEC Host Configuring MobileTEC Host involves the following: Creating MSMQ queues, triggers, and rules Creating MobileTEC event logs 1. Start the MobileHost system (Start > All Programs > WennSoft > MobileHost > MobileHost Admin). The Mobile Host Admin window opens. 2. Click the Create all Queues, Triggers, and Rules button. Creating these will take a few moments. When finished, the queue names will appear in the list at the bottom of the window. 3. Click OK to the message. 4. Click the Create MobileTEC Event Logs button. 2-17

26 5. Click Save. 6. Mark the Log Messages, Message Encryption, and Create New Call for any Customer or Location checkboxes. Unmark ALL other checkboxes. The Create New Call for any Customer or Location checkbox allows you create service calls for any customer that exists in the host system, not just the customer listed on the technician s current call(s). Note: Logging messages helps in troubleshooting inbound and outbound messages (communication) on the IIS machine. 7. Make any other changes, as necessary, and click Save. Verifying security for MobileHOST private queues It is a good idea to verify the security for all MobileTEC private message queues. These queues include the following: mobiletecadmin mobiletechost mobiletecipaddress 2-18

27 mobileteclaborexpense Complete the steps below for EACH private queue listed above. 1. (for Windows XP users) - Choose Start > Control Panel > Administrative Tools > Computer Management > Services and Applications > Message Queuing. (for Windows XP Professional users) - Choose Start > Control Panel > Performance and Maintenance > Administrative Tools > Computer Management > Services and Applications > Message Queuing. 2. Expand Private Queues. 3. Right-click on a private queue and select Properties. 4. Click the Security tab. 5. Select the SYSTEM user. 6. Under Permissions for SYSTEM, make sure the Allow Receive Message, Peek Message, and Send Message checkboxes are marked. 7. Repeat steps 3-6 for each private queue. 2-19

28 Verifying message queuing triggers are set to local system account 1. Choose Start > Control Panel > Administrative Tools > Computer Management > Services. 2. Click the Standard tab. 3. Right-click on Message Queuing Triggers and select Properties. 4. Click the Log On tab. 5. Make sure the Local System account radio button is selected. 6. Click OK. Hiding inventory item costs from technicians If you do not want your technicians to see the cost or price of an inventory item, you can hide that data from the technicians in the Inventory tab during call complete. Hiding these values involves setting values in an XML file called AppData.xml to false. This file resides in the MobileTEC client install folder on each client machine on which MobileTEC client was installed. Before editing this file, make sure the technician is logged out of the MobileTEC application. 1. Using a standard text editor, open the file AppData.xml. 2. Locate the following lines: <add key="showinventorycost" value="true" /> <add key="showinventoryprice" value="true" /> 3. To hide a value, change that value to "false." 4. Save the file. Repeat these steps on each client machine for which you want to hide these values from technicians. 2-20

29 Customizing the Call Summary Report for technicians Note: The procedures summarized in this section should be performed ONLY by authorized technical personnel, such as an IT person, WennSoft Support Specialist, or WennSoft Consultant. Only someone who is experienced and comfortable with editing XML files should perform these procedures. You can customize the Call Summary Report so that it reflects your organization s logo, customer appreciation message, and so on. You can also rename, re-arrange, or remove areas of the report. This template file is an XML file called CallSummaryReport.xml, and is located in the install folder for both the MobileHost application and all client application installs. You can use a standard text editor to make changes to this file. The ONLY copy you need to change is on the MobileHost server. These changes can be automatically sent down to the technicians using the MobileTEC Host Admin program. This copy acts as a template, and allows for quick updates for technicians and ensures consistency in content and format of the report. The standard logo is in a graphics file called logo.jpg, which is also located in the install folders. To replace the standard logo with your own, make sure it is called logo.jpg (it must be a.jpg file). This file is also copied down to the clients along with the template file. Note: Before customizing files, make a backup copy of the original files and move them to a different folder. That way, you can always revert back to the original files, if necessary. If you revert back to the originals, make sure to copy them back to the original install folder. After making changes, update the client systems by doing the following: 1. On the Host server, start the MobileHost system (Start > All Programs > WennSoft > MobileHost > MobileHost Admin). The Mobile Host Admin window opens. 2. From the menu, select Tools > Broadcast Call Summary Report Template. The updates begin immediately. 3. Click OK to the Call Summary Report Template Sent message. The new CallSummaryReport.xml and logo.jpg files are copied to each client machine. 2-21

30 2-22

31 Setting up and processing in Service Management This chapter contains step-by-step instructions on setting up Service Management Series to enable technicians to use MobileTEC, and to enable other features of the MobileTEC system. In addition, this chapter contains processing instructions for transactions that are sent from the technicians to the host system. What gets broadcasted from the host to the MobileTEC devices? When the person back at the office clicks the Broadcast button from the Appointments window, only the selected appointment will be sent down to the MobileTEC device. If clicked from the Service Call window, all appointments for that call will be sent. In general, the following data is sent: Service Appointments info (status cannot be RE-ASSIGN or COMPLETE) Service Call info Location Sub-location (if assigned to a task) Equipment (if assigned to a task) Tasks (all assigned tasks for the current service call, and only to primary technician) Inventory (applied to a service call) Notes (customer, location, service call, contract, and /or equipment note) Attachments (from service call with types being PDF, PNG, and JPG) Setting up and processing in Service Management

32 Setting up technicians to use MobileTEC In WennSoft Service Management Series, you must set up the technicians to be able to use MobileTEC. 1. Choose Microsoft Dynamics GP > Tools > Setup > Service Management > Lookup Setup > Technicians > Technicians. The Technician Setup window opens. 2. Select a Technician ID. 3. Mark the checkbox: MobileTEC User. 4. Enter a MobileTEC Password. This is the password that must be entered when the technician logs into his MobileTEC device. 5. Choose Save. 6. Repeat the steps above for technicians who use MobileTEC. 3-2

33 Setting up TimeTrack for unbilled transactions If technicians are going to enter unbilled TimeTrack transactions into MobileTEC, the host system, namely TimeTrack, must be set up to handle those transactions properly. This involves a setup option (Create a GL Journal Entry for Unbilled Transactions), as shown below: Choose Microsoft Dynamics GP > Tools > Setup >TimeTrack > Setup Options. The TimeTrack Setups Options window opens. After marking this checkbox, you also need to set up unbilled asset accounts. Refer to the TimeTrack documentation for more information. 3-3

34 Creating transactions for inventory and non-inventory items entered by technicians When inventory or non-inventory items are consumed on a service call, the technician can enter information, pricing, and so on directly on the MobileTEC device (laptop or pocket PC). When a service call is completed, that updated information is sent back to the host, and the appropriate transactions can be created. Step 1: Set up location inventory sites for technicians In this step, you will associate stocking locations to technicians. 1. Choose Microsoft Dynamics GP > Tools > Setup > Service Management > Lookup Setup > Technicians > Technicians. The Technician Setup window opens. 2. Select a Technician ID. 3. Click Inventory Sites. The Technician Inventory Site Setup window opens. 3-4

35 4. Mark the checkbox for the inventory site(s) associated with this technician. 5. Click OK. 6. Click Save on the Technician Setup window. 7. Repeat the steps above for each MobileTEC technician. Note: When finished, make sure the MobileTEC technician does a Refresh Lookups on his/her device (laptop or pocket PC) so that the appropriate items can be selected by that technician upon completing a call. 3-5

36 Step 2: Process transactions for inventory and non-inventory items In this step, you will process the inventory and non-inventory items entered by the MobileTEC technician, which will create the appropriate transactions. See After transaction processing on 3-7 for more information. 1. Choose Inquiry > Service Management > Mobile Inventory Inquiry. The Mobile Inventory window opens. The item/part numbers entered by the MobileTEC technician in the process of completing a service call, appears in the window. To delete a record, select that item/part and click Delete. 2. Click Process to begin processing transactions. You cannot process one item/part at a time; you can only do all at once. If, for some reason, a record was not processed, it will remain displayed in the window. Click Print to print out/view the list with errors. 3. When finished, close the window. 3-6

37 After transaction processing Transactions that are processed successfully disappear from the Mobile Inventory window. Transactions that do not process successfully appear in a report, which you can print using the Print button on this window (see below). The type of transaction(s) created depends on whether your system is set up to Use Sales Order Processing for Inventory (Tools > Setup > Service Management > Invoice Setup > Invoice Options) and whether the part used is an inventory item. If using SOP for Inventory... If you are using the Use Sales Order Processing for Inventory Items option, the system creates a SOP transaction. In addition, a new batch is created with the name of MOBILE<transaction date>, for example, MOBILE for June 2nd, If NOT using SOP for Inventory... If you are not using the Use Sales Order Processing for Inventory Items option, and the item is an inventory item (serialized or non-serialized), the system creates an item transaction. In addition, a new batch is created with the name of MOBILE<transaction date>, for example, MOBILE for June 2nd, If non-inventory item... If the item is not an inventory item, the system creates a GL transaction. In addition, a new batch is created with the name of MOBILE<transaction date>, for example, MOBILE for June 2nd, If using SOP Invoicing... If you are using SOP Invoicing in WennSoft Service Management, for non-inventory items, the system will add the non-inventory line item to the primary SOP document with a $0.00 price (even if a price was entered by the technician). In addition, the document will be placed on Hold. Therefore, you must enter a price, make other changes as needed, then post the document. Note: The costs are not applied to the service call for a non-inventory part until AFTER it is posted from the WS GL Transaction Entry window or Batch Entry window. Users must have security to the WS GL Transaction Entry window. Standard inventory items are posted to the service call BEFORE the SOP or inventory batches are posted. About inventory quantity overrides For SOP and inventory transactions, the system automatically overrides quantity shortages, using the transaction quantity instead. However, you MUST have the Adjustment Overrides checkbox marked in the Inventory Control Setup window. 3-7

38 About inventory types Some inventory types, such as Kit, Misc Charges, Services, and Flat Fee, will not be processed by the Mobile Inventory window. Printing the Mobile Inventory report On the Mobile Inventory window, click Print. The report contains all items for which transaction(s) could not be created. An Error Code field contains the error code created by econnect software, a Microsoft Dynamics GP application that offers fast and accurate access to back office Microsoft Dynamics GP transactions. A list of common errors appears below: Error Code Description/Resolution 282 The service call created has no division associated with it. Assign a division to this service call in Service Management Series The inventory site does not contain the amount of available items specified on the technician-created service call. Perform an item transaction adjustment to transfer the items needed to the inventory site. Contact WennSoft Support for more information. 3-8

39 Processing purchase orders created by technicians in the field Note: Technicians cannot create purchase orders if your company is using SOP Invoicing within WennSoft Service Management. Purchase orders that were created (originated) in the field by technicians need to be reviewed and processed before PO s can be committed and costs associated with those purchase order are processed throughout the system. When purchase orders are sent to the host system, they can be accessed from a WennSoft Service Management window called Mobile Purchase Order. To access this window, choose Inquiry > Service Management > Mobile Purchase Order Inquiry. To save changes made on this window, click Save. To cancel and close this window without saving changes, click Cancel. To select purchase orders, click the checkbox next to the PO or click the Mark All button to select all purchase orders or the Unmark All to deselect all purchase orders. To delete purchase orders, select the purchase orders and click Delete. 3-9

40 To print a report of purchase orders that need to be processed, click Print. To update the display of purchase orders submitted by technicians, click Redisplay. For information on "processing" purchase orders, see the sections below. Specifying which vendors are visible to MobileTEC technicians By default, several vendors within the Microsoft Dynamics GP system appear in vendor lookups within MobileTEC, visible to the technician for selection. If your organization contains far too many vendors from which technicians could possibly need to select from, you can de-select some vendors so that they do not appear in the technicians vendor lookup list. 1. Choose Inquiry > Service Management > Mobile Vendor Setup. The MobileTEC Vendor Setup window opens. 2. Un-check the vendors that you do not want to appear in technicians lookup lists within MobileTEC. 3. When finished, click OK to save. Before processing purchase orders Since processing purchase orders is the same as "committing" them, you may want to review some of the data that was sent over by the technicians with those purchase orders. The following information can be changed: 3-10

41 Vendor ID Item Number Quantity Unit Cost Cost Code Site ID About unknown vendors/items If a technician purchased items from an unknown vendor (meaning the host system does not have a record of that vendor), you will need to: 1. Create a new vendor record for that unknown vendor, using the Vendor Maintenance window in Microsoft Dynamics GP (Cards > Purchasing > Vendor). 2. Assign that item to that vendor using the Item Vendors Maintenance window (Cards > Inventory > Vendors). You also need to perform the above steps if you selected an item that is not currently assigned to the vendor, but both the item and vendor exist within the host system. Checking errors If errors appear for purchase orders sent from technicians, you will see an error code in the Mobile Purchase Order window, which will look like this: econnect error description lookup econnect error code To view the meaning of the error, highlight the error number, then click the lookup next to the econnect Error column, as shown above. 3-11

42 Processing (committing) the PO s When you have reviewed the purchase orders and are confident that they are ready to be committed, you can then process the purchase orders. 1. In the Mobile Purchase Order window, select the purchase order(s) to be processed. 2. Click the Process button. Depending on how many purchase orders are being processed, it may take awhile. After the purchase order is processed, it will be removed from the Mobile Purchase Order window, and moved to the Mobile PO history table (WS3003). You can now review the committed purchase orders in the Purchase Order entry window (Transactions > Purchasing > Purchase Order Entry). These purchase orders will contain a PO Status of "Released." The costs associated with this purchase order will appear in Service Management as "committed costs" on the service invoice. Setting up custom task code responses You can create custom task responses that coincide with your own reasons/ responses when completing a service call. The responses you create will appear in a drop-down list on the MobileTEC device (laptop and pocket PC) when the appropriate task is selected for a call. Custom responses are associated with task codes. 1. Choose Microsoft Dynamics GP > Tools > Setup > Service Management > Lookup Setup > Tasks > Task Codes. The Task Code Setup window opens. 2. Select a Task Code. 3-12

43 3. In the Response Type field, select Drop Down List. 4. Click the Responses button that appears at the top of the window. 5. Click OK to save the Task Code Setup window The Dropdown Task Response Setup window opens. 3-13

44 6. Enter a Response Value and click Save. The response appears in the list at the bottom of the window. Enter additional response values as needed. 7. When finished, close the Drop Down Task Response Setup window and save the Task Code Setup window. 3-14

45 Sending a note to a MobileTEC technician You can send service call notes to a technician in the field. Conversely, a technician can send his/her own note, or add to an existing note, back to the host. 1. Choose Cards > Service Management > Service Manager. 2. Select a customer. 3. Choose History and select a service call. 4. Double-click the note icon in the Service Call ID field. The Service Management Notes window opens. 5. Click Mobile Note. The word MOBILE fills automatically in the Subject field. 6. Type your note in the box. When finished, click Broadcast to send the note to the MobileTEC technician. When the technician receives the note, he/she can update the note, if necessary, and send it back to the host. 3-15

46 3-16

47 Index Index

48 A ASP.NET, version required 2-17 C configuring MobileTEC Host 2-17 E error codes 3-8 I installing Microsoft Message Queing 2-1 MobileTEC Web Service 2-4 inventory sites, setting up 3-4 M Microsoft Message Queing (MSMQ) definition 1-1 installing 2-1 Mobile Inventory report 3-8 P private queues (MSMQ) about 1-2 verifying security 2-18 processing transactions for items 3-6 purchase orders, processing 3-9 R responses, task codes 3-12 S scheduled task, creating for TimeTrack transactions 2-14 system requirements 2-1 T task code responses, setting up 3-12 U unbilled transactions setting up in TimeTrack 3-3 Index - 2