Connect to FTP account
In order to connect and to copy files into an FTP account, you should install WINSCP software which is free.
https://winscp.net/eng/download.php
Once installed, please open Session menu and click on “New Session” (usually when you open WinSCP, New Session dialog will open automatically )
Nom d’hôte : test.neopostwts.com => UAT / wtscloud.neopost.com => Production
Nom d’utilisateur/Mot de passe : Provided user and password Port is always 22
Once connected, you can copy the file in Import directory. Files in import directory will be processed around midnight and then will be moved to Imported directory so you can check the recipients the next day.
Activate Auto-Import in WTS
In order to activate auto-import in WTS, you need to browse Admin > Import settings and to click on Recipient Auto-Import Settings to open settings. You need to check Use Auto Import in order to activate Auto-Import using FTP.
The next day, you can check import history on the same page by clicking on Import History.
Please note that recipient csv file should exactly follow the format requested in WTS documents (attached file).
Comparing to manual import, auto-import using FTP is less forgiving and an error in csv file would cancel import process and all changes will be rolled back.
I checked CDIT and there are no modifications to be made in order to make auto-import function correctly, so normally a csv file generated by CDIT can be used with FTP Auto- Import.
You will find enclosed an example file that I used to load 3 new recipients in all environments.
List of Available Headers
|
WTS/WTS/WTS-P Import Field |
Required? | Description of Field | Accepted Headers for Import Field |
| Import Code (ID) | Recommend ed | The import code is used to uniquely identify a recipient between systems. It must be unique. It is advisable to use to help prevent duplicate recipients in WTS/WTS-P |
ID Code RecipientNo EmployeeNo |
| Assigned Code | No | The Assigned Code should be used if there is a badge ID identification number associated to the Recipient | BadgeId CurrentCode SecurityCode |
| Building Code | No | The Building Code is used to uniquely identify buildings. If used in conjunction with Recipient Room and Recipient Location/Recipient City, WTS/WTS-P will automatically generate the location tree at import | BuildingCode OfficeCode |
| Recipient Name | Yes | Recipient Name represents the recipient in WTS/WTS-P |
Name Lastname & Firstname (in different columns) |
| Recipient Location Code | Yes | Location Code is required for importing. This is used to find the delivery location of a recipient | LocId LocCode LocationNo |
| Recipient Location | Yes | This data will represent the location of the recipient in WTS/WTS-P | Location Site |
| Recipient Location Description | No | This field is available if additional info is needed for the location | Locdesc Description Desc |
| Recipient Room | No | This field is in case Room is needed to be separate from the location. Works as its own field | Altroom |
| Recipient Phone | No | Recipient Phone is used if a phone number or extension needs to be associated with the recipient. | Phone Extension |
| Recipient Cell Phone | No | This field is used is text messaging is going to be utilized by the customer so WTS/WTS-P can send out the text | Cell CellPhone Mobile |
| Recipient Fax | No | Recipient Fax is used if a fax number needs to be associated to a recipient in the WTS/WTS-P database | fax |
| Recipient Room | No | Associates a room number to a Recipient. It can also be associated with Building Code and Recipient Location/Recipient City. | Room Office |
|
WTS/WTS/WTS-P Import Field |
Required? | Description of Field | Accepted Headers for Import Field |
| Recipient Address | No | Recipient Address is used if it needs to be associated to the recipient in the database | Address |
| Recipient Address Line 2 | No | This is used if Address2 is needed to be associated with the Recipient | Address2 |
| Recipient City | No | Is used if the city needs to be associated with the Recipient in the database | City |
| Recipient State | No | Is used if the state needs to be associated with the Recipient in the database | State |
| Recipient Zip/ Post Code | No | Is used if the postal code needs to be associated with the Recipient in the database | Zip PostCode |
| Recipient Email | No | Recipient email is used if the customer wants to send emails to the recipient during different status setups. | |
| Send Email yes or no | No | If email is used it automatically sets email to be checked to send, this field allows you to control this with either a “1” (send email) or a “0” (do not send email) | SendEmail |
| Recipient Company | No | Is used if it needs to be associated with the Recipient in the database | Company |
| Mailbox Number | No | Mailbox Number is used if Recipients have Mailbox’s associated to them. | Mailbox Mailboxno |
| Classification | No | Classification is used if different grouping needs to be put in place for the Recipients. It can work in conjunction with email so only certain emails send out to certain classifications. | Classification Type |
| Department | No | Department is used to associate a Recipient and can be looked up in the database. | Dept Department |
| Cost Center | No | Cost Center is used to associate to a Recipient and can be looked up in the database. | costcenter |
| Room | No | AltRoom is used as a separate field that does not compound with the location. | AltRoom |
Comments
0 comments
Please sign in to leave a comment.