Latest articles
-
Best practice for creating a service in SFCC
Let’s say we want to query an external REST API, and will use LocalServiceRegistry for this. What is the best approach for creating our service with a proper encapsulation?
-
Commerce cloud client id not working
In order to use OCAPI in SFCC, you sometimes need to add a new client id. But why is the new id not working?
-
How to make Page Designer components searchable
Page Designer pages can be part of the search result just like content assets, however there are some details to take into consideration.
-
How to use multiple scopes for Commerce Cloud Job Steps
Sometimes your job steps need to run in specific scopes, but not all of them in same scope. Here is how to set up a job for this requirement.
-
How to add a column with not-null constraint in Liquibase
Let’s assume we have a running project using liquibase for the schema migrations and we want to add a new column to the user column. Our initial approach could look something like this:
-
Why querystring should be cached in SFCC
The modules/server/request.js of the Salesforce Commerce Cloud defines the querystring in the following way:
-
How to transform a Spring Boot Initializr Project to Multi Module
Spring Boot Initializr is the perfect starting point for creating a Spring Boot Gradle project from scratch. However it doesn’t provide an option for using a multi-module approach - which are the basic steps do make this transformation yourself?
-
How to integrate an HTTPForm controller
When adding a service in the Business Manager (Administration > Operations > Services) one of the types needs to be selected (like SOAP, FTP, etc.). They correspond with a specific service class when implementing the service call (dw.svc.SOAPService, dw.svc.FTPService, etc.). But how to pass parameters to a service with the type HTTPForm?
-
Fix Liquibase includeAll in a Spring Boot project
Liquibase has a very useful feature when using it in a Spring Boot multi-module project: includeAll. Unfortunatly it’s not working properly.
-
Extend a controller in the Salesforce Reference Architecture
With the new Salesforce Reference Architecture (SFRA) you are encouraged to keep the app_storefront_base untouched. Instead, custom functionality can be added by extending existing code. Let’s have a look how to do this with the Product Controller: