Custom SCAPI endpoints in 23.9
This update is truly a game-changer for Commerce Cloud customers! With the introduction of custom endpoints, we can fully customise Headless use cases, allowing for even more flexibility and control. AND without using a workaround!
Previously, hooks were the only way (through tweaking existing endpoints). But now, the possibilities are endless! And the best part? An open beta is available before the update freeze, so we can start exploring and testing this new feature immediately.
The development of custom endpoints will look a lot similar to how we build hooks:
- A mapping file (like hooks.json)
- A script file (Development is similar to controllers and hooks)
- A service schema file (The contract)
Another big thing to mention is that, if you look carefully at the screenshot, you can easily version your services for backwards compatibility!
Roadmap (Forward Looking Statement)
The ability to create custom GET endpoints is released together with the documentation.
The feature is officially released and recommended by Salesforce to be used in Production use cases (long story short, wait untill the holiday period is over before releasing your production use cases).
Paving the way for a Headless future
From a Headless perspective, Salesforce Commerce Cloud had much to catch up on compared to other platforms (which shall not be named 😎). But this area is rapidly evolving, and it was a necessary one. As customers interact with many different channels than just the storefront, other channels need to have a way of interacting with the platform – and usually that is through an API!
Giving developers and customers the freedom to customise is powerful. It also simplifies third-party integrations with Composable Storefront, and I expect more movement to happen in that area after this release!
As a bystander, it is noticeable that all “the rest” is not getting much attention, looking at the release notes of the past two months. But, understandably, decisions of priority have to be made.
Improve Product Search Result in Japanese
A new and exciting addition for Japanese customers. It is important to find the right product to ensure good conversion rates and improve customer experience.
Improve Code Profiler Tracking
Having “Production Mode” with less impact on performance will positively affect the TTFB (Time To First Byte), though it is not stated anywhere how much this will affect the storefront percentage-wise.
You can still access this information in other modes within 23.9, which are more useful for performance debugging.
The SLAS sessions will be limited to 45 days until September 15th, which was also mentioned in last month’s release notes – and a very important one to take note of.