Best Practices for CCT Creation in SuiteCommerce

TL;DR Opening

Follow best practices when creating a Customer-Centric Technology (CCT) in SuiteCommerce to ensure proper extension functionality and a smooth development process.

Best Practices for CCT Creation

When developing a CCT, consider the following best practices to enhance extension functionality:

• The essential files for an extension with a CCT should include all required components, excluding the Sass files. You may also need to create SuiteScript directories and files pertinent to your extension module or the CCT module.

• Utilize the baseline extension generated by the extension development tools as a foundational starting point for building your SuiteCommerce site extensions. The example CCT discussed here will not use all generated files, and some of the initial code provided may need to be replaced with your specific functional code.

• You can implement a similar approach to create a single extension that references multiple CCT modules, optimizing modularity and reusability in your development process.

Understanding Baseline Extensions

A baseline extension consists of a set of files that resides in your local extension development directory, serving as the foundation for any extensions you intend to build for your eCommerce web store or SCIS deployment. When executing the gulp extension:create command, the developer tools will create this baseline structure in a Workspace directory within your main extension development directory.

This baseline extension typically begins with one custom module crafted according to your specific needs, which can incorporate various file types such as:

Creating a Baseline Extension

To create a baseline extension, you can follow these steps:

1. Open a command line or terminal.

2. Access the top-level directory of your extension development environment established during your extension development tool installation.

3. Execute the command:

   Copy

   gulp extension:create

4. Provide the necessary information for your baseline extension when prompted. Keep the following in mind:

   • Use only alphanumeric characters without spaces for entries.
   • Pressing Enter will default to the preset values.

When naming your extension, choose a fantasy name for the user interface display, which may include special characters and spaces, such as My Cool Extension!. Similarly, create a distinct name for the internal files and folders, specify your business or vendor name, and assign a version number relevant for tracking and updates.

Conclusion

Adhering to these best practices when creating a CCT in SuiteCommerce will streamline your development process and ensure that your extensions function correctly within the NetSuite environment.

Source: This article is based on Oracle's official NetSuite documentation.

Key Takeaways

• Follow best practices to leverage essential CCT files effectively.
• Use baseline extensions as a foundation for your development.
• Ensure accurate module structure to support extension functionality.