VendorConnect Document Management Setup

These are the setup instructions required for Document Management through Third Party Applications, such as Arrivy and the AtlasNet Document Download Integration. (For Vendor Developers, see additional information under VendorConnect Document Management Setup.)

1. Update Xml System Setup record.

2. Create a second VendorConnect record.

3. Map Document Types to the Xml System…..

STEP 1: Update Xml System Setup record

Setup: MoversSuite Administration > Administration > Xml System Setup

From the Third Party Application’s Xml System Setup record, click Click here to add a new XML System Data Type Map.

This opens the Add XML System Date Type Map dialog. Enter information according to the image and table below:

STEP 2: Create a second VendorConnect record

Setup: MoversSuite Administration > MoversConnect > VendorConnect Setup

Since only one Xml System Data Type Map Name can be assigned per record, a second Vendor Connect record is needed for their documents. Choose the VendorConnect Vendor. For Xml System Data Type, choose the one matching the Vendor Name Document Notification. 

From Click here to add a new Branch Item, add the same set of Branches (Branch Items) and they MUST use the very same External Code(s) set as the External Codes used on the first record – the Order Information record.  Vendors expect the External Codes to be IDENTICAL between the branches as shown on the two separate VendorConnect Setup records.  

For example, Arrivy should have two VendorConnect Setup records: one with the Xml System Data Type set to Arrivy Order Information and the second records with the Xml System Data Type set to Arrivy Document Notifications. The Branch Items and External Codes added to each record are exactly the same.

NOTE: Users should not change their existing vendor connect record for their “Arrivy Order Information”.  This one uses an Xml System Data Type Map name that uses an Xml System Data Type of “Order Information”.

STEP 3:

Setup: MoversSuite Administration > Document Management > Document Type Setup

Since document types are required for MoversSuite documents, MoversSuite users need to map those codes using the Xml Interface associated to the XML System that their VendorConnect Setup record with the Document Notification (XML System Data Type Map) Name is associated to (from Step 2 in these instructions.)

Document types for VendorConnect vendors are optional.  The VendorConnect Vendor may or they may not have them.  Arrivy is a vendor that does not have them, and they have no plans whatsoever of supporting; however, Atlas does support document types.  So, depending upon if the vendor has document types or not, then follow one of the following choices:

Vendor DOES NOT support document types:

In this case, Engineering will assign a single, four character code for that vendor - which will appear on all documents from that vendor. MoversSuite users need to map this one external code to one of their existing document types or they can create a new document type just for that vendor’s documents. For Arrivy, that code is ARVD.  For Atlas, that code is ADOC.

Vendor DOES support document types:

The vendor would need to provide a list of their document type codes that they would send to us in their document notifications. MoversSuite users would need to map those codes to their document types as they see fit.

VendorConnect vendors that require a Bearer authentication token:  Arrivy does not use a Bearer authentication token so this would only apply to those vendors that require such a token (i.e. Atlas).  In Admin, add an External API for the appropriate vendor.