Order Confirmation Page Not Displayed When Using Single Page Checkout and External Payment

This topic applies to

Applies to

Vinson | Elbrus

In some implementations of the Vinson and Elbrus releases of SuiteCommerce Advanced, the Order Confirmation Page is not displayed when using one page checkout with an external payment system.

To implement this patch, create a custom module to override SC.Checkout.Configuration.Steps.OPC.js, which is part of the CheckoutApplication@2.2.0 module. You can download the code samples described in this procedure here: CheckoutApplication.Extension@1.0.0 VinsonCodeSamples.zip

Note

In general, NetSuite best practice is to extend JavaScript using the JavaScript prototype object. This improves the chances that your customizations continue to work when migrating to a newer version of SuiteCommerce Advanced. However, this patch requires you to modify a file in a way that you cannot extend, and therefore requires you to use a custom module to override the existing module file. For more information, see Customize and Extend Core SuiteCommerce Advanced Modules.


Step 1: Create the Override File

  1. Create an extensions directory to store your custom module. Depending on your implementation, this directory might already exist.

  2. Within the extension directory, create a directory for a new custom module with a name similar to the module being customized.

    For example, create Modules/extensions/CheckoutApplication.Extension@1.0.0.

  3. In your new CheckoutApplicationExtension@1.0.0 module directory, create a directory called JavaScript.

    For example: Modules/extensions/CheckoutApplication.Extension@1.0.0/JavaScript

  4. Copy the following source file and paste into the correct location:

    Copy This File:

    Place a Copy Here:

    Modules/suitecommerce/CheckoutApplication@X.Y.Z/JavaScript/ SC.Checkout.Configuration.Steps.OPC.js

    Modules/extensions/CheckoutApplication.Extension@1.0.0/JavaScript

    In this example, X.Y.Z represents the version of the module in your implementation of SuiteCommerce Advanced.

  5. Open your new copy of SC.Checkout.Configuration.Steps.OPC.js and locate the following line:

    , [OrderWizardModulePaymentMethodSelector, {record_type:'salesorder', preventDefault: true}]
  6. Replace this line with the following code:

    , [OrderWizardModulePaymentMethodSelector, {record_type:'salesorder', prevent_default: true}]
  7. Save the file.

Step 2: Prepare the Developer Tools For Your Customization

  1. Open your Modules/extensions/CheckoutApplication.Extension@1.0.0 directory.

  2. Create a file in this directory and name it ns.package.json.

    Modules/extensions/CheckoutApplication.Extension@1.0.0/ns.package.json

  3. Paste the following code in your new ns.package.json file:

    { "gulp": { "javascript": [ "JavaScript/*.js" ] }, "overrides": { "suitecommerce/CheckoutApplication@2.2.0/JavaScript/SC.Checkout.Configuration.Steps.OPC.js" : "JavaScript/SC.Checkout.Configuration.Steps.OPC.js" } }

    Important

    You must replace the string X.Y.Z with the version of the module in your implementation of SuiteCommerce Advanced.


  4. Open the distro.json file. This file is located in your root directory.

  5. Add your custom module to the modules object.

    Your code should look similar to the following example:

    { "name": "SuiteCommerce Advanced Vinson Release", "version": "2.0", "isSCA": true, "buildToolsVersion": "1.2.1", "folders": { "modules": "Modules", "suitecommerceModules": "Modules/suitecommerce", "extensionsModules": "Modules/extensions", "thirdPartyModules": "Modules/third_parties", "distribution": "LocalDistribution", "deploy": "DeployDistribution" }, "modules": { "extensions/CheckoutApplication.Extension": "1.0.0", "suitecommerce/Account": "2.2.0", ...

    This ensures that the Gulp tasks include your module when you deploy.  In this example, the custom modules are added at the beginning of the list of modules. However, you can add the modules anywhere in the modules object. The order of precedence in this list does not matter.

  6. Save the distro.json file.

Step 3: Test and Deploy Your Customization

  1. Test your source code customizations on a local server (see SCA on a Local Server) or deploy them to your NetSuite account (see Deploy to NetSuite). If you are currently running SCA on a local server, your changes should appear on your local site immediately.

  2. Confirm your results.

    Upon successful deployment, the Order Confirmation Page is displayed after completing an order when using one page checkout with an external payment system.

Related Topics