WTS Help - User contributions [en]

Importing Data

2014-09-02T22:55:24Z

Dgallagher: /* Importing Data */

== Importing Data ==

Data can be imported into WTS as either part of your account's initial set-up or as part of a recurring administrative task to keep data synchronized with a back-end system.

All Imports are handled via a CSV (Comma Separated Values) file.

Importing Recipients

The CSV File needs a header listing the column names.
There should be the same number of columns throughout the file as mentioned in the header.

The Data is mapped as follows:

(Where there are multiple Accepted fields, they will be concatenated and comma delimited in the order shown here.)

<table width="80%" border="1" cellspacing="0" cellpadding="4px">

<tr>
<th width="30%">WTS Field</th><th colspan = "4">Accepted Fields</th><th width="10%">Mandatory</th>
</tr>

<tr>
<td rowspan="4">Import Code

(A code used to uniquely identify a recipient between systems. Must be unique) </td><td colspan="4">Id</td><td rowspan="4">No- although advisable</td>
</tr>
<tr>
<td colspan="4">Code</td>
</tr>
<tr>
<td colspan="4">RecipientNo</td>
</tr>
<tr>
<td colspan="4">EmployeeNo</td>
</tr>
<tr>
<td rowspan="3">Assigned Code (A code assigned to a badge or other identifying item)</td><td colspan="4">BadgeId</td><td rowspan="3">No- Used on Handheld for Rapid Package Retrieval</td>
</tr>
<tr>
<td colspan="4">CurrentCode</td>
</tr>
<tr>
<td colspan="4">SecurityCode</td>
</tr>
<tr>
<td rowspan="3">Location Code

(A code to uniquely identify locations between systems. Used to find recipient locations during the import.)</td><td colspan="4">LocId</td><td rowspan="3">No- although advisable</td>
</tr>
<tr>
<td colspan="4">LocCode</td>
</tr>
<tr>
<td colspan="4">LocationNo</td>
</tr>

<tr>
<td rowspan="2">Building Code

(A code to uniquely identify buildings between systems. Used as an alternative to the LocationNo field. Use in conjunction with Recipient Room and Recipient City to automatically generate the Location Tree during the import.)</td><td colspan="4">BuildingCode</td><td rowspan="2">No- although advisable for tree import.</td>
</tr>
<tr>
<td colspan="4">OfficeCode</td>
</tr>

<tr>
<td rowspan="2">Recipient Name</td><td colspan="4">Name</td><td rowspan="2">Yes</td>
</tr>
<tr>
<td colspan="2">Lastname</td><td colspan="2">Firstname</td>
</tr>
<tr>
<td rowspan="2">Recipient Location</td><td colspan="4">Location</td><td rowspan="2">Yes</td>
</tr>
<tr>
<td colspan="4">Site</td>
</tr>
<tr><td rowspan="3">Location Description</td><td colspan="4">Locdesc</td><td rowspan="3">No</td></tr>
<tr><td colspan="4">Description</td></tr>
<tr><td colspan="4">Desc</td></tr>
<tr>
<td rowspan="3">Recipient Phone</td><td colspan="4">Phone</td><td rowspan="3">No</td>
</tr>
<tr>
<td colspan="4">Extention</td>
</tr>
<tr>
<td colspan="4">Ext</td>
</tr>
<tr>
<td rowspan="3">Recipient Cell Phone</td><td colspan="4">Cell</td><td rowspan="3">No</td>
</tr>
<tr>
<td colspan="4">Cellphone</td>
</tr>
<tr>
<td colspan="4">Mobile</td>
</tr>
<tr>
<td >Send SMS - Allows fine tuning of SMS system per recipient. (Only used if Cell phone is provided. If Send SMS field is not included in the file, WTS Defaults to 1.)</td><td colspan="4">SendSMS</td><td>No</td>
</tr>
<tr>
<td >Recipient Fax</td><td colspan="4">Fax</td><td>No</td>
</tr>
<tr>
<td >Recipient Room</td><td colspan="4">AltRoom</td><td>No</td>
</tr>
<tr>
<td rowspan="2">Recipient Room (combined w/ location)</td><td colspan="4">Room</td><td rowspan="2">No</td>
</tr>

<tr>
<td colspan="4">Office</td>
</tr>
<tr>
<td rowspan="1">Recipient Address</td><td colspan="4">Address</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="1">Recipient Address - Line 2</td><td colspan="4">Address2</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="1">Recipient City</td><td colspan="4">City</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="2">Recipient State</td><td colspan="4">State</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">County</td>
</tr>
<tr>
<td rowspan="2">Recipient Zip/Postcode</td><td colspan="4">Zip</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Postcode</td>
</tr>
<tr>
<td >Recipient Email</td><td colspan="4">Email</td><td>No</td>
</tr>
<tr>
<td >Send Email- Allows fine tuning of Email system per recipient. (Only used if Email Address is provided. If Send Email field is not included in the file, WTS Defaults to 1.)</td><td colspan="4">SendEmail</td><td>No</td>
</tr>
<tr>
<td >Recipient Company</td><td colspan="4">Company</td><td>No</td>
</tr>
<tr>
<td rowspan="2">Mailbox Number</td><td colspan="4">Mailbox</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Mailboxno</td>
</tr>
<tr>
<td rowspan="2">Classification</td><td colspan="4">Classification</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Type</td>
</tr>
<tr>
<td rowspan="2">Department</td><td colspan="4">Dept</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Department</td>
</tr>
<tr>
<td rowspan="1">Costcenter</td><td colspan="4">Costcenter</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="2">Forwarding Label (WTS will use the Forwarding Label instead of the WTS Label. Use 1 to use the forwarding label or set it to 0 or blank)</td><td colspan="4">ForwardingLabel</td><td rowspan="2">No</td>
</tr>
</table>

'''Existing recipients will be updated where possible.'''

If the '''import code''' is supplied, the recipient can be accurately matched.
The import code can be anything, as long as it's unique.
It can be an employee number or any other type of unique identifying code. This is important for ensuring that changes to names are respected.

If the Import Code is not supplied, the existing recipient is matched based on their '''name and location''' (to prevent 2 John Smiths at 2 locations being confused as the same person).
This is not as accurate as using an Import Code and may lead to duplicates where someone has moved location or changed their name.

The '''Location Code''' is used to find locations previously imported or added into the WTS system.

In most cases, the location list will have been massaged into a very useful tree structure and the recipients lovingly placed in their correct locations.
By using the import codes for both recipient and location, the existing tree structure is preserved and recipients are moved to their new locations.

Any Locations not found within the Delivery locations list will be added during the import. However, they will not be placed in any particular branch of the location tree, this will have to be done manually after the import. However, if the location was added using an import code, their position in the tree will be retained during future imports.

There is a way to import the location tree during the recipient import.
By supplying a Building Code, a Room No and a City, the Importer will create the relevant tree structure when creating the locations.

This example import will achieve this.
<div style="border:1px solid #aaaaaa;background-color:#eeeeee;padding:4px;">
'''Code,BuildingCode,Site,LastName,FirstName,Extension,Room,,Company,City,State'''

E0001,CDH,Discovery House,Samson,Dale,0122,31,ACME UK,Cambridge,Cambridgeshire

E0008,CDH,Discovery House,Gibson,Larry,0113,30,ACME UK,Cambridge,Cambridgeshire

E0120,NFH,Fulcrum House,Ekhart,Dean,0148,300,ACME UK,Nottingham,Nottinghamshire

E0023,WSF,Swallow House,Harris,Jason,0123,7,ACME UK ,Wyboston,Bedfordshire

E0025,WSF,Swallow House,Jones,Martin,0123,8,ACME UK,Wyboston,Bedfordshire

E0029,SFH,Safford Hall,Beird,Andrew,120,105,ACME UK,Stone,Staffordshire
</div>

This will create the following tree

*Cambridge
**Discovery House
***Discovery House #30
***Discovery House #31
*Nottingham
**Fulcrum House
***Fulcrum House #300
*Wyboston
**Swallow House
***Swallow House #7
***Swallow House #8

[[Main_Page|Back to Main Page]]

Importing Data

2014-09-02T22:48:07Z

Dgallagher: /* Importing Data */

== Importing Data ==

Data can be imported into WTS as either part of your account's initial set-up or as part of a recurring administrative task to keep data synchronized with a back-end system.

All Imports are handled via a CSV (Comma Separated Values) file.

Importing Recipients

The CSV File needs a header listing the column names.
There should be the same number of columns throughout the file as mentioned in the header.

The Data is mapped as follows:

(Where there are multiple Accepted fields, they will be concatenated and comma delimited in the order shown here.)

<table width="80%" border="1" cellspacing="0" cellpadding="4px">

<tr>
<th width="30%">WTS Field</th><th colspan = "4">Accepted Fields</th><th width="10%">Mandatory</th>
</tr>

<tr>
<td rowspan="4">Import Code

(A code used to uniquely identify a recipient between systems. Must be unique) </td><td colspan="4">Id</td><td rowspan="4">No- although advisable</td>
</tr>
<tr>
<td colspan="4">Code</td>
</tr>
<tr>
<td colspan="4">RecipientNo</td>
</tr>
<tr>
<td colspan="4">EmployeeNo</td>
</tr>
<tr>
<td rowspan="3">Assigned Code (A code assigned to a badge or other identifying item)</td><td colspan="4">BadgeId</td><td rowspan="3">No- Used on Handheld for Rapid Package Retrieval</td>
</tr>
<tr>
<td colspan="4">CurrentCode</td>
</tr>
<tr>
<td colspan="4">SecurityCode</td>
</tr>
<tr>
<td rowspan="3">Location Code

(A code to uniquely identify locations between systems. Used to find recipient locations during the import.)</td><td colspan="4">LocId</td><td rowspan="3">No- although advisable</td>
</tr>
<tr>
<td colspan="4">LocCode</td>
</tr>
<tr>
<td colspan="4">LocationNo</td>
</tr>

<tr>
<td rowspan="2">Building Code

(A code to uniquely identify buildings between systems. Used as an alternative to the LocationNo field. Use in conjunction with Recipient Room and Recipient City to automatically generate the Location Tree during the import.)</td><td colspan="4">BuildingCode</td><td rowspan="2">No- although advisable for tree import.</td>
</tr>
<tr>
<td colspan="4">OfficeCode</td>
</tr>

<tr>
<td rowspan="2">Recipient Name</td><td colspan="4">Name</td><td rowspan="2">Yes</td>
</tr>
<tr>
<td colspan="2">Lastname</td><td colspan="2">Firstname</td>
</tr>
<tr>
<td rowspan="2">Recipient Location</td><td colspan="4">Location</td><td rowspan="2">Yes</td>
</tr>
<tr>
<td colspan="4">Site</td>
</tr>
<tr><td rowspan="3">Location Description</td><td colspan="4">Locdesc</td><td rowspan="3">No</td></tr>
<tr><td colspan="4">Description</td></tr>
<tr><td colspan="4">Desc</td></tr>
<tr>
<td rowspan="3">Recipient Phone</td><td colspan="4">Phone</td><td rowspan="3">No</td>
</tr>
<tr>
<td colspan="4">Extention</td>
</tr>
<tr>
<td colspan="4">Ext</td>
</tr>
<tr>
<td rowspan="3">Recipient Cell Phone</td><td colspan="4">Cell</td><td rowspan="3">No</td>
</tr>
<tr>
<td colspan="4">Cellphone</td>
</tr>
<tr>
<td colspan="4">Mobile</td>
</tr>
<tr>
<td >Send SMS - Allows fine tuning of SMS system per recipient. (Only used if Cell phone is provided. If Send SMS field is not included in the file, WTS Defaults to 1.)</td><td colspan="4">SendSMS</td><td>No</td>
</tr>
<tr>
<td >Recipient Fax</td><td colspan="4">Fax</td><td>No</td>
</tr>
<tr>
<td >Recipient Room</td><td colspan="4">AltRoom</td><td>No</td>
</tr>
<tr>
<td rowspan="2">Recipient Room (combined w/ location)</td><td colspan="4">Room</td><td rowspan="2">No</td>
</tr>

<tr>
<td colspan="4">Office</td>
</tr>
<tr>
<td rowspan="1">Recipient Address</td><td colspan="4">Address</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="1">Recipient Address - Line 2</td><td colspan="4">Address2</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="1">Recipient City</td><td colspan="4">City</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="2">Recipient State</td><td colspan="4">State</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">County</td>
</tr>
<tr>
<td rowspan="2">Recipient Zip/Postcode</td><td colspan="4">Zip</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Postcode</td>
</tr>
<tr>
<td >Recipient Email</td><td colspan="4">Email</td><td>No</td>
</tr>
<tr>
<td >Send Email- Allows fine tuning of Email system per recipient. (Only used if Email Address is provided. If Send Email field is not included in the file, WTS Defaults to 1.)</td><td colspan="4">SendEmail</td><td>No</td>
</tr>
<tr>
<td >Recipient Company</td><td colspan="4">Company</td><td>No</td>
</tr>
<tr>
<td rowspan="2">Mailbox Number</td><td colspan="4">Mailbox</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Mailboxno</td>
</tr>
<tr>
<td rowspan="2">Classification</td><td colspan="4">Classification</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Type</td>
</tr>
<tr>
<td rowspan="2">Department</td><td colspan="4">Dept</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Department</td>
</tr>
<tr>
<td rowspan="2">Costcenter</td><td colspan="4">Costcenter</td><td rowspan="2">No</td>
</tr>
<tr>
<td rowspan="2">Forwarding Label</td><td colspan="4">Forwardinglabel</td><td rowspan="2">No</td>
</tr>
</table>

'''Existing recipients will be updated where possible.'''

If the '''import code''' is supplied, the recipient can be accurately matched.
The import code can be anything, as long as it's unique.
It can be an employee number or any other type of unique identifying code. This is important for ensuring that changes to names are respected.

If the Import Code is not supplied, the existing recipient is matched based on their '''name and location''' (to prevent 2 John Smiths at 2 locations being confused as the same person).
This is not as accurate as using an Import Code and may lead to duplicates where someone has moved location or changed their name.

The '''Location Code''' is used to find locations previously imported or added into the WTS system.

In most cases, the location list will have been massaged into a very useful tree structure and the recipients lovingly placed in their correct locations.
By using the import codes for both recipient and location, the existing tree structure is preserved and recipients are moved to their new locations.

Any Locations not found within the Delivery locations list will be added during the import. However, they will not be placed in any particular branch of the location tree, this will have to be done manually after the import. However, if the location was added using an import code, their position in the tree will be retained during future imports.

There is a way to import the location tree during the recipient import.
By supplying a Building Code, a Room No and a City, the Importer will create the relevant tree structure when creating the locations.

This example import will achieve this.
<div style="border:1px solid #aaaaaa;background-color:#eeeeee;padding:4px;">
'''Code,BuildingCode,Site,LastName,FirstName,Extension,Room,,Company,City,State'''

E0001,CDH,Discovery House,Samson,Dale,0122,31,ACME UK,Cambridge,Cambridgeshire

E0008,CDH,Discovery House,Gibson,Larry,0113,30,ACME UK,Cambridge,Cambridgeshire

E0120,NFH,Fulcrum House,Ekhart,Dean,0148,300,ACME UK,Nottingham,Nottinghamshire

E0023,WSF,Swallow House,Harris,Jason,0123,7,ACME UK ,Wyboston,Bedfordshire

E0025,WSF,Swallow House,Jones,Martin,0123,8,ACME UK,Wyboston,Bedfordshire

E0029,SFH,Safford Hall,Beird,Andrew,120,105,ACME UK,Stone,Staffordshire
</div>

This will create the following tree

*Cambridge
**Discovery House
***Discovery House #30
***Discovery House #31
*Nottingham
**Fulcrum House
***Fulcrum House #300
*Wyboston
**Swallow House
***Swallow House #7
***Swallow House #8

[[Main_Page|Back to Main Page]]

Importing Senders

2014-09-02T22:44:04Z

Dgallagher: Created page with "== Importing Senders== Senders can be imported into WTS as either part of your account's initial set-up or when needed. Sender Imports are handled via a CSV (Comma Separated Va..."

== Importing Senders==

Senders can be imported into WTS as either part of your account's initial set-up or when needed.

Sender Imports are handled via a CSV (Comma Separated Values) file.

Importing Senders

The CSV File needs a header listing the column names.
There should be the same number of columns throughout the file as mentioned in the header.

The Data is mapped as follows:

(Where there are multiple Accepted fields, they will be concatenated and comma delimited in the order shown here.)

<table width="80%" border="1" cellspacing="0" cellpadding="4px">

<tr>
<th width="30%">WTS Field</th><th colspan = "4">Accepted Fields</th><th width="10%">Mandatory</th>
</tr>

<tr>
<td rowspan="3">Sender Name

</td><td colspan="4">Sender</td><td rowspan="3">Yes</td>
</tr>
<tr>
<td colspan="4">SenderName</td>
</tr>
<tr>
<td colspan="4">Name</td>
</tr>
<tr>
<td rowspan="1">Address Line 1

</td><td colspan="4">Address</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="1">Address Line 2

</td><td colspan="4">Address2</td><td rowspan="1">No</td>
</tr>

<tr>
<td rowspan="1">City</td><td colspan="4">City</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="2">State</td><td colspan="4">State</td><td rowspan="2">Yes</td>
</tr>
<tr>
<td colspan="4">County</td>
</tr>
<tr><td rowspan="2">Zipcode/Postal Code</td><td colspan="4">Zip</td><td rowspan="2">No</td></tr>
<tr>
<td colspan="4">Postcode</td>
</tr>
<tr>
<td rowspan="1">Company</td><td colspan="4">Company</td><td rowspan="1">No</td>
</tr>
<tr>
<td >Email</td><td colspan="4">Email</td><td>No</td>
</tr>
<tr>
<td rowspan="3">Cell Phone</td><td colspan="4">Cell</td><td rowspan="3">No</td>
</tr>
<tr>
<td colspan="4">Mobile</td>
</tr>
<tr>
<td colspan="4">Cellphone</td>
</tr>

</table>

[[Main_Page|Back to Main Page]]

Main Page

2014-09-02T20:39:25Z

Dgallagher: /* Welcome to the Help Pages */

== Welcome to the Help Pages ==
In here you can find answers to most questions you might have.
<table cellspacing="0" width="100%">
<tr style="background: #eef">
<td style="vertical-align:top; border-top: 1px solid #ccf; border-left: 1px solid #ccf; border-right: 1px solid #ccf; border-bottom: 1px solid #ccf; padding: 1em;" >

<table cellspacing="0" width="100%">
<tr style="background: #eef">
<td width="33%" valign="top" >'''WTS Main Site'''
* [[About]]
* [[The Dashboard]]
* [[Main Toolbar]]
* [[Support]]
* [[Users]]
* [[Package Tracking]]
* [[Pickups]]
* [[Test]]

</td>
<td width="33%" valign="top" >'''Administration'''
* [[Recipients]]
* [[Storage Locations]]
* [[Delivery Locations]]
* [[Alerts]]
* [[Customizing Fields and Names]]
* [[Managing Receipt Statuses]]
* [[Route Administration]]
* [[Location Tree Administration]]
* [[Modifying Document Templates]]
* [[Receipt Status Management]]
* [[Scheduling Status Changes]]
</td>
<td width="33%" valign="top" >'''Technical Information'''
* [[Importing Data]]
* [[Importing Senders]]
* [[Supported Device Drivers]]
* [[Install Checklist]]
* [[UPS Quantum Setup]]
</td>
</tr>
<tr style="background: #eef"><td valign="top" >
'''Mobile Device Hardware Help'''
* [[How To Program Handheld]]
* [[Connecting The 4 Slot Cradle To Your Network]]
* [[Cradle IP Address]]
* [[Cradle MAC Address]]

</td>
<td valign="top" >

'''How To...'''
* [[How to change your password]]
* [[How to unlock another users account]]
* [[Receiving]]
* [[How to Execute Reports]]
* [[How to Sort Columns]]
* [[Status Change and Delivery]]
* [[How to Verify a Package]]
* [[How to Collect a Signature]]
* [[How to handle a non-signature delivery]]
</td>
<td valign="top" >
''''''
* [[How to record delivery to a different location]]
* [[How to change the status of a package]]
* [[How to deliver a package multiple times]]
* [[How to Receive a package]]
* [[How to Receive Multiple Packages]]
* [[How to organize your dashboard]]
* [[How to create alerts]]
* [[How to Verify Packages Received]]
* [[How to use the Reporting Web Service]]
</td>
</tr>

<tr style="background: #eef"><td valign="top" >
'''Hardware Manuals'''
* [[Motorola MC55 User Guide]]
* [[Motorola MC55 Specifications]]
* [[Motorola MC65 User Guide]]
* [[Motorola MC65 Specifications]]
* [[Motorola LI4278 Bluetooth Barcode Scanner]]
* [[Topaz 1 x 5 Signature Pad Specification]]

</td>
<td valign="top" >

'''Trouble Shooting & FAQ'''
* [[Display Issues]]
* [[Printing]]
* [[Synchronizing]]
* [[SAYT Lists]]
* [[Browser Issues]]
* [[Scanning Barcodes]]
* [[Network Issues]]
* [[Java Requirements]]
* [[Cradle Issues]]
* [[Slow Label Printing]]

</td>
<td valign="top" >

</td>
</tr>

</table>

Importing Data

2014-09-02T20:38:26Z

Dgallagher: /* Importing Data */

== Importing Data ==

Data can be imported into WTS as either part of your account's initial set-up or as part of a recurring administrative task to keep data synchronized with a back-end system.

All Imports are handled via a CSV (Comma Separated Values) file.

Importing Recipients

The CSV File needs a header listing the column names.
There should be the same number of columns throughout the file as mentioned in the header.

The Data is mapped as follows:

(Where there are multiple Accepted fields, they will be concatenated and comma delimited in the order shown here.)

<table width="80%" border="1" cellspacing="0" cellpadding="4px">

<tr>
<th width="30%">WTS Field</th><th colspan = "4">Accepted Fields</th><th width="10%">Mandatory</th>
</tr>

<tr>
<td rowspan="4">Import Code

(A code used to uniquely identify a recipient between systems. Must be unique) </td><td colspan="4">Id</td><td rowspan="4">No- although advisable</td>
</tr>
<tr>
<td colspan="4">Code</td>
</tr>
<tr>
<td colspan="4">RecipientNo</td>
</tr>
<tr>
<td colspan="4">EmployeeNo</td>
</tr>
<tr>
<td rowspan="3">Assigned Code (A code assigned to a badge or other identifying item)</td><td colspan="4">BadgeId</td><td rowspan="3">No- Used on Handheld for Rapid Package Retrieval</td>
</tr>
<tr>
<td colspan="4">CurrentCode</td>
</tr>
<tr>
<td colspan="4">SecurityCode</td>
</tr>
<tr>
<td rowspan="3">Location Code

(A code to uniquely identify locations between systems. Used to find recipient locations during the import.)</td><td colspan="4">LocId</td><td rowspan="3">No- although advisable</td>
</tr>
<tr>
<td colspan="4">LocCode</td>
</tr>
<tr>
<td colspan="4">LocationNo</td>
</tr>

<tr>
<td rowspan="2">Building Code

(A code to uniquely identify buildings between systems. Used as an alternative to the LocationNo field. Use in conjunction with Recipient Room and Recipient City to automatically generate the Location Tree during the import.)</td><td colspan="4">BuildingCode</td><td rowspan="2">No- although advisable for tree import.</td>
</tr>
<tr>
<td colspan="4">OfficeCode</td>
</tr>

<tr>
<td rowspan="2">Recipient Name</td><td colspan="4">Name</td><td rowspan="2">Yes</td>
</tr>
<tr>
<td colspan="2">Lastname</td><td colspan="2">Firstname</td>
</tr>
<tr>
<td rowspan="2">Recipient Location</td><td colspan="4">Location</td><td rowspan="2">Yes</td>
</tr>
<tr>
<td colspan="4">Site</td>
</tr>
<tr><td rowspan="3">Location Description</td><td colspan="4">Locdesc</td><td rowspan="3">No</td></tr>
<tr><td colspan="4">Description</td></tr>
<tr><td colspan="4">Desc</td></tr>
<tr>
<td rowspan="3">Recipient Phone</td><td colspan="4">Phone</td><td rowspan="3">No</td>
</tr>
<tr>
<td colspan="4">Extention</td>
</tr>
<tr>
<td colspan="4">Ext</td>
</tr>
<tr>
<td rowspan="3">Recipient Cell Phone</td><td colspan="4">Cell</td><td rowspan="3">No</td>
</tr>
<tr>
<td colspan="4">Cellphone</td>
</tr>
<tr>
<td colspan="4">Mobile</td>
</tr>
<tr>
<td >Send SMS - Allows fine tuning of SMS system per recipient. (Only used if Cell phone is provided. If Send SMS field is not included in the file, WTS Defaults to 1.)</td><td colspan="4">SendSMS</td><td>No</td>
</tr>
<tr>
<td >Recipient Fax</td><td colspan="4">Fax</td><td>No</td>
</tr>
<tr>
<td >Recipient Room</td><td colspan="4">AltRoom</td><td>No</td>
</tr>
<tr>
<td rowspan="2">Recipient Room (combined w/ location)</td><td colspan="4">Room</td><td rowspan="2">No</td>
</tr>

<tr>
<td colspan="4">Office</td>
</tr>
<tr>
<td rowspan="1">Recipient Address</td><td colspan="4">Address</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="1">Recipient Address - Line 2</td><td colspan="4">Address2</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="1">Recipient City</td><td colspan="4">City</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="2">Recipient State</td><td colspan="4">State</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">County</td>
</tr>
<tr>
<td rowspan="2">Recipient Zip/Postcode</td><td colspan="4">Zip</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Postcode</td>
</tr>
<tr>
<td >Recipient Email</td><td colspan="4">Email</td><td>No</td>
</tr>
<tr>
<td >Send Email- Allows fine tuning of Email system per recipient. (Only used if Email Address is provided. If Send Email field is not included in the file, WTS Defaults to 1.)</td><td colspan="4">SendEmail</td><td>No</td>
</tr>
<tr>
<td >Recipient Company</td><td colspan="4">Company</td><td>No</td>
</tr>
<tr>
<td rowspan="2">Mailbox Number</td><td colspan="4">Mailbox</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Mailboxno</td>
</tr>
<tr>
<td rowspan="2">Classification</td><td colspan="4">Classification</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Type</td>
</tr>
<tr>
<td rowspan="2">Department</td><td colspan="4">Dept</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Department</td>
</tr>
<tr>
<td rowspan="2">Costcenter</td><td colspan="4">Costcenter</td><td rowspan="2">No</td>
</tr>

</table>

'''Existing recipients will be updated where possible.'''

If the '''import code''' is supplied, the recipient can be accurately matched.
The import code can be anything, as long as it's unique.
It can be an employee number or any other type of unique identifying code. This is important for ensuring that changes to names are respected.

If the Import Code is not supplied, the existing recipient is matched based on their '''name and location''' (to prevent 2 John Smiths at 2 locations being confused as the same person).
This is not as accurate as using an Import Code and may lead to duplicates where someone has moved location or changed their name.

The '''Location Code''' is used to find locations previously imported or added into the WTS system.

In most cases, the location list will have been massaged into a very useful tree structure and the recipients lovingly placed in their correct locations.
By using the import codes for both recipient and location, the existing tree structure is preserved and recipients are moved to their new locations.

Any Locations not found within the Delivery locations list will be added during the import. However, they will not be placed in any particular branch of the location tree, this will have to be done manually after the import. However, if the location was added using an import code, their position in the tree will be retained during future imports.

There is a way to import the location tree during the recipient import.
By supplying a Building Code, a Room No and a City, the Importer will create the relevant tree structure when creating the locations.

This example import will achieve this.
<div style="border:1px solid #aaaaaa;background-color:#eeeeee;padding:4px;">
'''Code,BuildingCode,Site,LastName,FirstName,Extension,Room,,Company,City,State'''

E0001,CDH,Discovery House,Samson,Dale,0122,31,ACME UK,Cambridge,Cambridgeshire

E0008,CDH,Discovery House,Gibson,Larry,0113,30,ACME UK,Cambridge,Cambridgeshire

E0120,NFH,Fulcrum House,Ekhart,Dean,0148,300,ACME UK,Nottingham,Nottinghamshire

E0023,WSF,Swallow House,Harris,Jason,0123,7,ACME UK ,Wyboston,Bedfordshire

E0025,WSF,Swallow House,Jones,Martin,0123,8,ACME UK,Wyboston,Bedfordshire

E0029,SFH,Safford Hall,Beird,Andrew,120,105,ACME UK,Stone,Staffordshire
</div>

This will create the following tree

*Cambridge
**Discovery House
***Discovery House #30
***Discovery House #31
*Nottingham
**Fulcrum House
***Fulcrum House #300
*Wyboston
**Swallow House
***Swallow House #7
***Swallow House #8

[[Main_Page|Back to Main Page]]