SuiteCommerce 2018.2: SCDeployer Role for 2FA, New Extensibility API Methods, and Legacy Config Migration

Overview

The 2018.2 release of SuiteCommerce and SuiteCommerce Advanced (SCA) touches developer tooling, the extensibility API, configuration record layout, and runtime requirements. The most impactful changes for developers are the new SCDeployer role required for CLI deploys under Two-Factor Authentication (2FA), two new LayoutComponent methods, and a mandatory Node.js version bump. SCA also drops the legacy mountain-name convention (Denali, Mont Blanc, Elbrus, etc.) in favor of date-based versioning (e.g., "SuiteCommerce Advanced 2018.2").

Two-Factor Authentication & the SCDeployer Role

NetSuite 2018.2 accounts are provisioned with 2FA by default. The SuiteCommerce developer CLI tools (gulp-based) cannot complete an interactive 2FA challenge, so a new role called SCDeployer is shipped inside the Extension Management SuiteApp (2018.2 bundle). You must assign and configure this role before running any of these commands:

• gulp extension:fetch
• gulp extension:deploy
• gulp theme:fetch
• gulp theme:deploy
• gulp deploy

Without the role configured, these commands will fail against any 2FA-enabled account.

Extensibility API: New LayoutComponent Methods

Two methods are added to LayoutComponent:

• registerView() — Makes a child view available in any template attached to the component. Template developers reference the child view via an HTML element with a data- attribute.
• showContent() — Renders additional content on the page, either as a modal overlay or as a full replacement of the main view.

These are additive; no existing API surface is removed.

SuiteCommerce Configuration Record Changes

New Properties

• quote.showHyperlink — Show Request A Quote Hyperlink (My Account > Quotes)
• quote.textHyperlink — Hyperlink Text (My Account > Quotes)
• quickOrder.showHyperlink — Show Quick Order Hyperlink (Shopping > Quick Order)
• quickOrder.textHyperlink — Hyperlink Text (Shopping > Quick Order)

Moved to Legacy Tab

Footer and Newsletter configuration properties have been relocated to a new Legacy tab on the SuiteCommerce Configuration record. The base theme and SCA source code no longer ship the templates that consume these properties. They exist solely for backward compatibility with pre-2018.2 implementations.

• newsletter.companyName
• newsletter.genericFirstName
• newsletter.genericLastName
• footer.navigationLinks
• footer.navigationLinks.text

Oracle states that Footer and Newsletter functionality will be re-implemented as SuiteCommerce Extensions in a future release. New 2018.2 implementations will not have the templates to use these Legacy properties. SCA 2018.2 customers do not have access to these properties at all.

Google Tag Manager Editor

A new bundled SuiteApp lets you connect your SuiteCommerce site to Google Tag Manager without editing source code. Supported integrations include Google Analytics, Google Ads, Facebook Pixel, Optimizely, Bing, Criteo, and LiveChat. Install the SuiteApp bundle to enable the editor.

SMT Category Visibility Dates

SuiteCommerce 2018.2 supports Site Management Tools (SMT) Category Visibility Dates, enabling time-based display control, preview, and staging of categories. Requires Site Management Tools v3 or later.

Node.js Requirement Change

Developer tools now require Node.js 8.11.4. Previous versions are unsupported. This applies to theme, extension, and core SCA developer tool workflows.

What to Do

1. Set up the SCDeployer role. If your account has 2FA enabled (all 2018.2-provisioned accounts do), install or update the Extension Management SuiteApp (2018.2 bundle), assign the SCDeployer role to your developer users, and update your CI/CD or local gulp commands to authenticate with this role.
2. Update Node.js to 8.11.4. Run node -v in your development environment. If it is below 8.11.4, upgrade before using any SuiteCommerce developer tool commands.
3. Audit Footer and Newsletter configuration. If you are upgrading from a pre-2018.2 SuiteCommerce implementation, verify that your theme still includes the templates that consume Footer and Newsletter properties. If it does, the Legacy tab values will continue to work. If you are on a fresh 2018.2 install, these properties are inert—plan to adopt the forthcoming Extensions when available.
4. Adopt new Extensibility API methods. If you maintain custom extensions, evaluate whether registerView() and showContent() simplify your current child-view or modal rendering patterns. These are optional but can replace manual DOM manipulation.
5. Install the Google Tag Manager Editor SuiteApp if you currently manage third-party tags by editing SCA source. The bundled SuiteApp removes the need for code changes when adding or updating tag integrations.
6. Verify SMT version. If you want Category Visibility Dates, confirm you are on Site Management Tools v3 or later.