SuiteCommerce and SuiteCommerce Advanced 2023.2 has been released • https://system.netsuite.com/app/help/helpcenter.nl?fid=section_89171237588.html • The base theme has been updated with numerous fixes and improvements, such as an updated look-and-feel, better accessibility and the ‘fall back’ theme architecture that should make future updates to this theme (and any custom themes built with it) easier for customers • We have improved the way that changing the quantity of an item in the cart works — for a lot of items and use cases, this will result in a significant performance improvement • Out of stock messaging has been improved so that if a customer tries to order a number of items and some of them are out of stock, SuiteCommerce will now tell the user how many are unavailable • A variety of bug fixes and other small improvements

@Steve Goldberg is the NetSuite eCommerce Team planning to add more features to the extensibility API? For example, it would be really nice to have some hooks to inject logic in the

initialize

method in the same way we are able to inject logic in the

getContext

. Some native pagination on the front-end. I know that even SuiteScript has a

N/commerce

module, any plans to add utilities here? (I'm just asking 🙂 Developers would be very happy with the addition of new features to speed-up development)

We are planning on add more stuff to the extensibility API. Can you expand please: 1. What sort of things do you want to do in

initialize()

? 2. What do you mean native pagination? Can you give an example including a use case. 3. I'm not sure there's much development happening in N/commerce right now

@Steve Goldberg see below my answers: 1. Wow, there are a lot stuff that customizations require here, for example, some times you need to add validations on ship methods, payments, ship address, cart, product detail page, product list page, related items, etc. With older SCA versions you had the ability to inject logic before/after the initialize using the .wrap method, now you cannot. These would be like hooks, similar to what we can still do with

Application.On

on the backend. 2. Well, since we are very limited or is not best practice anymore on SCA to create custom modules to modify native sections from myAccount for example, there are scenarios where we need to re-do a transaction history list (sales orders, payments, invoices) and we need to handle the pagination on our end in the front-end, it is a repeated work that would be nice to have something built-in and configurable (SCS clients often request to re-create stuff like that as well) 3. I see, that I would be great having available the utilities methods on the backend suitescript 2.0, or the configuration record.

@Steve Goldberg Can we expect the following updates in the upcoming releases? 1. more extensibility API for the MyAccount application to customize the order, especially for the 'Request-a-Quote' page. 2. Use of custom skins on local. Currently, they're not working when you run local. 3. Extensibility API to modify the breadcrumbs on CMS pages. 4. Additional events for the CMS pages similar to the events of Backbone view.

Regarding point 4, @Sohan Kumar Dash, can you not just use

cms:rendered

?

I wasn't aware of this event. Thanks @Steve Goldberg Is there any documentation that lists events like this?

@Steve Goldberg Additional to the above bullet list, could we get in a future release an updated version of the dev tools when creating a new extension via command? The current version is still creating using the legacy backbone classes, it would be nice having the option to use the SCView, SCCollection, etc