Overview

THIS ARTICLE IS ONLY FOR CUSTOMERS USING THE BUNDLE "PACEJET SHIPPING FOR NETSUITE" THAT HAVE SUITESCRIPT 2.0 SCRIPTS ENABLED. Most Pacejet customers are currently using Pacejet's SuiteScripts 1.0 scripts, and the information provided below does not apply to that environment. If you are unsure, please contact your Pacejet Representative.

You can link to the different articles using the navigation bar on the left.

Once you have configured the API Version 2.0 Scripts (see NETSUITE UPGRADE: 3 of 4. Configuring the 2.0 Scripts ), proceed with the steps below to deploy them.

IMPORTANT! Proceeding with the steps below commits your NetSuite environment to using the Pacejet shipping for NetSuite 2.0

The following steps show you how to deploy the API Version 2.0 scripts. After these scripts are deployed, you are ready to use the scripts in the Pacejet center.

This process requires two steps:

1. Undeploy the API 1.0 scripts

2. Deploy the API 2.0 scripts

Undeploy the API Version 1.0 Scripts

The following steps show you how to undeploy the API 1.0 scripts to prepare your environment for the version 2.0 scripts.

IMPORTANT! When you start undeploying the 1.0 scripts, your system will be down until the following procedures for deploying the 2.0 scripts are completed.

• The Implementation script needs to be run by a Pacejet Implementation Specialist
  Note: Now is the time to contact your implementation specialist and have them run the implementation scripts.

• Carrier Classes of Service and Subsidiaries need to be configured.
  This process could take several hours depending on your configuration's complexity.

1. Hover over Customization, Scripting, then click Script Deployments.
   

2. Verify that API Version 1.0 is selected in FILTERS.
   

3. Find all Pacejet Scripts.
   You can click the title of the Script column ()to sort by name.

4. Undeploy everything labeled Pacejet.
   
   

   • Click Edit next to the desired Pacejet script.

   • Unselect DEPLOYED and click Save ( ).
     
     

Do NOT unselect the Deployed checkmark from the Script Deployments list as it does not undeploy the script.

1.0 Scripts That Need To Be Disabled
customdeploy_pacejet_itmflfllmnt_client	Pacejet Item Fulfillment Client Intgrtn
customdeploy_pacejet_itemfulfillment	Pacejet Item Fulfillment Integration
customdeploy_pacejet_purchaseorder	Pacejet Purchase Order Integration
customdeploy_rest_integration	Pacejet REST Integration
customdeploy_pacejet_salesorder	Pacejet Sales Order Integration
customdeploy_pj_notsched	Pacejet Scheduled Updates
customdeploy_pj_sched	Pacejet Scheduled Updates

If your environment includes the Pacejet SPS 1.0 scripts (shown below) do NOT disable them, leave these enabled.

customdeploy_pacejet_spssched	Pacejet SPS Schedule
customdeploy_pacejet_sps_map	Pacejet SPS Update

Deploy the API Version 2.0 Scripts

Now that you have successfully undeployed the API 1.0 Scripts, you can deploy the scripts for API version 2.0. See the directions below.

1. Select Customization, Scripting, Script Deployments (if you haven't already).

2. Change the API VERSION filter to 2.0 and select All under the Script dropdown menu (if needed).
   

3. Sort by the Script column ( ).
   

4. Deploy each of the following scripts (see image above for the script types).
   - Pacejet Integration
   - Pacejet Integration Queue
   - Pacejet Integration Queue Map Reduce
   - Pacejet Integration Restlet
   - Pacejet Integration Suitelet
   - Pacejet Integration Web Hook
   - Pacejet Portlet
   - Pacejet Schedule Integration
   - Pacejet Third Party Client Integration
   - Pacejet Third Party Integration

5. Select Edit on the first Pacejet script and select the Deployed checkbox.
   

6. Click Save ( ).

After you have completed all the necessary steps, proceed to setting up your Pacejet Center. Start at PACEJET CENTER: 1 of 4. Configure Your Pacejet Settings, and complete the steps listed in all four PACEJET CENTER articles.

Top