Category: Blog

CloudCraze, now commonly referenced as Salesforce B2B Commerce for Visualforce, helped organizations build B2B storefronts directly on the Salesforce platform. The solution supported capabilities such as customer-specific pricing, product catalogs, carts, checkout, account-based buying, and Community Cloud storefront experiences.

For Salesforce administrators and developers maintaining a legacy Visualforce commerce implementation, patch history remains an important operational reference. Version changes can affect security controls, JavaScript libraries, extension points, cookies, permissions, and storefront behavior.

At CLOUDSTREET, we have compiled the following ongoing log of feature updates, security patches, and bug fixes for CloudCraze and Salesforce B2B Commerce for Visualforce from January 2020 through April 2023. As new updates or patches are made available by Salesforce, this blog post will be actively updated to reflect them.

We are based in Houston, Texas, and support Salesforce customers locally and globally. If you need help evaluating a legacy commerce org, Schedule a Call with our team.

3 Ways Administrators Can Use This Version Log

This reference is particularly useful for three activities:

1. Release validation: Confirm which patch was installed in a sandbox or production org.
2. Security review: Identify releases that addressed guest-user access, extension-point vulnerabilities, cookie security, or potential cross-site scripting concerns.
3. Upgrade planning: Review JavaScript dependency changes and potential compatibility considerations before deploying a patch.

The release records below are organized chronologically and limited to the supplied history for versions 4.5 through 4.8.

2020 CloudCraze Patch Releases

Date	CloudCraze version	Patch build	Primary update
January 3, 2020	v4.8	3.133.24	Added guest-user security fixes for Communities. These fixes supported guest self-registration and cart creation after required Communities security alerts were addressed.
February 18, 2020	v4.8	3.133.25	Fixed a bug that could create multiple CC Order records when a buyer repeatedly pressed the space bar, Enter, or Return after selecting Process Payment.
June 3, 2020	v4.5	3.115.61	Addressed security vulnerabilities in extension point classes.
June 4, 2020	v4.6	3.119.32	Addressed security vulnerabilities in extension point classes.
June 9, 2020	v4.7	3.124.38	Addressed security vulnerabilities in extension point classes.
June 12, 2020	v4.8	3.133.26	Addressed security vulnerabilities in extension point classes. The release also included related permission and extension-point updates.
September 23, 2020	v4.5	3.115.62	Enabled the Secure attribute for HTTP cookies and upgraded jQuery and jQuery Migrate.
September 30, 2020	v4.6	3.119.33	Enabled the Secure attribute for HTTP cookies and upgraded jQuery and jQuery Migrate.

The 2020 releases show two recurring themes: Salesforce Communities security requirements and updates to front-end dependencies. The June releases focused on extension-point security across multiple version lines. The September releases improved cookie transport security and modernized JavaScript libraries.

Salesforce’s patch notes explain that the Secure cookie attribute helps ensure cookie data is transmitted through encrypted HTTPS requests. Administrators should also review custom storefront code for compatibility when JavaScript libraries change.

2021 CloudCraze Patch Releases

Date	CloudCraze version	Patch build	Primary update
February 23, 2021	v4.5	3.115.64	Upgraded Handlebars and jQuery UI.
February 23, 2021	v4.6	3.119.35	Upgraded Handlebars, Bootstrap, and jQuery UI.
March 23, 2021	v4.8	3.133.29	Upgraded Handlebars, Bootstrap, and jQuery UI.
December 16, 2021	v4.5	3.115.65	Upgraded Handlebars to 4.7.7 and Underscore to 1.13.1.
December 16, 2021	v4.6	3.119.36	Upgraded Handlebars to 4.7.7 and Underscore to 1.13.1.
December 16, 2021	v4.7	3.124.43	Upgraded Handlebars to 4.7.7 and Underscore to 1.13.1.

The February and March 2021 releases primarily refreshed third-party JavaScript libraries distributed with the managed package. The December releases continued that dependency-maintenance approach, standardizing Handlebars and Underscore versions across the 4.5, 4.6, and 4.7 lines.

JavaScript Dependency Considerations

Library upgrades can be beneficial from a security and maintainability perspective, but they can also affect custom storefront behavior. Before deploying a patch, we recommend reviewing:

1. Custom Handlebars templates for syntax or rendering assumptions.
2. Bootstrap-based themes for styling or component changes.
3. jQuery UI extensions for deprecated methods or altered event behavior.
4. Subscriber code and extension points that reference managed-package JavaScript resources.

If your team is unsure how a legacy storefront will respond to a dependency update, Contact Our Team for an assessment of your Salesforce commerce implementation.

2022 CloudCraze Patch Release

Date	CloudCraze version	Patch build	Primary update
January 13, 2022	v4.8	3.133.30	Upgraded Handlebars to 4.7.7 and Underscore to 1.13.1.

The 3.133.30 release continued the JavaScript library maintenance introduced in late 2021. For administrators, this patch is also a useful reminder that a release described as a library upgrade can have implications for custom templates, front-end extensions, and storefront regression testing.

2023 CloudCraze Patch Releases

Date	CloudCraze version	Patch build	Primary update
March 14, 2023	v4.8	3.133.31	Upgraded jQuery UI to 1.13.2 and jQuery Validate to 1.19.5.
April 4, 2023	v4.7	3.124.45	Upgraded jQuery UI to 1.13.2 and jQuery Validate to 1.19.5.
April 11, 2023	v4.5	3.115.66	Upgraded jQuery UI to 1.13.2 and jQuery Validate to 1.19.5.
April 13, 2023	v4.6	3.119.37	Upgraded jQuery UI to 1.13.2 and jQuery Validate to 1.19.5.

The April 2023 releases aligned the legacy version lines around newer jQuery UI and jQuery Validate libraries. When assessing these patches, developers should pay particular attention to custom validation rules, form behavior, client-side checkout logic, and any overrides to the standard user-interface includes.

For technical comparison, Salesforce documents the CloudCraze 4.6 history in its CloudCraze 4.6 patch notes and the 4.8 history in its CloudCraze 4.8 patch notes.

4 Administrator Recommendations for Legacy Patch Management

Although updates for the legacy 4.x version lines represented in this requested history concluded in 2023, this log remains a valuable compliance, security, and operational reference. We recommend four practical steps:

1. Record the installed build. Document the CloudCraze version and managed-package patch number in each environment.
2. Keep sandbox and production aligned. Salesforce recommends testing and validating the same patch build in a sandbox before installing that same build in production.
3. Review customizations. Inspect extension point classes, Visualforce pages, JavaScript overrides, Handlebars templates, and checkout customizations.
4. Retain evidence. Store release notes, test results, deployment dates, and sign-off records for audit and change-management purposes.

Salesforce indicates that installation URLs for some legacy patches may be available through a Support & Services case. Administrators should therefore confirm package availability and installation instructions through their Salesforce support channel before scheduling a deployment.

For organizations considering a broader modernization effort, CLOUDSTREET can help evaluate whether a legacy Visualforce storefront should be maintained, refactored, or considered for a newer B2B Commerce Accelerator. Our Salesforce services include implementation, integration, managed support, migration, and commerce optimization.

Why This Log Still Matters

A legacy package can continue supporting important revenue operations long after its most active development period. Patch history helps administrators answer practical questions such as:

1. Which security-related changes were applied?
2. When did the storefront’s JavaScript dependencies change?
3. Which environments received a specific build?
4. What regression tests should be repeated during an upgrade?
5. What evidence is available for an internal or external compliance review?

The log also provides context when diagnosing an older storefront. A checkout issue, login problem, template-rendering change, or unexpected browser behavior may relate to a package patch or dependency update rather than to a recent declarative configuration change.

As Salesforce continues evolving its platform and commerce capabilities, teams may also evaluate adjacent opportunities involving automation, analytics, and AI. Our Salesforce Artificial Intelligence services can help organizations assess those opportunities within a broader Salesforce roadmap.

Conclusion: Bookmark This 19-Release Reference

This post is an ongoing log of feature updates, security patches, and bug fixes for CloudCraze and Salesforce B2B Commerce for Visualforce. It consolidates 19 supplied patch records covering January 2020 through April 2023 and provides administrators and developers with a practical reference for maintenance, testing, security review, and compliance documentation.

As new updates or patches are made available by Salesforce, this blog post will be actively updated to reflect them. Bookmark this page and return when reviewing a legacy Visualforce commerce deployment or preparing for a package upgrade.

If you would like help with your Salesforce commerce roadmap, you can Schedule a Call, Get a Quote, or Contact Our Team. From our Houston, Texas headquarters, we support customers locally and globally.

Sources

• Salesforce Help: Patch Notes for CloudCraze 4.6
• Salesforce Help: Patch Notes for CloudCraze 4.8
• Salesforce B2B Commerce for Visualforce Release Notes and Upgrade Guide